Skip to content
WHO/AFRO HIS Review

Search is only available in production builds. Try building and previewing the site to test it out locally.

10 · Workplan (Weeks 4–10)

Owner: Pallavi Dani (core chapter) · Editors: Steven Uggowitzer Effort: ~1.5 person-days · Due: v0.5 EOD Fri 2026-09-04 · v0.8 Fri 2026-09-11

What WHO expects here

A workplan that is not a wall of prose. A Gantt they can look at once and know when things happen. Named consultant per deliverable. Named gate dates. Brazzaville trip windows explicit so WHO country office can plan around them. Ties back to the risk register so a reviewer can see what happens if a date slips.

Ultimate contents

Gantt through Weeks 4–10

Rendered chart (Mermaid gantt or a Typst-native diagram) that a reviewer can absorb in ten seconds. Colour-coded by workstream. Includes the four contractual deliverables + the intermediate internal artefacts (iteration demos, weekly updates, steering committee meetings).

Named deliverables + gate dates

Table view of the same content: what ships, when, who owns, who approves, what happens if it slips.

DeliverableGate date (hypothetical)AuthorApproverSlip consequence
D1 Inception ReportFri 2026-09-19StevenStephanie -> DrotiEvery downstream date compresses
D2 Draft Review ReportFri 2026-10-24Steven + SimonStephanie -> DrotiValidation-workshop rescheduling
D3 Final Review ReportFri 2026-11-07StevenStephanie -> DPMContract-close date at risk
D4 Executive PresentationWk 10 (Brazzaville if T2 confirmed)Steven + StephanieStephanieVerbal presentation delivered anyway

Resource allocation per consultant

Per-week per-consultant load. Where two consultants share a workstream, who is primary vs supporting. Where a consultant is off, that is called out (Steven off between date X and date Y — surface any known off-time here).

Brazzaville trip windows

Trip 1 (bid manifest = Simon + Charles, plus Stephanie francophone-cover from Johannesburg) opens on ~Wk 4. Trip 2 (if confirmed) around Wk 9–10 for D4 delivery. Steven joins Trip 1 only if IQVIA elects and only from ~2026-09-07 onward.

Milestone ties to risk register

Each gate date is a risk-register anchor. If the gate is at amber or red, the risk register (Chapter 11) shows why and what the mitigation is.

Change-control mechanism

If a date needs to move, the change-control log (T25 in the master plan) captures the request, the reasoning, and the WHO/IQVIA joint agreement. Named in this chapter so the mechanism is visible up-front rather than surfacing during the first slip.

Evidence to draw on

  • workspace/plan/00_MASTER_PLAN.md Part G (weekly execution schedule)
  • IQVIA Technical Approach §Gantt (bid slide 11)
  • workspace/repos/afro-docs/typst/assets/diagrams/ for Gantt sources
  • Consultant availability confirmations (out-of-band)

Complementary effort triggered

Pallavi’s core chapter. Gantt maintained in a live tool + exported. Explicit gate dates. Team commitment on availability confirmed in writing.