Pan Capital

OBJECTIVE OF THE OFFICE/DEPARTMENT

This is a requisition for employment at the Pan American Health Organization (PAHO)/Regional Office of the World Health Organization (WHO)

Contractual Agreement:

Non-Staff - International PAHO Consultant

Job Posting:

August 25, 2026

Closing Date:

September 20, 2026, 11:59 PM Eastern Time

Primary Location:

Off Site

Organization:

ITS Information Technology Services

Schedule:

Full time

PURPOSE OF CONSULTANCY

This requisition is for a consultancy at the Pan American Health Organization (PAHO)/Regional Office of the World Health Organization (WHO).

DESCRIPTION OF DUTIES:

1. Objective of the Department

The Information Technology Services Department (ITS) provides leadership and direction in the deployment of information and communication technologies and systems to support the Pan American Health Organization/Regional Office of the Americas of the World Health Organization (PAHO/WHO) in carrying out its mandate. ITS establishes and maintains strategies, policies, standards, and procedures to ensure the effective and efficient provision of information and communication services in a geographically dispersed environment.

2. Purpose of the Consultancy

PAHO operates the Workday-based PAHO Management Information System (PMIS) across human capital management, payroll and absence, finance, procurement, grants, and related processes. The reporting and integration layer delivers operational, managerial, and statutory reporting to business owners and connects Workday to financial, payroll, and identity systems and to the corporate data and analytics platform. ITS seeks a hands-on Workday Reporting and Integrations Consultant to support daily delivery, strengthen reporting and integration reliability, rationalize the report catalogue, and establish practical documentation and development standards. This is a delivery-focused, hands-on technical consultancy.

The consultant reports to and is supervised by the IT Advisor, Business Solutions and Integrations Architect, referred to in this document as the Supervisor, who prioritizes and accepts assigned work. The consultant works within a supported delivery model: business areas approve requirements; the Workday Security team administers security; the PMIS team coordinates releases; and an application management services (AMS) partner provides specialist or overflow capacity. The consultant remains accountable for assigned work and for reviewing AMS work returned within the reporting and integration scope, works autonomously against a prioritized backlog, and reports formally each month.

3. Statement of Work3.1 Delivery and Stakeholder Coordination

• Manage an assigned, prioritized backlog; confirm scope, acceptance criteria, dependencies, effort, and target dates; and maintain complete task records in the designated task-management system, which is the source of record.

• Elicit requirements directly from responsible business areas, translate them into technical specifications, confirm the specification before building, and demonstrate completed work. An incomplete, ambiguous, or technically unachievable specification is returned to the responsible business area and the Supervisor before development proceeds.

• Coordinate related work with PMIS functional resources, the Workday Security team, and the AMS partner, escalating capacity, capability, access, and critical-path risks through the Supervisor.

• Notify the Supervisor promptly where delivery is at risk and propose a recovery plan or revised date for approval. Review the existing catalogue before recommending new development and promote reuse over unnecessary custom development.

3.2 Workday Reporting and Data Model

• Design, build, test, maintain, and optimize Workday reports, particularly Advanced, Matrix, and Composite reports, together with calculated fields, Worksheets, dashboards, discovery boards, and other applicable reporting capabilities.

• Apply strong knowledge of the Workday data model, including business objects, related business objects, report data sources, indexed data sources, filters, single- and multi-instance relationships, calculated-field dependencies, and relationships between HCM and Financial Management data.

• Administer report prompts, formatting, sharing, scheduling, delivery, performance, and approved security behavior; tailor delivered reports where appropriate.

• Maintain the report catalogue and carry out approved ownership, consolidation, rationalization, disablement, and retirement activities under section 3.6.

3.3 Workday Integrations

• Design, build, test, deploy, and support EIB, Core Connector, Cloud Connect, Document Transformation, RaaS, and REST/SOAP web-service solutions.

• Develop and troubleshoot XML, XSLT, JSON, transformation logic, integration maps and attributes, launch parameters, transport configuration, PGP settings, and file conventions.

• Monitor scheduled integrations daily; resolve failures and discrepancies; implement reconciliation, data-quality, root-cause, corrective, and preventive controls; and maintain operational documentation.

• Specify integration security, credential, key, certificate, and transport requirements and implement integrations within configuration approved and provided by the Workday Security team.

• Deliver curated Workday data to PAHO's corporate data and analytics platform through approved extracts, RaaS endpoints, connectors, or web services, ensuring that outputs are reconciled, appropriately secured, efficient, and documented.

• Migrate reports, integrations, and configuration between tenants using approved promotion procedures.

3.4 Security Operating Model

• Identify and specify the security needed for assigned reports, data sources, calculated fields, Worksheets, dashboards, and integrations, including least privilege, segregation of duties, ISU/ISSG, domain-access, credential, certificate, key, and transport requirements.

• Configure integrations to use items approved and issued by the Workday Security team, which retains issuance, custody, and rotation of integration credentials, certificates, and encryption keys. The consultant does not generate, retain, or exchange secret material unless specifically delegated in writing.

• Do not create, modify, or assign security groups, domain policies, or business-process security policies unless a specific task is explicitly delegated and approved by the Workday Security team.

• Validate approved security behavior and report access failures, over-permissioning, unintended exposure, expiry risks, or changed data-access requirements promptly.

