Skip to content

What Is a Logic Model for Grants? 5-Part Guide

Updated 4 official sources

Quick Answer: A logic model is a visual diagram that maps how your grant program's resources (inputs) lead to activities, outputs, and ultimately short- and long-term outcomes.

Full answer and how we checked it

It has 5 steps or components and is required by many federal community-based agencies including SAMHSA, DOL, ED, and ACF. The W.K. Kellogg Foundation model is a widely used format, but always follow the NOFO's own template if it has one.

Data note: Amounts may shift with annual appropriations.

In this guide

If you're a program director or grant writer building your first logic model, this guide explains what each component means and how to make your model score well with reviewers.

A logic model for grants is a visual or written framework that explains how your program's resources and activities lead to your intended outcomes. It shows reviewers - in a structured, readable format - that you understand the causal chain between what you're doing and what you expect to change.

It sounds simple. Most applications don't do it well.

Understanding what is a logic model for grants means knowing which agencies require it, how to build the 5-component framework correctly, and what the most common mistakes are - because reviewers see those mistakes constantly. Last updated: October 2026.

Which Agencies Require a Logic Model

Not every federal agency requires a logic model. Knowing whether yours does matters before you spend time building one.

Agencies that typically require a logic model:

  • SAMHSA (Substance Abuse and Mental Health Services Administration) - many behavioral health service NOFOs ask for one, but not all do, so check the attachment list
  • ACF (Administration for Children and Families) - required for most Head Start, child welfare, and family support programs
  • DOL (Department of Labor) - required for workforce development and employment training grants
  • ED (Department of Education) - required for many education program grants, particularly those under ESSA

Agencies that typically don't require a logic model:

  • NIH - NIH research grants don't use a logic model format. NIH uses the Specific Aims page and Research Strategy, which serve a different function.
  • NSF - NSF research grants use Intellectual Merit and Broader Impacts criteria rather than a logic model framework.

When in doubt, check the specific Funding Opportunity Announcement (FOA) or Notice of Funding Opportunity (NOFA). The required attachments section will list whether a logic model is required and whether there are format or page limit specifications.


Looking for your next grant?

About once a week, we email a short list of open grant calls with real deadlines from different funders. It lists open calls only.

No spam. Unsubscribe anytime.

The 5-Component Framework

The W.K. Kellogg Foundation model is the most cited logic model framework in federal grant writing, and it's the framework most agencies reference when they describe what they want. It has 5 components that run left to right, from resources to impact.

Component 1: Inputs

Inputs are the resources you put into the program. These are what you're investing to make the activities possible.

Examples of inputs:

  • Funding (federal award, organizational match)
  • Staff (number of FTEs, qualifications)
  • Facilities and equipment (clinic space, vehicles, software)
  • Community partners and referral networks
  • Existing data systems or assessment tools
  • Volunteer time

Don't list inputs as vague aspirations ("qualified staff," "community support"). Be specific: "2.0 FTE licensed social workers," "existing partnership agreement with County Health Department," "clinic space at 3 community locations."

Component 2: Activities

Activities are what you do with those inputs - the actual program services you deliver. This is where most applicants are appropriately specific, because activities are what the program narrative describes in detail.

Examples of activities:

  • Individual counseling sessions
  • Job skills training workshops
  • Outreach and community education events
  • Case management
  • Referral coordination
  • Data collection and assessment

Activities should be concrete and action-oriented. "Provide trauma-informed individual therapy" is an activity. "Support mental health" is not.

Component 3: Outputs

Outputs are the direct, countable products of your activities. They don't measure change - they measure what you did.

Examples of outputs:

  • 200 individuals enrolled in the program
  • 1,500 therapy sessions delivered
  • 24 job skills workshops conducted
  • 450 community members reached through outreach events
  • 80 case management plans completed

Outputs answer the question: how much did you do? They're measurable by counting - attendance, sessions delivered, materials distributed, referrals made. Outputs are important for process evaluation and for documenting program fidelity, but they don't tell you whether anything changed for participants.

Component 4: Outcomes

Outcomes are the changes that result from your activities - changes in knowledge, attitudes, skills, behavior, or conditions for the people you serve. This is where most logic models fall apart, and it's the most common reviewer critique.

The critical distinction: outputs vs. outcomes

