Nonprofit logic model examples should show more than five filled columns. They should connect a defined population and service to a plausible change, name evidence that could challenge the connection, and distinguish what staff deliver from what participants experience. Below are three hypothetical models for youth mentoring, food access, and workforce training, with measurement notes for each.
These are teaching examples, not evaluations of real organizations or promises of results. Use the nonprofit logic model template to arrange the chain; use your program records, participant input, and evaluation capacity to decide what belongs in it. The companion guide to creating a nonprofit logic model covers the blank-page workflow. This article focuses on comparing completed examples and testing their claims.
How to read the five-column examples
Read inputs → activities → outputs → near-term outcomes → longer-term contribution. Inputs are resources, activities are the work, outputs are its direct products, and outcomes describe change. A model can add intermediate outcomes or use different column labels when that makes the program easier to explain.
Do not classify an item solely by whether it contains a number. “Thirty people attended” measures delivery; “the share demonstrating a skill increased” measures change. Both are countable. The relevant distinction is what the measure represents. CDC's program-description guidance explains these relationships, rather than prescribing one mandatory layout.
Keep three notes below any example: the population and need, the assumptions connecting the boxes, and external factors the program cannot control. An arrow is a proposed relationship. It does not establish that the service caused the outcome, and moving a claim to the final column does not make it more credible.
Example 1: A youth mentoring program
Assume a community program supports students who want a consistent adult relationship and help navigating school goals. Define the eligible group, referral route, participation period, and consent process before copying the model. A broad mission such as “help young people succeed” cannot tell a coordinator who is supposed to receive which service.
| Part | Illustrative content |
|---|---|
| Inputs | Coordinator, trained and screened mentors, safeguarding procedures, school partners, meeting space, transport support |
| Activities | Match participants, run scheduled mentoring meetings, support mentors, review goals with young people, coordinate referrals |
| Outputs | Active matches, meetings delivered, mentor training completed, participant attendance and referrals recorded |
| Near-term outcomes | Participants report access to a trusted adult and can identify practical steps toward their chosen goals |
| Longer-term contribution | More sustained engagement with education and supportive relationships, alongside other influences |
The mechanism is the sustained relationship and appropriate support, rather than the meeting count alone. A participant can attend every session and still feel that the match is unhelpful. The model therefore needs a way to hear that experience and an activity for reviewing an unsuitable match.
For measurement, pair meeting records with a short participant check-in at entry and after a defined participation period. Ask consistent questions, explain how answers are used, and report how many people responded out of those eligible. If only the most engaged participants complete the follow-up, a favorable average may conceal people who left early.
Put the assumptions on the board: mentors remain available, meetings are accessible, young people want this form of support, and school partners can coordinate within appropriate permissions. Changes in transport, family circumstances, or school policy may affect participation. A graduation claim requires a longer observation period and stronger evaluation than a short mentoring pilot can normally provide.
A useful revision replaces “sessions delivered → better graduation” with “consistent meetings → trusted relationship and goal support → engagement indicators,” then states what remains uncertain. That gives staff an actionable link to improve when attendance is high but participant feedback is weak.
Example 2: A community food access program
Suppose a pantry wants eligible households to obtain usable food more reliably. The need is access, not merely distribution volume. Opening hours, travel, dietary suitability, storage, and how people are treated can all affect whether the service reaches that aim.
| Part | Illustrative content |
|---|---|
| Inputs | Food supply, volunteers, coordinator, suitable storage, distribution site, referral partners, record system |
| Activities | Source food, offer distribution appointments or walk-in access, provide appropriate choices, explain services and referrals |
| Outputs | Distribution sessions, household visits, food quantities, service information and completed referrals |
| Near-term outcomes | Participating households report more reliable access to food they can use and better understanding of available support |
| Longer-term contribution | Reduced food-access gaps and improved household stability within the broader local support system |
Distinguish unique households from visits. Twenty households visiting three times produce 60 visits, not 60 different households. The program may need both counts, but reporting one as the other would overstate reach. Write the unit and reporting period directly on the output card.
An evaluation question might be: “During the follow-up period, was the service available when participating households needed it?” Use a suitable, clearly defined collection method and ask whether the food was usable. Food insecurity is a separate outcome requiring an appropriate measure; pounds distributed cannot stand in for it.
Do not promise a reduction in food insecurity from a larger distribution total alone. Housing costs, benefit access, employment, food prices, and other services may change at the same time. If the program cannot observe these conditions, state that limitation rather than turning a distribution chart into a causal claim.
A weak chain is “more boxes → healthier community.” A stronger chain names who receives appropriate food, the access barrier addressed, the experienced change, and the observation period. If households report unsuitable items, the response is to revisit sourcing and choice, not simply increase the box target.
Example 3: A workforce training program
Assume a program helps adults seeking entry-level employment in a defined occupation. Specify the intended role and local demand before writing “employment” in the final column. A generic training offer may produce completions without preparing participants for the opportunities actually available.
| Part | Illustrative content |
|---|---|
| Inputs | Instructors, employer partners, curriculum, devices, accessible venue, participant support, labor-market information |
| Activities | Assess starting skills, teach and practice tasks, provide coaching, arrange relevant assessments and employer introductions |
| Outputs | Enrolments, teaching hours delivered, assessments completed, coaching meetings and introductions arranged |
| Near-term outcomes | Participants demonstrate relevant skills and can apply them in applications, interviews or practical assessments |
| Longer-term contribution | Employment and retention in suitable roles, with income or job-quality changes tracked where feasible |
A certificate can sit in different places depending on the question. “Certificates issued” is a delivery or completion count. “Participants meet an independently assessed competence requirement” describes an achieved capability. Define what the credential demonstrates before treating it as evidence that the program created useful skills.
Keep placement and retention separate. Someone starting a job and someone remaining in appropriate work after a stated follow-up period represent different milestones. Identify the denominator: all enrolled participants, all completers, or only those seeking work? None is automatically interchangeable with another.
For example, a hypothetical cohort has 40 enrolments, 30 completions, and 18 verified job starts. Job starts are 18/40 = 45% of enrolments or 18/30 = 60% of completers. Both calculations are arithmetically correct, but they answer different questions. Report the cohort, period, definition and missing follow-up status beside either percentage. These numbers are invented for the example.
Employer hiring decisions, transport, caring responsibilities, accessibility and economic conditions can affect the result. A logic model helps identify these dependencies; it does not remove them. If people gain demonstrable skills but cannot reach the available jobs, improving transport support may be more relevant than adding another class.
Compare the examples by mechanism and evidence
The same columns serve three different mechanisms. Mentoring depends on a useful relationship; food access depends on usable support reaching households; training depends on learning connected to opportunities. Reusing the boxes is reasonable. Reusing the outcome claims without checking those mechanisms is not.
| Example | Delivery evidence | Change evidence to investigate | Main interpretation risk |
|---|---|---|---|
| Mentoring | Meetings and active matches | Participant relationship and goal-support measures | Counting attendance as proof of benefit |
| Food access | Visits, unique households and quantities | Reliability and usability of access | Treating repeated visits as new households |
| Workforce | Teaching, completions and introductions | Demonstrated skills, job starts and retention | Changing denominators or ignoring missing follow-up |
Review at least one break in each chain. Ask what you would see if services were delivered as planned but outcomes did not improve. That question distinguishes a testable model from a diagram whose arrows are never allowed to be wrong.
Add a measurement note without overloading the diagram
Keep each outcome card short, then put the operational definition beside it. Record who is measured, the indicator, collection method, baseline or comparison, follow-up timing, denominator, missing-data treatment and responsible person. Add the decisions the result will inform, such as changing meeting times or revising a training module.
Avoid collecting information only because it might look useful in a funder report. Consider whether the team can gather it consistently, whether participants understand the purpose, and how access to the records will be managed. A modest indicator collected reliably can support better decisions than an ambitious measure with no owner.
Separate proposed targets from observations. Mark “target” or “hypothesis” explicitly, then record actual results when available. Do not invent a baseline to make a model look complete. If there is no baseline, identify the first feasible collection point and explain what comparisons will remain limited.
Review assumptions with people who deliver and use the service
Ask program staff whether the stated activities fit real staffing and schedules. Ask participants and partners, through appropriate and accessible participation, whether the proposed mechanism reflects their experience. Evaluation colleagues can help determine what the evidence could support and where claims need narrowing.
Use a left-to-right review for feasibility and a right-to-left review for logic. Starting from a desired outcome, identify the earlier change that would make it plausible, the activity that could influence it, and the resource needed to deliver that activity. An outcome with no believable connection should be revised or removed.
USDA's logic model planning framework also identifies assumptions and external factors. Use those headings to document disagreement, rather than hiding it in the grant narrative. A model is useful when the team can explain the uncertainty as well as the intended chain.
Adapt the example into a usable program model
Choose the closest scene in the template and replace the population, activities and outcomes with your own. Add an assumptions strip and a compact measurement note. Keep the detailed evaluation plan separate, with a clear reference to the corresponding outcome.
Export a PNG for a proposal or review pack and keep editable JSON for revisions. CodePic's shared link is read-only; one editor should consolidate review comments into the document. Date the version so a changed activity does not leave an old evaluation question attached to the new model.
For the administrative steps around submission and review, use the grant application process guide. The grant workflow and the program logic model serve different purposes: one tracks decisions and handoffs, while the other explains how the funded work is expected to contribute to change.



