If you work in the nonprofit sector, you’ve probably been asked to produce a theory of change, a logic model, or both. Grant applications use the terms almost interchangeably. Board members conflate them. And most program staff, if they’re being honest, aren’t entirely sure where one ends and the other begins.

That confusion isn’t just academic. Choosing the wrong framework for the wrong context — or building one when a funder expects the other — wastes evaluation time and weakens your application. This guide explains what each framework actually is, how they differ, when to use each one, and why the best evaluation strategies use both.

What Is a Theory of Change?

A theory of change is a comprehensive explanation of how and why your program’s activities will lead to long-term social impact. It maps the causal pathway from the problem you’re addressing to the ultimate change you want to see in the world — and critically, it makes explicit the assumptions underlying each step.

Think of it as the “because” document. Youth in underserved communities lack career exposure → therefore we provide mentorship with working professionals → because sustained adult relationships build social capital → which increases college enrollment → which improves lifetime earning potential. Each arrow requires evidence or at least a defensible rationale.

When to use a theory of change

  • Strategic planning. When your organization is defining or redefining its mission, a theory of change forces clarity about what you actually believe will produce change.
  • Complex initiatives. Multi-partner, multi-year programs with many moving parts need a theory of change to align stakeholders on the causal logic.
  • Funder narratives. Major foundations and impact investors increasingly ask for a theory of change in the narrative section of grant proposals.
  • Advocacy and systems change. When your work targets policy or systemic shifts — not just individual participant outcomes — a theory of change is the right frame.
Key feature: A theory of change surfaces your assumptions. If your program assumes that “mentorship leads to improved self-efficacy,” that assumption should be stated explicitly and, ideally, supported by research. When assumptions are hidden, evaluation becomes guesswork.

What Is a Logic Model?

A logic model is a visual diagram that maps a single program’s resources, activities, outputs, and outcomes in a linear, left-to-right sequence. It answers the operational question: what will we do, and what will we measure?

The standard logic model has five columns:

  • Inputs — The resources you invest (staff, funding, facilities, curriculum).
  • Activities — What your program does (workshops, counseling sessions, outreach).
  • Outputs — The direct products of activities (number of sessions delivered, participants served).
  • Short-term outcomes — Immediate changes in participants (knowledge gained, attitudes shifted).
  • Long-term outcomes — Sustained changes (employment, health improvement, recidivism reduction).

When to use a logic model

  • Grant reporting. Most federal and state funders require a logic model as part of the application or evaluation plan.
  • Program design. When launching a new program, a logic model forces you to connect every activity to a measurable result.
  • Staff alignment. A one-page logic model is the fastest way to get your team on the same page about what the program does and what success looks like.
  • Evaluation planning. The outcomes column of your logic model becomes the blueprint for your pre/post measurement design.
Key feature: A logic model is operational and concrete. It doesn’t explain why your approach works — it maps what you’ll do and what you’ll track. That simplicity is its strength for day-to-day program management.

Key Differences: Theory of Change vs Logic Model

Dimension Theory of Change Logic Model
Scope Broad — maps the entire causal pathway from problem to long-term social impact Narrow — maps a single program’s inputs through outcomes
Complexity Non-linear; may include multiple pathways, feedback loops, and external factors Linear; follows a left-to-right or top-to-bottom sequence
Assumptions Explicitly states and tests the assumptions behind each causal link Assumptions are implicit or listed separately
Primary audience Board, strategic funders, impact investors, policy advocates Program staff, grant managers, government funders
Typical format Narrative document or complex diagram (multi-page) One-page visual diagram (5-column table or flow chart)
Best timing During strategic planning, before designing programs During program design, before launching or applying for funding

When to Use Each Framework

The right choice depends on your context, audience, and program stage:

Use a theory of change when…

  • You’re applying to a foundation that explicitly asks for one (check the RFP language).
  • Your work addresses systemic or policy-level change, not just individual outcomes.
  • You need to align multiple partner organizations around a shared vision.
  • You’re in the strategic planning phase and haven’t yet designed specific programs.

Use a logic model when…

  • A government funder requires one as part of the grant application (most do).
  • You need to design an evaluation framework with specific, measurable indicators.
  • Your program team needs a practical reference document for implementation.
  • You’re building a grant report and need to map activities to outcomes clearly.

Use both when…

  • You’re applying for a large, multi-year grant that requires both strategic rationale and operational detail.
  • Your organization runs multiple programs that serve a single overarching mission.
  • You want a theory of change for the board and a logic model for the program team.

How They Work Together

Theory of change and logic model are not competing frameworks — they’re complementary layers of the same evaluation strategy. The theory of change sits above the logic model in the hierarchy:

  1. Start with the theory of change. Articulate the problem, your approach, the causal assumptions, and the long-term impact you’re working toward. This is your strategic foundation.
  2. Build logic models for each program. For every program component, create a logic model that operationalizes one pathway in your theory of change. The logic model’s outcomes should map directly to steps in your causal chain.
  3. Use the logic model to drive evaluation. The outcomes column becomes your measurement plan — the specific indicators, instruments, and data collection points for your pre/post evaluation.
  4. Use evaluation results to test the theory of change. When your data shows that a logic model outcome was (or wasn’t) achieved, that evidence either supports or challenges the assumptions in your theory of change. This feedback loop is how evaluation drives organizational learning.

Organizations that connect both frameworks build evaluation systems that are strategically coherent and operationally practical. The theory of change tells the story. The logic model runs the program. The data ties them together.

Automate the Measurement Layer

Whichever framework you use, the hardest part is the same: collecting pre/post data and running the statistical analysis that proves your outcomes actually occurred. That’s where most nonprofits get stuck — not on the framework, but on the math.

OutcomeRadar handles the analysis layer automatically. Upload your pre/post survey data, and it runs paired t-tests, calculates effect sizes (Cohen’s d), determines statistical significance, and generates a funder-ready report — whether your outcomes come from a theory of change or a logic model. The framework is your job. The statistics are ours.

Your framework defines the outcomes. We prove they happened.

Upload pre/post survey data and OutcomeRadar runs the statistical analysis — t-tests, effect sizes, significance levels — and produces a funder-ready report in 60 seconds. No statistics background required.

Try OutcomeRadar free with sample data →
← Back to Resources