This is the most common mistake reviewers see, and it costs points every time.

  • Output: "200 people attended the job training workshops." (What you did - countable)
  • Outcome: "75% of participants gained employment within 90 days of completing the program." (What changed - measurable improvement)
  • Output: "500 therapy sessions delivered." (What you did)
  • Outcome: "70% of clients showed a 5-point or greater reduction on the PHQ-9 depression scale at 90-day follow-up." (What changed)

If you can measure it by counting attendance, sessions, or deliverables, it's almost certainly an output, not an outcome. Outcomes require a before-and-after comparison or a threshold achievement that indicates change.

Outcomes are typically organized by timeframe:

Short-term outcomes (0-1 year): Changes in knowledge, awareness, or skills. These are the most proximal to your activities and the easiest to measure within a grant period. "Participants demonstrate increased knowledge of safe injection practices," "Participants can complete a professional resume."

Medium-term outcomes (1-3 years): Changes in behavior or practice. These are more meaningful than knowledge changes because they indicate actual application. "60% of participants remain employed at 6-month follow-up," "80% of clients remain engaged in treatment at 6 months."

Long-term outcomes (3-5+ years): Changes in community conditions or population-level indicators. "Reduced unemployment rate among target population by 15%," "Reduced psychiatric hospitalization rate in the service area."

Component 5: Impact

Impact is the long-term change in community conditions that your program contributes to - alongside other programs, policies, and environmental factors. It's the "why this matters at the population level" statement.

Examples: Reduced poverty rate in the target community. Improved workforce participation among returning citizens. Decreased youth suicide rate in the county.

Don't confuse impact with outcomes. Impact operates at the community or population level, over years, and is rarely attributable to a single program. Your logic model connects your work to a larger impact goal, but you won't measure impact within a 3-year grant period.


Logic Model ElementDefinitionExample (Workforce Program)
InputsResources you bring to the programStaff, funding, training materials, facilities
ActivitiesWhat you do with those resourcesJob readiness workshops, skills training
OutputsDirect products of activities200 participants trained, 50 workshops delivered
Short-term OutcomesChanges in 0-12 months150 participants earn credentials
Medium-term OutcomesChanges in 1-3 years120 participants employed at $18+/hr
Long-term OutcomesChanges in 3+ yearsReduced unemployment in service area

The Timeline Problem: Don't Set Yourself Up to Fail

One of the most common logic model errors is listing long-term community-level impacts as outcomes you'll measure during the grant period.

If your grant runs 3 years, you can't measure population-level change. The timeframe isn't long enough, and your program isn't operating at that scale. Promising to "reduce county overdose rates by 20%" as a 3-year grant outcome sets you up for a negative final evaluation report - and it raises credibility concerns with reviewers who know the timeframes involved.

Commit to outcomes that are genuinely achievable within your project period:

  • Knowledge and skill changes at program completion
  • Behavior changes at 3-month and 6-month follow-up
  • Employment and housing status at 90 days post-exit

Connect those outcomes to the longer-term impact through logic - "sustained employment reduces poverty and improves housing stability" - but don't commit to measuring the long-term impact within the grant period.


Theory of Change vs. Logic Model: What's the Difference

These terms are often used interchangeably in grant applications, but they have distinct meanings.

A logic model describes what you'll do and what results you expect. It's a map of the program's components and their intended sequence.

A theory of change explains WHY those activities lead to those outcomes. It articulates the causal assumptions underlying the program - why training someone in job skills leads to employment, why case management improves treatment retention, why peer support reduces isolation.

Some agencies want both. Most community-facing agencies are satisfied with a logic model that incorporates the causal logic in the accompanying narrative explanation. The visual diagram shows the components; the 2-3 paragraph narrative explains the reasoning.

If your FOA asks for a "theory of change," give them both the diagram and a clear explanation of the causal logic. If it asks for a "logic model," the diagram with a brief narrative is standard.


Format: Diagram vs. Prose

Most agencies that require a logic model want a visual diagram - a table or flowchart that shows the 5 components across a page or two. The visual format makes it immediately clear how inputs connect to activities connect to outputs connect to outcomes.

A standard table format:

InputsActivitiesOutputsShort-Term OutcomesMedium-Term OutcomesLong-Term Impact
2.0 FTE counselorsIndividual therapy sessions500 sessions deliveredReduced depression symptoms (PHQ-9)80% treatment retention at 6 monthsReduced psychiatric hospitalization

