What is a workplan, and how does it connect to results?

A workplan translates the "activities" level of a Results Framework into something schedulable and trackable: a concrete task, a responsible person or Implementing Partner, a start and end date or period, and a way of recording whether it actually happened. Without a workplan, "activities" remain a list of intentions with no way to tell whether delivery is on schedule.

A well-formed workplan activity carries several things at once: what is being done, who is responsible for doing it, when it is scheduled, what milestone or target it is meant to reach, and what status/progress it currently shows. Evidence — a photo, an attendance sheet, a signed record — is what turns a claimed "100% complete" into something a reviewer could actually verify rather than take on trust.

The relationship between workplan implementation and results reporting is directional and easy to get backwards: activities and their progress feed INTO a results report, they are not derived FROM it after the fact. A report built by reverse-engineering plausible-sounding activity progress to match an already-decided indicator narrative is not monitoring — it is storytelling wearing monitoring's clothes.

A workplan activity in METRA GET links to a logframe output, carries a responsible party, a status, and a progress percentage — updated as work happens, not reconstructed at reporting time.

The Workplan Scheduling Matrix shades which weeks an activity is planned for; Report Builder's "Next Work Plan" section reads that same schedule to show what genuinely comes next — the month, quarter or half immediately following the report's own period, never a hardcoded guess.