Program Outcome Story
Program Outcome Story is a ready-to-adapt example of a participant-centered program report, with a fictional repair-session story, a small outcome table, and clear limits on what the evidence shows.
Every employee gets a seat — priced per employee in Communications & Intranet, quoted with this template ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
Built for: Community and nonprofit services · Public libraries and repair cafés · Volunteer and civic programs
Overview
Program Outcome Story is a content-page example for reporting one program moment without letting an engaging account outrun its evidence. The sample follows a fictional neighborhood repair program through a Saturday lamp-repair intake session. It pairs a short narrative about a changed intake question with an illustrative participant quote, a three-row table of results, and a closing section that separates observations, unknowns, and next actions.
Use this format when a program has a bounded event or activity to describe, a record that supports its counts, and permission to share any participant perspective included. The sample says twelve lamps came in: seven were returned working, three needed parts, and two were referred to qualified repair specialists. Those figures are fictional examples for the template, not verified program results. The page also demonstrates how to state what one session does not establish, including long-term use, electrical safety, waste reduction, or a causal effect.
This is not a live performance dashboard, a case-management record, or a substitute for consent documentation, required funder reporting, or safety assessments. Do not use it to imply that every repair succeeded or that a single session proves lasting impact. Before publishing, verify the source record, confirm quote and image permissions, identify a page owner, and set a follow-up date for unresolved outcomes. Keep the page focused on this story; link to an authoritative program or policy page if readers need broader procedures.
What's inside this template
A lamp, a question and a changed intake conversation
A concise opening establishes the human moment and the specific intake question at the center of the story.
-
A fictional sample story from a neighborhood repair program: what happened at one Saturday lamp-repair intake session, what the program can show, and what it does not yet know.
What happened at Saturday intake
This section gives the event context, sample counts, recordkeeping approach, and limits on what one session can establish.
-
One session, twelve lamps, one changed question At a Saturday lamp-repair intake session, a participant placed a reading lamp on the table. She explained that she used it every evening and the room felt different without it. The volunteer paused before asking about the fault: “What would you like to be able to do again?” That question changed the conversation. The team began asking about the use of the item as well as the problem. It gave volunteers useful context without turning an intake conversation into a promise about the outcome. What the session recorded Twelve lamps came in. Seven were returned working, three needed parts and two were referred to qualified repair specialists. These invented sample counts describe one session; they do not establish electrical safety, long-term waste reduction or a causal effect of the changed question. The story behind the record In this fictional example, the program keeps a de-identified intake log in its own records system and a separate record of what a contributor permits it to share. The illustrative participant chooses a short quote and no photograph. The contextual image on this page does not depict that participant or event.
In the participant's words (illustrative)
The quote shows how a participant experienced the conversation while clearly marking the voice as fictional and the example as illustrative.
-
Fictional participant voice · the example includes a no-photo choice I came in because I read by that lamp every night. Nobody had asked me that before they asked what was broken, and it made me feel like the lamp was worth the trouble. Participant, Saturday intake session
The evidence behind the story
The table makes each sample result, its denominator, and the named record source easy to compare.
-
Counts describe this one session only, out of twelve lamps. Result Lamps (of 12) Record kept Returned working 7 De-identified intake log Needed parts 3 De-identified intake log, part noted Referred to qualified repair specialists 2 De-identified intake log, referral noted
Observed, not yet known, and what happens next
This section separates recorded facts from unresolved outcomes and assigns concrete follow-up actions.
-
Three separate statements, so no one reads more into the session than it shows. The next report should show what happened to the lamps waiting for parts, including any that could not be repaired. Observed: twelve lamps came in; seven were returned working, three need parts and two were referred to qualified repair specialists. Not yet known: whether the seven repaired lamps stay in use, and how the three lamps waiting on parts turn out. Next action: the intake lead adds a "what does this lamp do for you?" question to the intake sheet, and the coordinator checks in on the three lamps waiting on parts at the next session.
How to use this template
- Replace the fictional session details with a specific program event and verify each count against the source record you intend to cite.
- Confirm the participant’s permission for the exact quote and any image, and remove identifying details that are not approved for publication.
- Edit the narrative to describe what happened and what the team observed, keeping interpretation and claims of impact separate from recorded facts.
- Update the outcome table with the correct denominator, result labels, and record source, and mark results that remain pending.
- Assign the program owner to review the story, evidence limits, and next action before publishing it as a content page.
- Set a follow-up reminder for unresolved outcomes, then update the page or publish a clearly scoped follow-up when verified information is available.
Best practices
- Label illustrative figures as fictional during drafting and replace every sample count before publishing a real program story.
- Include the session scope and denominator beside the counts so readers do not mistake one event for cumulative program performance.
- Use a participant quote only with permission for the intended channel, and make a no-photo choice clear when relevant.
- Keep the source record named in the table so a reviewer can trace each result without exposing private intake details.
- Separate observed results, unknown outcomes, and next actions rather than blending them into a single impact claim.
- Describe referrals as referrals, not completed repairs, unless a later verified record confirms the result.
- Name an owner and revisit the story when pending outcomes change or the page no longer represents the program accurately.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What kind of program is this story template designed for?
The example follows a neighborhood lamp-repair program and one Saturday intake session. Its structure can suit community services, learning programs, volunteer initiatives, and other programs that want to pair a human perspective with a small set of observed outcomes. Replace the sample story and counts with verified material from the program being described.
Does the story prove the program caused an outcome?
No. The sample explicitly limits its claims to what one session recorded: twelve lamps came in, with seven returned working, three needing parts, and two referred to qualified specialists. It does not establish long-term use, waste reduction, electrical safety, or causation. Keep observed results separate from interpretation.
Who should prepare and approve a program outcome story?
A program coordinator or communications writer can assemble the story from the session record and participant-approved material. The program should designate an owner to verify counts, referrals, and wording before publication. The template does not prescribe an approval workflow, so use your organization’s existing review process.
How often should we publish or update this page?
The example describes one session, so it works best as a dated account of a specific event rather than a live dashboard. Publish a new story when there is a meaningful, verified program moment to report, and revisit the page if follow-up changes what is known about the reported outcomes. Do not leave a one-session snapshot looking like current cumulative performance.
How should we handle participant quotes and images?
Use a quote only when the participant has agreed to the specific use and wording, and follow your organization’s consent and privacy procedures. The fictional example describes a de-identified intake log and a separate record of sharing permission; its participant chooses a short quote and no photograph. The page’s contextual lamp image is not presented as a picture of the participant or event.
What should we customize before publishing?
Replace the fictional setting, story, quote, counts, record descriptions, and next actions with accurate information from your program. Confirm whether each result is final or still pending, and preserve the distinction between observed, not yet known, and planned. Remove any detail that cannot be substantiated or shared.
Can the outcome table connect to our records system?
The supplied table contains static sample values; it is not a live data connection. Verify figures against your source records and update the page manually unless your publishing setup provides a separately configured data connection. The example names a de-identified intake log but does not specify an integration.
What is the common mistake this format helps prevent?
A common pitfall is turning a small, single-session count into a broad claim about program impact. This layout separates the story, recorded results, unknowns, and next action so readers can see the evidence boundary. It still depends on the page owner keeping figures and follow-up notes accurate.
Related templates
Go deeper on the topic
-
A modern intranet is a specific surface — typically the home-base destination where employees get company news, find policies, and access key apps. A digital...
Ready to use this template?
Every employee gets a seat. Request pricing for Communications & Intranet and we quote into a workspace with Program Outcome Story ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