Always accompany the diagram with a written narrative - 2 to 3 paragraphs that walk the reviewer through the logic. The diagram organizes information; the narrative explains the causal reasoning. Without the narrative, reviewers are left to infer the connections themselves. That's work you don't want them doing.

Page limit: most logic model requirements fit within 1-2 pages for the diagram plus 1 page for the narrative. Check the FOA for attachment page limits.


Aligning Your Logic Model with Your Evaluation Plan

This is where many proposals lose points that have nothing to do with program quality. The logic model and evaluation plan must align - every outcome in the logic model needs a corresponding indicator and measurement method in the evaluation plan.

If your logic model lists "increased participant knowledge of diabetes self-management" as a short-term outcome, your evaluation plan must describe a knowledge assessment that measures that specific knowledge domain. If it lists "60% employment at 90-day follow-up" as a medium-term outcome, your evaluation plan must describe how you'll track employment status at 90 days.

Reviewers scoring the evaluation criterion look for this alignment. A disconnect between the logic model and the evaluation plan suggests the two were written by different people without comparing notes.

Build your logic model first. Then build your evaluation plan around it.

For the full evaluation plan breakdown, including agency-specific requirements and SAMHSA National Outcome Measures, see how to write a grant evaluation plan.


The CDC's Program Evaluation Framework

For health-related grants, referencing CDC's program evaluation framework signals methodological rigor to reviewers. CDC replaced its 1999 Framework for Program Evaluation in Public Health with the CDC Program Evaluation Framework, 2024 (opens in a new tab) (MMWR Recommendations and Reports, Vol. 73, No. 6, September 26, 2024). If your template still cites the 1999 version, update it.

The 2024 framework includes 6 steps:

  1. Assess context
  2. Describe the program (where your logic model fits)
  3. Focus the evaluation questions and design
  4. Gather credible evidence
  5. Generate and support conclusions
  6. Act on findings

Three cross-cutting actions apply at every step: engage collaboratively, advance equity, and learn from and use insights. The 2024 version also lists five evaluation standards.

You don't need to walk through all 6 steps in your narrative, but referencing the framework and showing that your evaluation design is grounded in it adds credibility - particularly for SAMHSA, HRSA, and CDC-funded programs.


Worked Examples by Program Type

Workforce Development Grant

Inputs: 3 employment counselors (2.0 FTE), employer partner network (12 companies), job listing database, training facility, $180,000 federal award

Activities: Skills and employability assessment, resume writing workshops, mock interview coaching, employer matching sessions, job placement follow-up calls

Outputs: 150 participants assessed, 120 resumes completed, 80 mock interviews conducted, 40 employer introductions completed

Short-term outcomes: 80% of participants complete a professional resume; participants demonstrate improved interview performance on a standardized scoring rubric

Medium-term outcomes: 60% of participants gain employment within 90 days of program completion; 70% of employed participants retain employment at 6-month follow-up

Long-term impact: Reduced unemployment rate among returning citizens in the target county


Mental Health Services Grant

Inputs: 4.0 FTE licensed therapists, clinic space at 2 community locations, referral agreements with 6 primary care practices, electronic health record system, $250,000 SAMHSA award

Activities: Individual therapy sessions (trauma-informed CBT protocol), group therapy sessions, care coordination and case management, crisis intervention, warm handoffs from primary care partners

Outputs: 75 individuals served, 500 individual therapy sessions delivered, 120 group therapy sessions held, 30 care coordination plans completed

Short-term outcomes: 70% of clients show a 5-point reduction on the PHQ-9 depression scale at 90-day follow-up; 65% show reduction on the GAD-7 anxiety scale

Medium-term outcomes: 80% of clients remain engaged in treatment at 6 months; 60% show sustained symptom reduction (PHQ-9 < 10) at 12 months

Long-term impact: Reduced psychiatric emergency department utilization in the target zip codes


Building Your Logic Model: Practical Steps

Step 1: Start with your long-term impact goal. Work backward from there to identify what conditions need to change (outcomes), what behaviors need to shift (medium-term outcomes), what people need to learn or gain (short-term outcomes), and what activities produce those changes.

