These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Impact Measurement Platform
- Who it's for
- Public program offices
Public program offices
A public program office often reports outcomes across departments with different goals and reporting dates. The platform gives each organization and goal a stable code, then connects a program, its owner and observation lines to that context. A reviewer can inspect the source identifiers and supporting documents behind a reported value before making a revision-specific decision.
How Impact Measurement Platform is set up for you
Organization boundaries
Use distinct organization records where departments own different goals or review responsibilities. The code keeps results attributable when display names change.
Observation trail
Keep each measured line under the program, with its date, source identifier, unit and outcome state. This supports a review of the actual measurement rather than just a summary value.
Assigned corrections
Give missing evidence and returned review work a follow-up action with a named assignee and due date.
Decision history
Retain the reviewer, reason, source revision and evidence reference for each decision. Earlier returns remain part of the story after a corrected version is approved.
A public program office often reports outcomes across departments with different goals and reporting dates. The platform gives each organization and goal a stable code, then connects a program, its owner and observation lines to that context. A reviewer can inspect the source identifiers and supporting documents behind a reported value before making a revision-specific decision.
Begin with one organization, one active goal and a program whose observations come from a known source. Agree what source record identifier and document reference each line needs. Enter a pending line and a verified document, then rehearse a reviewer return and later approval. Use the program workspace to confirm that the current status and prior decisions tell the same story.
After that pilot, add further departments with their own goals and mapping rules. Decide who can read across organizations and which analyst summaries are authorized. Keep any external source or delivery acknowledgement in its owning system, with the corresponding reference or receipt recorded on the program's operation trace. This avoids treating a local status change as proof of an external result.
Features to start with
Roles on the team
- Read Only Analyst
- Reads authorized summaries and aggregates across every table plus the four platform pages. No record creation or editing, no schema or administrative capability.
- Impact Measurement Platform Operator
- Prepares assigned work: record entry on Impact Programs, Outcome Observations, Follow Up Actions and Evidence Documents, read-only on configuration, review and provenance tables. Scope to authorized organizations is enforced by workflow guards.
- Impact Measurement Platform Administrator
- Maintains approved configuration: record entry on Theory Of Change Goals, read-only on all operational, review and provenance tables, and access to all four platform pages. No schema editing, deletion, bulk operations or export grants.
- Impact Measurement Platform Reviewer
- Reviews independent assigned work: record entry on Review Decisions only, read-only on every other table. Reviewers cannot approve their own preparation; the workflow guards enforce reviewer independence.
Set up Impact Measurement Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.