Program logic model: inputs, outputs and outcomes
A program logic model is a short description of how a program expects to produce a change. It connects what the team has, what it does, what it delivers and what participants are expected to gain. A useful model makes the proposed connection clear enough for someone to question it. It does not show that the program worked. It shows what the team thinks should happen and what evidence would help assess that belief.
Imagine a library offering evening workshops for people who want to complete online job applications. The program could count how many workshops it runs and how many people attend. Those counts tell the team what it delivered. They do not show whether participants can complete an application independently, which may be the outcome the program is intended to support.
Define the change a program logic model should explain
Write a short statement of the situation, who is affected and what the program can reasonably change. The library may be able to help participants navigate forms and upload a document. It cannot determine which people receive a job offer. That more distant outcome depends on hiring decisions, local job availability and other factors outside the workshops. Naming a result within the program’s influence makes the model easier to evaluate.
Describe what success would look like from the participant’s point of view. “Improve digital skills” is broad. “Use a sample form to enter information, upload a file and check the submission screen without step-by-step help” identifies something that can be observed. If access varies across participants, include it in the model. Someone may demonstrate the skill during a workshop but have no suitable device at home. The program should distinguish learning a skill from having the opportunity to use it.
Separate inputs, activities, outputs and outcomes
Inputs are resources the program uses, such as a room, working computers, staff time and a practice form. Activities are what the team does with those resources, such as running guided sessions and offering supervised practice. Outputs describe what was delivered or who was reached. They can include sessions completed, attendances and practice attempts. Outcomes describe a change in skill, knowledge, behavior or another condition the program seeks to influence.
Decide which unit each output counts. Fifty attendances could mean 50 people came once or ten people came five times. If the question is whether the program reaches more people, count unique participants. If the question is whether people receive enough practice, attendance per participant may matter. Write both measures if both questions matter, and explain how repeated participation will be identified without collecting more information than the team needs.
Keep the sequence short enough to follow. For the library, staff and equipment enable practice sessions. People complete sample applications during the sessions. Some participants then show they can complete a new sample without direct help. If the program later investigates actual application behavior, that is a further outcome with its own measurement and access constraints. One arrow should represent a connection the team can explain, not just a convenient place to insert an aspiration.
Identify assumptions that could interrupt the chain
Ask what must be true for each step to contribute to the next. Attendance may lead to practice only if the session includes enough time for each person to try the tasks. A successful practice attempt may transfer only if the sample resembles the forms people will encounter. Being able to apply independently may still depend on access to a device, a stable connection or appropriate support. These assumptions tell the team what else to observe.
List external factors separately from design choices. If the room is unavailable, the team can look for another venue. If a hiring website changes its interface, the team may need to revise the practice materials. If jobs are scarce, a decline in submitted applications could occur even when participants learn the intended skill. Record important outside factors so the evaluation does not attribute every change to the program.
Consider an alternative explanation for the expected result. Participants who return for several sessions may already be more comfortable with computers than people who attend once. If frequent attendees later perform better, the program may have helped, but the difference alone cannot establish how much it helped. A short starting task, administered consistently, can show what participants could already do and where the initial groups differed.
Attach measures the team can use
Choose a measure for each link you intend to examine. A sign-in record can show reach. A completed practice form can show that an activity occurred. An observation checklist on a new task can show which steps participants can handle independently. Set out who collects each measure, when it is collected and what will count as an acceptable record. An indicator that no one can collect consistently will not answer the question it appears to cover.
Agree how the result will inform a decision. If attendance is strong but practice is incomplete, consider changing session design or class size. If practice is complete but independent performance remains low, inspect which steps are causing trouble. A program can learn from a weak result when the model lets the team locate the break. The education program evaluation guide discusses how to turn such questions into a broader evaluation.
Check that the output measure cannot be mistaken for an outcome. In a summary table, label attendance as reach and a completed independent task as observed performance. If the team reports confidence from a short survey, report that separately from observed skill. A participant can feel more confident and still need help with a particular step.
Review the model with the people who run and use the program. They may identify a missing resource, an unrealistic assumption or a measure that does not reflect the experience. Revise it when the program changes, and record the date so later comparisons use the right version. A good model gives the team a practical explanation to examine and improve.
Ready when you are
Start your order with the essentials
Enter the topic, length, and deadline. We will carry these details into the full order form.