Step 2: Identify every activity your program will deliver. Be specific about what each activity involves.

Step 3: Map outputs to activities. For each activity, what's the countable product?

Step 4: Map outcomes to outputs. What should change as a result of participants receiving these activities? Be honest about the timeframe each change requires.

Step 5: Draft the visual diagram. Keep it to 1-2 pages. Use a table or flowchart - whichever reads more clearly for your program's structure.

Step 6: Write the narrative explanation. 2-3 paragraphs explaining the causal reasoning connecting your activities to your outcomes.

Step 7: Check alignment with your evaluation plan. Every outcome needs a measurement method and a data source.

For the full evaluation plan breakdown, including SMART outcomes and agency-specific requirements, see how to write a grant evaluation plan.

For the full federal proposal structure, see how to write a federal grant proposal.



The Logic Model Flaw That Kills Applications in the First 60 Seconds of Review

A frequent logic model failure has nothing to do with the outputs-vs-outcomes confusion everyone talks about. It's a logic model that was clearly written after the narrative was finished, not before. Reviewers can tell. The inputs list doesn't match the budget. The activities don't match the work plan. The outcomes don't appear in the evaluation section.

The W.K. Kellogg Foundation model is a widely used template, and yet many applicants still confuse its two most important columns. The output column answers "how much?" The outcome column answers "so what changed?" That distinction isn't just semantic. Reviewers who see "delivered 200 sessions" in the outcomes column assume you don't understand your own theory of change, which calls into question whether your evaluation plan will measure anything meaningful. Short-term outcomes should show change at the knowledge or skill level, medium-term outcomes should show behavioral change, and long-term outcomes should show community or systemic change. The timeline problem is just as real: some logic models list "reduce county overdose mortality by 25%" as a medium-term outcome for a 3-year prevention grant. County-level mortality data has a two-year reporting lag, your program serves one county out of dozens, and the causal attribution is impossible to establish. That kind of outcome doesn't signal ambition. It signals that the applicant didn't think through the evaluation.

The causal logic in the narrative matters as much as the diagram. Most applications include the diagram but write a single sentence connecting it to the program. SAMHSA reviewers specifically look for an explanation of why each activity leads to the next level of outcome. If you're running peer support groups and expecting reduced psychiatric hospitalizations 18 months later, the logical pathway is: peer connection reduces isolation, reduced isolation improves treatment engagement, improved treatment engagement reduces crisis episodes, fewer crisis episodes reduce hospitalization. You can't skip from "peer groups" to "hospitalizations" without that chain. Reviewers who don't see the chain don't trust the causal logic, even if the diagram is beautifully formatted.

A better approach: build the logic model column by column from right to left. Start with the long-term impact you genuinely believe is achievable in 5 to 10 years. Work backward to the medium-term outcomes that would need to exist for that impact to happen. Work backward again to the short-term outcomes that would need to exist for the medium-term outcomes to happen. Then identify what activities would produce those short-term outcomes. Then identify what inputs those activities require. This reverse-engineering process produces a logic model where every arrow represents a claim you can defend. The forward-building approach, which starts with "here's what we're going to do" and then asks "what will probably happen," produces logic models with weak causal chains that reviewers sense immediately, even if they can't articulate why.

A common misreading: 2 CFR 200.202 (opens in a new tab) doesn't tell applicants to submit a logic model. It tells the federal agency to design each program "with clear goals and objectives" and performance measures before it posts the NOFO. Your reporting duties come from the award terms and the performance reporting rules in 2 CFR 200.329. Still, because agencies now have to state goals and measures up front, a logic model whose outcomes match the NOFO's performance measures gives you a ready map for those reports. One that doesn't will leave you translating your own outcomes into the agency's measures after the award.

What Federal Grant Reviewers Doesn't Tell You

A crowded logic model doesn't earn credit for thoroughness. Reviewers read many applications per cycle, so if they can't follow the causal chain quickly, you've lost the point. Simplify to your 3-4 strongest pathways.

Outcomes that can't be measured within the grant period don't belong in your logic model. "Reduced community poverty rates" as a 3-year outcome for a workforce training program isn't realistic or measurable in that timeframe. Use proximate outcomes: job placements, wage increases, credential completions.

