Define measures the organization and funder can both use by comparing the intended outcome, population, definition, method, timing, disaggregation, and decision—not by choosing whichever metric appears in the application template. Keep exact matches, translate differences explicitly, add valid funder-specific views, and escalate conflicts or missing evidence. The output is a shared measure specification that both parties can interpret without weakening the organization’s own outcome logic.
Your next step in the reporting course
Goal: Choose measures that your team and reporting audience can interpret consistently.
Start with: Bring your evidence plan and the audience requirements. Work on one important measure before extending the list.
Carry forward: Leave with an agreed measure and any unresolved differences. Next, write the counting rule so another person can use it.
Bring the unresolved reporting question from your funder context profile. This lesson turns it into a measure that a partner can collect and another person can calculate. The four alignment labels below describe actions. They are not course stages or an external certification. Keep them separate from evidence status: an agreed definition may still have missing observations.
- Name the decision the measure must support.
- Start with the organization’s intended outcome and governed definition.
- Extract the funder’s requirement and source language.
- Compare construct, population, method, timing, disaggregation, and calculation.
- Classify the relationship as Match, Translate, Extend, or Resolve.
- Write the complete shared measure specification.
- Test it against real records, missing data, and edge cases before agreement.
What makes a measure genuinely shared?
A measure is shared when both parties agree on what is being observed, who is included, how and when it is measured, how it is calculated, what missing evidence means, and which decision it can support.
The label is the least reliable part. “People served,” “jobs created,” “retention,” “well-being,” or “households reached” can conceal different populations, thresholds, time windows, data sources, and exclusions. Agreement on a label without agreement on the specification creates false alignment.
Begin with the outcome the organization is accountable for and the decision the funder needs to make. Then ask whether one indicator can represent that outcome credibly, whether several indicators are needed, or whether the evidence is not yet available. Fewer measures help only when they still cover the claims and decisions that matter. Two identically named measures may still be non-comparable because their sources, timing or calculation rules differ.
Use four alignment decisions: Match → Translate → Extend → Resolve
Every proposed measure should fall into one of four action categories. The category determines whether to reuse, crosswalk, add, or discuss the measure.
What exactly should you compare?
Compare at least seven attributes before treating two measures as equivalent.
| Attribute | Question | Common hidden difference |
|---|---|---|
| Construct | What change or condition is being represented? | Job start versus stable employment |
| Population | Who is eligible for the numerator and denominator? | All enrolled participants versus program completers |
| Method and source | How is the value produced and verified? | Self-report versus employer or administrative verification |
| Timing | At what event or follow-up window? | At exit versus 90 days after exit |
| Calculation | What are the numerator, denominator, aggregation, and rounding rules? | Rate among respondents versus rate among all eligible participants |
| Disaggregation | Which groups or places must remain visible? | Portfolio total hiding disability or place-based differences |
| Decision and claim | What action or conclusion is this measure allowed to support? | Operational monitoring presented as proof of attribution |
How do you write the shared measure specification?
Write enough detail that a program lead, partner, analyst, and funder would compute and interpret the measure the same way using the same records.
The specification should include:
- stable measure ID and display label;
- outcome or construct represented;
- plain-language definition;
- population and eligibility rules;
- numerator, denominator, unit, aggregation, and rounding;
- source, method, collection moment, and follow-up window;
- required disaggregation and suppression rules;
- missing-value and incomplete-follow-up treatment;
- quality threshold and known limitations;
- owner, approvers, version, effective date, and intended decisions;
- organization and funder mappings, plus external standards only where relevant.
Worked example: placement, checkpoint status and retention
Fictional course exercise. The program has 80 starters. At 90 days after exit, 60 have known employment status and 36 are employed. Twenty statuses are unknown. No continuous employment history or complete job-quality evidence has been supplied.
The funder’s draft form asks for “employment success.” Do not select a convenient percentage before agreeing what it means. A job start, employment on a specified date and continuous retention answer different questions. The same record may contribute to several measures, but the measures should remain distinct.
| Measure | Definition to agree | Available in the exercise? |
|---|---|---|
| Job starts | Eligible people who begin a job in the agreed period; specify whether repeated starts count | No complete start-event register supplied |
| Employment status at 90 days | Status at the agreed checkpoint after exit, with an explicit follow-up window | 36 employed among 60 known statuses |
| Continuous retention | Employment sustained through a defined period; specify gaps and job changes | Not established by one checkpoint |
| Job quality | Agreed aspects of suitable work and how they are assessed | Not established by employment status alone |
| Transport theme | Human-reviewed theme in the defined interview set | 12 of 18 interviewees mention transport; not cohort prevalence |
For the current records, report 60% employed among known statuses and 75% follow-up coverage. The confirmed proportion across all starters is 45%. Do not label the 20 unknown statuses as unemployed, or describe either percentage as a causal program effect.
Write one specification another person can reproduce
The following is a draft specification for the exercise. A team would agree the permitted timing tolerance and evidence source before implementing it; those details should not be guessed from the observed totals.
| Field | Draft rule |
|---|---|
| Measure ID | employment_status_90d_v1 |
| Population | All 80 starters in the defined course cohort |
| Checkpoint | 90 days after each person’s program exit; approve the allowable response window before collection |
| Numerator | Unique eligible people recorded employed at that checkpoint |
| Primary observed-rate denominator | Unique eligible people with known status at the checkpoint |
| Coverage denominator | All eligible starters due for follow-up |
| Missing state | Unknown stays separate from employed and not employed |
| Results supported | 36/60 = 60% observed employed; 60/80 = 75% coverage; 36/80 = 45% confirmed across starters |
| Interpretation limit | Point-in-time status, not continuous retention, job quality or causal attribution |
| Approval | Named program/data owner, version and effective reporting period |
Decide separately whether the funder needs an all-eligible rate, a rate among known statuses, or both. If the agreement specifies another denominator, preserve that view with its label and coverage note. Do not silently switch denominators to make reports agree.
Test edge cases before collecting the next period
Use a small test set containing ordinary and difficult records. Ask two people to apply the specification independently. Differences reveal an unclear rule before it becomes a reporting discrepancy.
| Test record | Expected review |
|---|---|
| One person submits twice | Apply the agreed identity and latest-valid-response rule; count the person once |
| A response arrives outside the follow-up window | Retain its timestamp; apply the approved window rule rather than shifting the date |
| No follow-up response | Record unknown and reflect it in coverage |
| Two sources report different statuses | Keep the conflict and resolve using the agreed source/review policy |
| A participant changes jobs | Do not assume continuous retention; use the explicit continuity rule |
| One partner sends only a percentage | Request counts and denominator; do not average percentages without valid weights |
A missing owner does not automatically mean a measure is unnecessary: assign responsibility before retiring a required measure. Likewise, an unavailable value may signal a collection gap. Record the decision to retain, revise or stop a measure and any reporting commitments affected.
How many measures should you keep?
Keep the smallest set that covers the decisions and material claims without hiding important differences. There is no universal correct number.
Review measures that have no owner or decision, duplicate another measure, or cannot be interpreted with available evidence. Resolve required collection and ownership gaps before removing them. Keep multiple measures when they represent different levels of a pathway, populations, time windows, risks, or stakeholder perspectives. A count of people trained, a competency change, and six-month employment are not redundant merely because they concern the same program.
When should you map to SDG, IRIS+, or GRI?
Map after the shared measure is fully defined. Record the exact external metric or disclosure, version, match quality, and any differences in boundary or calculation.
Use the official UN SDG indicator framework, the current IRIS+ catalog downloads, or the applicable GRI Standards. Do not claim exact alignment because the external label resembles the local outcome.
Use this alignment instruction
Compare the approved Organization Evidence Model, verified Funder Context Profile, current measure definitions, and any external standard actually required. For each proposed measure, return: decision supported; organization outcome and definition; funder requirement and exact source; construct; population; method/source; timing; calculation; disaggregation; missing-data rule; external mapping and version; and an action of MATCH, TRANSLATE, EXTEND, or RESOLVE. Cite both sides. Do not invent a metric, target, source, or funder preference. List contradictions, missing evidence, privacy concerns, and human decisions required before approval.
Where Sopact Sense improves continuity
The method can begin in a crosswalk spreadsheet. The problem appears when the same measure is used across forms, partners, programs, periods, funders, and reports while definitions continue to change.
In a configured Sopact workflow, agreed definitions can guide collection and analysis as responses and supporting documents arrive. Keep each measure with the relevant source, period and contact or partner record so later reviews use the same context. Check the implementation’s calculation, validation and permissions with representative records before depending on automated outputs. People approve definitions, mappings, targets, access rules, and exceptions; generated recommendations never become governed measures automatically.
Watch: connect measures to a reporting framework
Watch the 11-minute 58-second framework-to-report walkthrough. Use it to discuss the reporting view; verify the current standard and the measure specification separately. A demonstration does not establish an exact mapping. Browse the video library.
Frequently asked questions
What are the steps for defining shared impact measures?
Name the decision; start from the organization’s outcome; extract the funder’s sourced requirement; compare construct, population, method, timing, calculation, and disaggregation; classify the relationship as Match, Translate, Extend, or Resolve; write the full specification; and test it against real and incomplete records.
What is the difference between an outcome and an indicator?
An outcome is the change or condition the organization cares about. An indicator is the observable measure used to assess some aspect of that outcome. One outcome may require several indicators, and one indicator rarely captures every stakeholder perspective or causal explanation.
Should every funder receive the same measures?
They should draw from the same governed evidence model, but valid audience-specific views may differ. A funder-specific extension is acceptable when it is clearly defined and does not silently replace the organization’s core outcome or rewrite historical data.
What if the funder and organization use the same metric name?
Compare the complete specification. The same label can hide different populations, denominators, sources, time windows, or missing-data rules. Treat it as a Match only when the substantive rules agree.
What if the requested evidence does not exist?
Mark it missing and decide whether to collect it prospectively, use a defensible alternative, disclose the limitation, renegotiate the requirement, or decline the claim. Do not reconstruct unsupported historical values with AI.
How should qualitative evidence be included?
Define the question, source, consent, sampling or inclusion rule, coding method, review process, and permitted interpretation. Qualitative evidence can explain mechanism, context, variation, and unintended outcomes; it should not be silently converted into a quantitative value.
Can AI select the best impact metrics?
AI can compare documents, draft specifications, and flag conflicts. It cannot decide organizational priorities, infer funder intent, establish validity, or approve a measure. Require citations, testing across groups and formats, named owners, and documented human overrides.
Do standard metrics guarantee comparability?
No. Comparability also depends on population, unit, period, boundary, calculation, source, and missing-data treatment. Record the exact standard version and mapping quality rather than treating a shared code as proof of identical implementation.
Practice and continue
Choose one ambiguous measure. Write the source requirement, complete its specification and test at least three edge cases. Record what the owner approves and what remains unresolved. Carry that specification into the linked lesson.
Related practice: Give every measure one governed definition →
When you are ready to present the results, use How to Write an Impact Report and report examples.
By Sopact Academy · Revised September 12, 2026. The numerical exercise and draft specification are fictional. Apply the actual agreement and approved measurement rules in your work.