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 Work

3.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 & Skills

5.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 understanding of the Workday data model and ability to trace data across related objects, select appropriate sources, and validate reporting and integration outputs.

• Working knowledge of XML, XSLT, and JSON; SQL and Workday REST/SOAP experience are desirable.

• Experience operating with separate Workday security administration and working alongside an AMS or managed-service partner, including specifying work precisely, reviewing and testing work returned, and retaining accountability for the outcome.

• Ability to elicit requirements from non-specialist business users, confirm written specifications, manage a prioritized backlog, document rigorously, and communicate effectively in English.

• Experience applying AI, analytics, or automation capabilities to enterprise reporting, data-quality analysis, documentation, testing, or operational support is desirable.

• Experience in a regulated, multi-country, or international organization environment is desirable.

5.2 Technical Competencies

• Reporting: Advanced, Matrix and Composite reports; calculated fields; Worksheets and dashboards; prompts, sharing, scheduling, performance and output validation.

• Workday data model: Business and related business objects; HCM/Financial relationships; report data sources and filters; single- and multi-instance relationships; data lineage.

• Integrations: EIB, Core Connectors, Cloud Connect, Document Transformation, RaaS, web services, XML/XSLT/JSON, transports and integration error handling.

• Operations and governance: Incident and problem resolution, release impact assessment, risk-based testing, migration, documentation, security-requirement definition, and audit evidence.

5.3 Certifications

Workday Pro certification in Reporting and/or Integrations is desirable. Workday Pro certification is available only through a Workday customer or partner organization; where it is not held, the candidate shall evidence equivalent hands-on production experience and completed Workday training obtained through a customer or partner organization. Relevant certifications in data, integration, or cloud platforms are an asset.

6. Language Skills

English: Fluency in written and spoken English is required.

Other languages: Working knowledge of Spanish is desirable; knowledge of French or Portuguese is an asset.

7. Key Performance Indicators

• Indicator: Assigned tasks delivered by the agreed date; Target: At least 90%, excluding documented PAHO-side dependencies and qualifying AMS escalations; Measured: Monthly

• Indicator: Monthly report complete and timely; Target: By the fifth working day; Measured: Monthly

• Indicator: Production changes with documented testing and approval; Target: 100%; Measured: Monthly

• Indicator: Scheduled report and integration run success; Target: Baseline within 45 days; target set by the Supervisor thereafter; Measured: Monthly

• Indicator: Report-performance remediation; Target: Completed against the Supervisor-approved remediation plan; Measured: Monthly

• Indicator: Integration failures resolved or covered by an approved workaround within service level; Target: At least 95%; Measured: Monthly

• Indicator: Assigned release regression testing completed within PMIS timeframes; Target: 100%; Measured: Per release

• Indicator: Business-critical reports and integrations covered by current documentation; Target: 100% by contract end; Measured: Quarterly

• Indicator: Reports within the approved rationalization scope assigned an owner or approved disposition; Target: 100% by the applicable agreed milestone; Measured: Monthly

• Indicator: Objects disabled or retired without approved disposition, dependency check, and notice; Target: Zero; Measured: Monthly

Service levels, priorities, and remediation windows are those confirmed under PAHO’s IT service-management framework at contract signature. On-time and remediation indicators exclude documented PAHO-side dependencies, including pending security configuration, specification clarification, approval, access, tenant provisioning, and PMIS release scheduling, where the consultant has recorded the dependency, requested action, responsible party, and risk notification when it arose. Critical incidents and incidents arising from consultant-delivered changes are reported and analysed with root cause and preventive action documented, rather than scored against an automatic zero threshold. Catalogue ownership and disposition measures apply to the Supervisor-approved rationalization scope and agreed milestones, not to business decisions outside that scope.

8. Work Schedule & Conditions

• Position: Workday Reporting and Integrations Consultant

• Work type / Duty Station: Full-time consultancy; remote (off-site), with a minimum of four hours daily overlap with Washington, D.C. business hours. Limited scheduled out-of-hours support may be required with advance notice and corresponding adjustment of regular hours.

• Duration: 6 months, subject to satisfactory performance, with a formal review at month two and availability of funds

