Impact programs

The impact program is the working record for an outcome. It carries a number, name, organization, owner, theory-of-change definition and observation date. Its status tells the team whether it is defined, collecting, validated, reviewed or published. The revision identifies the version being considered, while the outcome value and decision reason keep the eventual result close to its context.

The Impact Programs Workspace lets an operator select a program from a status board and inspect the related history, observations, decisions and operation trace. A reviewer can see the same selected case before recording a decision. That is useful when a program has had a return, a correction or an uncertain delivery attempt: the current status alone is only a summary of the case.

• Clear ownership. Assign a person and organization when defining the program.
• Visible progression. Use the recorded status and revision to identify the next action.
• Related context. Inspect observations, decisions, history and run details from the selected program.

The operator prepares the program and its evidence. The reviewer independently decides on the revision. Analysts read results and the supporting trail for authorized organizations. The administrator maintains the goal context used to classify the work.

Agree how a new program number is assigned and who owns corrections. Define what the observation date means for your reporting cycle. Select the goal that applies to the program before collecting outcome lines. Decide which source reference, service code and document hash are expected when a program is associated with an external delivery. Record who will investigate a result that needs reconciliation.

Use a real sample with multiple observations. Check that the operator can locate the program from the collection list, that a reviewer sees the intended revision, and that a later edit is distinguishable from the version already reviewed. Agree the evidence package required before a program is marked validated. Keep the reviewer’s reason on the decision record so a returned case has a clear next action.

An operator defines a community service program for one organization and links it to the current goal. The owner records the observation date and starts collecting measured lines. One line has a source record identifier and an outcome value; another needs a supporting document. The operator attaches the document, records its verification state and assigns a follow-up action for the missing source reference. Once the package is ready, the program is presented for review at its current revision.

The reviewer returns the revision with a reason. The operator makes the correction, preserving the earlier decision and status history, then sends the updated revision back. When a reviewer approves, the program can progress through reviewed to published. The analyst can inspect the reported value alongside the definition and decision trail.

• Program status board — Programs grouped by their recorded working state.
• Programs in collection — Defined and collecting programs with their owner and observation date.
• Programs ready for review — Validated programs waiting for an independent decision.

Define and collect follows the owner through observation entry. Review the revision follows the independent decision.