Reach
How many people could reasonably have encountered the work?
Distribution only — never rename this impact.
AGENT SIX33Building from zeroAGENT SIX33Building from zeroFree tool · no signup · local-first
Build an honest impact scorecard that keeps reach, delivery, use, return, and evidenced change on separate lines — then export the strongest claim your evidence can actually support.
Why this exists
A view proves exposure. A delivery proves the promise arrived. Use proves contact. Return proves the first encounter mattered. None of those automatically proves a life changed.
This tool keeps each signal useful by refusing to collapse them into one flattering total. Unknown numbers can stay unknown. Zero can stay zero. The record becomes more credible because the definition does not move when the result is inconvenient.
A measurement system cannot rescue a vague intended change.
Use the same reporting window where possible. Leave unknown numbers blank.
A change number without a method is a story, not a measurement.
How many people could reasonably have encountered the work?
Distribution only — never rename this impact.How many people actually received the complete promise?
Proof that the work arrived, not that it worked.How many people meaningfully used or completed it?
Evidence of contact and utility.How many came back, replied, referred, or repeated?
Evidence that the first encounter mattered.How many have credible evidence of the intended change?
An impact claim can begin here — with the method attached.Unsupported
“We impacted 10,000 lives.”The number may only be views, distribution, customers, or intention. The claim hides the method.
Evidence-shaped
“10,000 people were reached; 420 used the tool; 38 returned; seven reported the intended change in a 30-day follow-up.”Every signal remains legible. The outcome language says what the evidence can and cannot establish.
An impact scorecard keeps distribution, delivery, use, return behaviour, and evidenced change on separate lines. It helps a team report what happened without turning every view, customer, or good intention into an impact claim.
Reach estimates how many people could have encountered the work. Impact requires credible evidence that something meaningful became different because of it. Reach can enable impact, but it is not evidence of change by itself.
A sale proves a transaction and may also prove delivery. It does not automatically prove the promised outcome. If the product's intended change is later evidenced, report the transaction and the outcome as separate numbers.
The method should match the claim. A direct self-report may support a carefully worded reported outcome; observed behaviour, repeated measurement, or independent verification can support stronger language. Always publish the method and limitations beside the number.
Usually they will when every number describes the same cohort and reporting window. If a later level is larger, check whether the sources, dates, definitions, or populations differ before calculating a conversion rate.
No. The scorecard runs in your browser and stores a working copy locally on that device. Nothing is submitted to AGENT SIX33. You can reset it or export a JSON copy at any time.