• Position Type: Band A of International PAHO Consultant (IPC-Band A)

• Reporting To: IT Advisor, Business Solutions and Integrations Architect (the Supervisor)

• Work Assignment: All work is assigned, prioritized, approved, and accepted through the Supervisor; reporting specifications are defined and approved by the responsible business area. The consultant shall not independently commit to delivery dates, initiate development activities, or accept new work outside the approved intake and prioritization process without prior authorization.

• Remuneration: Daily Rate $215

• Benefits and equipment: No health insurance, benefits, allowances, equipment, or office space are provided beyond the stated remuneration. The consultant is responsible for insurance, taxes, social-security contributions, and an approved access arrangement.

• Security and confidentiality: PAHO information may be processed only through approved platforms and shall not be entered into public or unapproved AI services. The work shall be performed personally by the contracted consultant; subcontracting or substitution is not permitted without prior written approval from PAHO. Credentials are issued personally and are non-transferable, and secret material shall at no point be transferred to or disclosed by the consultant.

• Intellectual property: Work products created under the contract are PAHO property and must remain in approved repositories. No PAHO data or work products may be retained after contract end.

ADDITIONAL INFORMATION

• This vacancy notice may be used to identify candidates for other similar consultancies at the same level.
• Successful candidates will be placed on the roster and subsequently may be selected for consultancy assignments falling in this area of work or for similar requirements/tasks/deliverables. Inclusion in the Roster does not guarantee selection for a consultant contract. There is no commitment on either side.
• Only candidates under serious consideration will be contacted.
• All applicants are required to complete an on-line profile to be considered for this consultancy. For assessment of your application, please ensure that your profile in the PAHO Career page is updated; all experience records are entered with elaboration on tasks performed at the time. Kindly note that CV/PHFs inserted via LinkedIn are no accessible.
• A written test may be used as a form of screening.
• If your candidature is retained for interview, you will be required to provide, in advance, a scanned copy of the degree(s)/diploma(s)/certificate(s) required for this position. PAHO/WHO only considers higher educational qualifications obtained from an institution accredited/recognized in the World Higher Education Database (WHED), a list updated by the International Association of Universities (IAU)/United Nations Educational, Scientific and Cultural Organization (UNESCO). The list can be accessed through the link: http://www.whed.net/. PAHO will also use the databases of the Council for Higher Education Accreditation http://www.chea.org/search/default.asp and College Navigator, found on the website of the National Centre for Educational Statistics, https://nces.ed.gov/collegenavigator to support the validation process. Some professional certificates may not appear in the WHED and will require individual review.
• Any appointment/extension of appointment is subject to PAHO/WHO Regulations, and e-Manual.
• For information on PAHO please visit: http://www.paho.org
• PAHO/WHO is committed to providing a respectful and supportive workplace for all personnel .
• PAHO is an ethical organization that maintains high standards of integrity and accountability. People joining PAHO are required to maintain these standards both in their professional work and personal activities.
• PAHO also promotes a work environment that is free from harassment, sexual harassment, discrimination, and other types of abusive behavior. PAHO conducts background checks and will not hire anyone who has a substantiated history of abusive conduct.
• PAHO personnel interact frequently with people in the communities we serve. To protect these people, PAHO has zero tolerance for sexual exploitation and abuse. People who commit serious wrongdoings will be terminated and may also face criminal prosecution.
• PAHO/WHO has a smoke-free environment and does not recruit smokers or users of any form of tobacco.
• Applications from women and from nationals of non and underrepresented Member States are particularly encouraged.
• Consultants shall perform the work as independent contractors in a personal capacity, and not as a representative of any entity or authority. The execution of the work under a consultant contract does not create an employer/employee relationship between PAHO and the Consultant.
• PAHO/WHO shall have no responsibility whatsoever for any taxes, duties, social security contributions or other contributions payable by the Consultant. The Consultant shall be solely responsible for withholding and paying any taxes, duties, social security contributions and any other contributions which are applicable to the Consultant in each location/jurisdiction in which the work hereunder is performed, and the Consultant shall not be entitled to any reimbursement thereof by PAHO/WHO.