Outputs are the direct products of activities
A logic model lays out how a program is expected to work, step by step: inputs (staff, funds, equipment, supplies) make possible activities (club meetings, blood pressure checks, teaching), which produce outputs (the direct, countable products of those activities, such as sessions held or people reached), which in turn lead to outcomes. Outcomes are divided into short-term (knowledge, attitudes), intermediate (behavior), and long-term (health status). In this item, the number of club meetings held against the plan is a direct product of program activities, so it is an output. Outputs measure what the program did, not what changed in the people it served.
Placing every option on the chain
The number of trained staff and working blood pressure monitors are resources put into the program, so they are inputs. The proportion of members taking medicines daily is a change in behavior, so it is an intermediate outcome. The number of stroke deaths among members reflects health status and is a long-term outcome that a one-year program may influence only slowly. Only the count of meetings held sits in the output box.
| Logic model component | Meaning | Example from this program |
|---|
| Inputs | Resources put in | Trained staff, working BP monitors |
| Activities | What the program does | Running hypertension club meetings |
| Outputs | Direct products of activities | Number of meetings held against plan |
| Intermediate outcome | Behavior change | Members taking medicines daily |
| Long-term outcome | Health status | Stroke deaths among members |
A quick test for outputs
A useful test is to ask whether the program team could produce the figure by its own effort, regardless of how clients respond. Holding meetings, distributing leaflets, and conducting home visits are within the team's control, so their counts are outputs. Whether members take their medicines or avoid stroke depends on the clients and on other factors, so those are outcomes. Watch out! "Number of" does not automatically mean output. The number of trained staff is an input, and the number of stroke deaths is a long-term outcome; look at what is being counted, not at the wording.
Why the distinction matters
Monitoring outputs tells the team whether the program is being delivered as planned, while measuring outcomes tells it whether the program is working. A shortfall in meetings held against the plan points to an implementation problem to fix early. Good outputs with poor outcomes suggest that the activities themselves need to change. Using the logic model in this way helps the municipal health team choose indicators for each stage and explain results to the local government.