A logic model maps how a program is expected to move from resources and activities to outcomes and impact. It helps teams choose useful indicators, track progress, and interpret findings, while making the assumptions behind each step easier to see and discuss.

Multiple Choice

Which statement best describes a typical use of a logic model in program evaluation?

A logic model is a planning and communication tool that shows how a program is supposed to work by mapping resources, activities, outputs, outcomes, and the intended impact. This structure helps you plan indicators, measure progress, and interpret results by making explicit the causal pathway and the assumptions behind it. In practice, you use it to decide what to measure, how to collect data, and how to judge whether results reflect the intended sequence from inputs to impact. It isn’t a statistical model used to test causality, so it’s not about conducting hypothesis tests. It isn’t just a budget tool, even though it includes resources as inputs. And it doesn’t replace a theory of change; a logic model often reflects that theory and helps you communicate it, but it doesn’t stand in for it.

A program can have clear goals, committed staff, and a busy calendar of activities—and still be hard to evaluate. The missing piece is often a shared picture of how the work is meant to lead to change. A logic model provides that picture. It maps a program’s resources, activities, outputs, and intended outcomes, helping teams decide what to measure and how to make sense of what they find.

That makes a logic model more than a tidy diagram. It’s a planning and communication tool: a way to show the reasoning behind a program and connect daily work with longer-term aims. When people can see those connections, evaluation becomes less like collecting numbers in a vacuum and more like asking useful questions about how, why, and for whom a program is working.

A simple map of how change might happen

Most logic models follow a sequence. A program starts with inputs, such as funding, staff time, equipment, expertise, or community partnerships. It uses those resources to carry out activities—the services, events, or other work the program delivers.

Those activities produce outputs, the immediate and countable results of that work. If a community program runs ten workshops, for example, the number of workshops held and the number of people who attended are outputs. They show what the program delivered, but not necessarily what changed for participants.

That next step is where outcomes come in. These describe changes that may happen because people took part, such as increased knowledge, stronger skills, or improved access to a service. Outcomes may be short-term or take longer to appear. A program might aim first to help people understand their options, then to support changes in their behavior, and eventually to contribute to broader community improvements.

Some models also include impact, a term often used for wider or longer-term effects. The distinction between outcomes and impact can vary across fields, so teams should define their terms rather than assume everyone uses them in the same way.

The sequence isn’t a promise that change will happen automatically. It’s a reasoned account of what a program expects to happen—and what needs to be true along the way.

From a diagram to useful indicators

A logic model helps evaluation teams choose indicators: specific signs that can show whether key parts of a program are happening or changing. Without a clear model, teams may collect data because it’s easy to count, not because it answers an important question.

Consider a job-readiness program. Its activities might include skills workshops and one-on-one coaching. Outputs could include the number of sessions delivered, attendance, or coaching hours. Short-term outcomes might include stronger interview skills or greater confidence in applying for work. Longer-term outcomes could include job placement or improved employment stability.

Each step calls for a different kind of indicator. Attendance records can show whether people took part, but they can’t show whether a workshop improved interview skills. A skills assessment or participant interview may offer better evidence of that change. Employment records could help track later outcomes, though the program may need to consider privacy, access, and how much time it takes for those outcomes to appear.

This is one of the model’s most useful roles: it helps match each question to a sensible measure. It also prompts teams to think about data collection before the program is underway. Who will gather the information? When will they do it? Can participants share it safely and comfortably? A little planning here can prevent a mountain of data that no one knows how to use.

Reading results with the whole story in view

A logic model can also help teams interpret findings. Suppose a program delivered all its planned workshops, but participants’ knowledge didn’t increase. The model gives evaluators a place to investigate the gap. Were the sessions reaching the intended audience? Did the material fit participants’ needs? Was there enough time for people to absorb it? Or was the chosen measure poorly suited to the kind of learning that took place?

On the other hand, if outcomes improved, the model can help the team ask whether the expected pathway makes sense. Did participants first gain knowledge, then change their behavior? Did another service or community event contribute to the result? These questions matter because programs don’t operate in a sealed room. Local conditions, policy changes, family responsibilities, and other services can all shape what happens.

A logic model doesn’t prove that a program caused an outcome. It isn’t a statistical method for testing causality. Instead, it makes the program’s reasoning visible and helps evaluators decide what evidence to collect. Stronger claims about cause and effect may require other evaluation methods, such as comparison groups or carefully designed statistical analysis.

That distinction is important. A map can show the route a program expects to take; it can’t, by itself, prove that the route led to the destination.

Not just a budget sheet—and not a theory by itself

Because inputs appear in a logic model, it can be useful during planning and discussions about resources. A team may see that a proposed activity needs staff time, transport, equipment, or specialist knowledge. That can inform budgeting. But the model isn’t only a budget tool. Its larger purpose is to connect resources and work with expected results.

It also doesn’t replace a theory of change. A theory of change explains why a program’s activities are expected to lead to particular outcomes. It often explores the conditions, assumptions, and wider forces involved. A logic model can show that reasoning in a compact, visual form, but a short diagram may not capture every detail behind it.

For example, a program might assume that offering evening workshops will improve attendance among working adults. That assumption could depend on reliable transport, childcare, or trust in the organization. If those conditions aren’t considered, a diagram may look neat while leaving out the very factors that shape participation.

The two tools can work together: a theory of change offers the fuller explanation, while a logic model makes the main pathway easier to discuss and use.

The model should change when the evidence does

A logic model is most helpful when teams treat it as a working document, not a polished poster that never moves. Programs change. Staff learn more about participants’ needs. New funding rules arrive. A community partner may leave, or a promising activity may prove harder to deliver than expected.

When that happens, revisiting the model can help teams separate a design problem from an implementation problem. If an activity wasn’t delivered as planned, the issue may be staffing or access. If it was delivered but the expected outcome didn’t follow, the team may need to examine its assumptions, timing, or measures. Those are different findings, and they point toward different decisions.

It’s also worth keeping the model clear. Too many boxes can make it difficult to see the main story. A useful version names the key resources, activities, outputs, and outcomes without trying to capture every detail of the program’s world. Teams can add notes about assumptions and external conditions alongside it.

A clearer route from effort to evidence

A logic model helps program teams decide what matters, what to measure, and how to interpret the results in context. It links the work people do each day with the changes they hope to support, while making assumptions easier to discuss.

It won’t prove causality, settle every question, or replace a deeper explanation of why change should occur. But it can give evaluation a clear starting point. When a program’s path is visible, the team can see not only whether activities happened, but whether those activities seem to lead where they were meant to go—and where the story may need another look.