• Process PAHO information, including personal, payroll, medical, financial, confidential, or tenant-derived data, only through PAHO-approved platforms. Such information shall not be entered into public or unapproved AI services, and any AI-assisted output used in PAHO work remains subject to consultant review, validation, confidentiality, and human accountability.

• Maintain audit evidence for report and integration changes, and engage the ITS Information Security unit on security incidents, information classification, credential and certificate handling, and integrations transmitting PAHO data outside the tenant.

3.5 Operations, Releases, and Improvement

• Provide first-line support for the reporting and integration layer; coordinate Workday Support and AMS cases; and retain responsibility for specification, review, testing, acceptance, and documentation of escalated outcomes.

• Escalate work to the AMS partner where it exceeds available capacity against agreed priorities, requires capability outside the contracted scope, requires access the consultant does not hold, or is on the critical path for payroll or a financial deadline where reliance on one resource presents unacceptable risk. Escalation outside these criteria requires Supervisor approval.

• Assess Workday release impacts, execute assigned risk-based Sandbox Preview regression testing within PMIS cycle timeframes, address identified defects, monitor API and feature deprecations, and support tenant refresh validation.

• Establish a prioritized baseline of reports and integrations recording inventory, purpose, owner, data sources, calculated-field dependencies, approved security, schedules, downstream consumers, procedures, current run success, recurring failure patterns, and report-performance issues.

• Identify risks, technical debt, performance issues, duplication, and automation opportunities with estimated effort, benefit, risk, and dependency, and implement only work approved and prioritized by the Supervisor. Unprioritized findings remain recorded for future consideration and do not become open-ended obligations.

• Identify and propose practical automation and AI-assisted improvements to reporting, documentation, testing, reconciliation, and operational support for evaluation and prioritization by the Supervisor.

3.6 Report Catalogue Rationalization

Business-critical objects are designated under an existing PAHO classification or, where none applies, during the baseline and approved by the Supervisor. Payroll, financial close, statutory or external reporting, regulatory submission, downstream-system dependency, and external-party impact inform the designation.

• Analyse the complete catalogue at inventory level and provide detailed dependency review and proposed disposition for the Supervisor-approved rationalization scope, prioritizing business-critical, never-used, orphaned, duplicated, and superseded reports. Categories comprise: never run since creation and created more than twelve months previously; owner or last user departed more than twelve months previously with no subsequent use; historically used but not run within the previous twelve months; and duplicated or superseded reports.

• Before proposing retirement, check dashboard and worklet placement, sharing, scheduled delivery, sub-report use, use as another report's data source, and RaaS or integration consumption. An unresolved dependency prevents retirement.

• Propose a disposition of retain, reassign, consolidate, disable or retire, or defer for further review. Never-used reports and unused reports whose owner departed may be proposed for retirement without owner confirmation where no dependency exists. Historically used, duplicated, or superseded reports require responsible-business-area confirmation, because annual, statutory, and audit cycles may not appear in recent usage.

• Execute retirements by disposition list approved by the Supervisor. Identified affected owners receive thirty days' notice; approved reports are disabled rather than immediately deleted; and deletion may occur after a further sixty-day quiet period without objection, including after the consultancy where PAHO assumes the scheduled action.

• Record reinstatements with the reason. Reinstatement is a permitted outcome before reports are deleted; the control target is zero reports disabled or retired without approved disposition, completed dependency check, and required notice.

3.7 Documentation, Reporting and Knowledge Transfer

• Maintain specifications, data dictionaries, security requirements, test evidence, deployment records, runbooks, version-controlled work products stored in PAHO-approved repositories, and structured knowledge transfer.

• Provide demonstrations, walkthroughs, and user guidance to designated PAHO staff so that delivered work can be supported by PAHO personnel without the consultant, and submit the required monthly activity report.

• Deliver a secure documented handover covering in-flight work, configuration and design records, repositories, specifications, testing, runbooks, outstanding issues, operational dependencies, service-account requirements, certificate and key expiry information, renewal actions, and disposition lists in progress. It expressly excludes the transfer or disclosure of passwords, private keys, tokens, or other secret material; personal credentials remain non-transferable. Handover occurs during the final two weeks of the contract or within ten working days of notice of non-extension or termination, whichever occurs first.

4. Monthly Activity Report

By the fifth working day of the following month, the consultant submits a report drawing on the task-management system and containing:

• An executive summary of deliveries, AMS escalations, major risks, and next-month priorities.

• A system export of all assigned and carried-forward tasks. Narrative is required only for material changes, exceptions, delays, blocks, cancellations, re-scoping, and AMS escalations, stating reason, impact, action required, responsible party, and any approved revised date.

• Scheduled report and integration performance, incidents, production changes, releases, and preventive actions.

• Portfolio changes, rationalization actions, documentation coverage, milestone progress, security findings, and technical debt.

• Release impact and assigned regression-testing status where applicable.

A task is delivered when deployed or otherwise implemented in the approved environment, verified against the approved specification and acceptance criteria, documented, and accepted by the responsible business area or designated owner. Certification of the monthly deliverable is contingent on receipt of a complete monthly report.

5. Qualifications & Skills5.1 Education & Experience

• University degree in Computer Science, Information Systems, Software Engineering, Information Technology, or a related field, or an equivalent combination of education and relevant professional experience.

• At least three years of hands-on production experience with Advanced, Matrix, and Composite reports, calculated fields, Worksheets, and dashboards, and at least two years with EIB, Core Connectors, and Document Transformation. These periods may be concurrent.

• Demonstrated understan...