Dotted-line arrows between your activities and outcomes signal weak theory. If you can't draw a solid causal connection between what you're doing and what you expect to happen, the reviewer will notice. Every arrow should represent a defensible assumption backed by evidence or prior research, the same standard behind the evidence tiers funders use.

How Grantsights Checked This Guide

Grantsights reviewed the W.K. Kellogg Foundation guide, CDC evaluation framework materials, SAMHSA application patterns, ACF program guidance, and the text of 2 CFR 200.202, and updated the CDC section in October 2026 for the framework CDC published in 2024. Where official sources stop: official templates show the boxes, but they rarely tell applicants when a logic model will fail because the budget, work plan, and evaluation plan do not match.

Source checkedWhat it confirmsApplicant decision
W.K. Kellogg Foundation Logic Model Development Guide (opens in a new tab)Inputs, activities, outputs, outcomes, and impact frameworkUse the accepted 5-part structure
CDC Program Evaluation Framework, 2024 (opens in a new tab)Six evaluation steps, with "Describe the program" as step 2Tie outcomes to evaluation measures
NIH application guide (opens in a new tab)Research applications use other narrative structuresDo not force a logic model into NIH mechanisms that do not ask for one
Grants.gov (opens in a new tab)NOFO attachment requirements vary by programCheck the attachment list before formatting

According to CDC's 2024 framework, published in MMWR, program evaluation work is organized into 6 steps wrapped in 3 cross-cutting actions. According to the W.K. Kellogg Foundation guide, a logic model links 5 core elements: resources, activities, outputs, outcomes, and impact. According to Grants.gov, attachment requirements are set by the specific opportunity package, not by a universal federal form. According to the National Institutes of Health, research applications use a different application guide structure than many service-grant NOFOs.

A logic model that introduces activities or outcomes not found in the budget, work plan, or evaluation section is a red flag reviewers can spot quickly, because each of those sections is scored against the same program.

Bad fit check: do not add a logic model when the NOFO does not ask for one and the page limit is tight. For example, an NIH R21 usually needs a clear Specific Aims page and Research Strategy, not a SAMHSA-style diagram. A SAMHSA services grant, DOL workforce grant, or ACF family-services grant is a better fit because reviewers expect outputs, outcomes, and evaluation measures to line up. Use this page with evaluation plan guidance, SMART objectives, federal proposal guidance, and current grant matches.

Sources


FAQ: Common Questions

Is a logic model the same as a theory of change?

They're related but not identical. A logic model describes what your program will do and what results it expects - it's a map of components and sequence. A theory of change explains WHY those activities produce those results - the causal assumptions underneath the model. Some agencies use the terms interchangeably. When an FOA asks for a theory of change, it typically wants a logic model that includes the causal reasoning in the narrative, not just the diagram.

Does NIH require a logic model?

No. NIH research grants don't use a logic model format. NIH uses the Specific Aims page and Research Strategy, which are structured around scientific significance, innovation, rigor, and feasibility - a different framework designed for research rather than service delivery. If you're applying to NIH, don't include a logic model unless a specific program announcement explicitly requests one.

How long should a logic model be?

The visual diagram should fit on 1-2 pages. The accompanying narrative explanation is typically 1-3 paragraphs. Some FOAs specify a page limit for the logic model attachment - follow it. Reviewers don't score length; they score clarity. A logic model that clearly presents the program's theory on one page is better than a sprawling 4-page document.

What is the difference between outputs and outcomes in a logic model?

Outputs are countable products of your activities - sessions delivered, people enrolled, materials distributed. They tell you how much you did. Outcomes are measurable changes that result from those activities - knowledge gained, behavior changed, symptoms reduced, employment attained. They tell you whether something changed. The test: if you can measure it by counting attendance or deliverables, it's an output. If it requires a before-and-after comparison or threshold assessment, it's an outcome.

What agencies require a logic model for grant applications?

Many SAMHSA behavioral health service NOFOs ask for a logic model, though some don't. ACF requires them for most child welfare, Head Start, and family support programs. DOL requires them for workforce development and employment training grants. ED requires them for many education program grants, particularly under ESSA. NIH and NSF don't typically require logic models for research grants. Always confirm by reading the specific FOA or NOFA for your program.

Last updated October 10, 2026. Corrected October 10, 2026: what changed. Published by Grantsights from public sources. See our editorial policy, how we build and check guides, corrections and how we make money.