play icon for videos

Logic Model: Components, Examples, and How to Build One in 2026

The complete guide to logic models — the five canonical components (inputs, activities, outputs, outcomes, impact), the if-then chain, four worked examples, an interactive builder, and what AI changes about the six-month logic-model project.

Updated
May 18, 2026
360 feedback training evaluation
Use Case

USE CASE · LOGIC MODEL

Inputs · Activities · Outputs · Outcomes · Impact. The five components have not changed. The six-month project to build them has.

Logic Model: Components, Examples, and How to Build One in 2026

The W.K. Kellogg Foundation's 2004 Logic Model Development Guide established the canonical five-component structure that program designers, evaluators, and funders have used for two decades. What are logic models, exactly? Working diagrams of how a program turns resources into change. The structure still holds. What changed is the build. The classical timeline — four to six months of workshops, consultants, drafts, and board reviews — is over. This guide covers the canonical components in full, walks four worked examples, gives you an interactive builder, and explains what AI logic model construction changes about the work underneath.

ANSWER

A logic model is a visual diagram showing how a program's inputs, activities, outputs, outcomes, and impact connect in an if-then chain. The W.K. Kellogg Foundation's 2004 Logic Model Development Guide is the canonical version. Strong logic models build right-to-left — start with the impact, work backwards through outcomes, outputs, activities, and inputs.

SECTION 01 · DEFINITION

What is a logic model

A logic model is a visual diagram showing how a program's inputs, activities, outputs, outcomes, and impact connect in an explicit if-then chain. It is the standard tool program designers, evaluators, and funders use to articulate what a program does, what it produces, and what change it is meant to create. The W.K. Kellogg Foundation's 2004 Logic Model Development Guide is the most widely cited version, and the five-component structure has been the canonical shape for two decades.

The discipline goes by several names — logic model, logical model, program logic model, logical framework, program model, results chain, theory of action. They are not interchangeable in every detail, but they share the same fundamental shape: resources committed produce activities done, activities done produce countable outputs, outputs drive participant-level outcomes, and outcomes contribute to broader impact. The Kellogg version remains the dominant reference because its 2004 development guide was structured for nonprofit and public-health practitioners rather than academic evaluators, and its templates are still in working use.

The classical workflow was a four-to-six-month project. Staff workshops, consultant engagement, multiple draft rounds, board approval cycles. The structure that emerged was sound. The cost of getting there was high enough that most programs built the logic model once at proposal time, filed the diagram, and rarely refreshed it. This guide covers the components, the if-then chain, and the build process in full — then explains what happens when the build compresses from months into days because the AI-native platform underneath handles the drafting and document mechanics that took most of the original timeline.

RELATED FRAMEWORK · THEORY OF CHANGE

A theory of change is the narrative reasoning about why a program should work — the assumptions, the causal pathways, the contextual factors. A logic model is the operational diagram of how the program will work. Theory of change answers why and under what conditions. Logic model answers what and in what sequence. Strong programs build both, with theory of change upstream of the logic model.

For the upstream framework, see theory of change. For the data-collection layer that feeds outcome measurement, see data collection methods. For impact measurement on completed programs, see stakeholder impact analysis.

SECTION 02 · THE FIVE COMPONENTS

Inputs activities outputs outcomes impact: the five components

The five canonical logic model componentsinputs activities outputs outcomes impact — run left to right in the diagram, connected by an explicit if-then chain. Each component answers a different question. Each has its own quality standard. The most common logic-model failure — and the most common reviewer critique — is confusing two adjacent components, especially outputs vs. outcomes. This section covers all five at the depth funders and evaluators expect.

01 · INPUTS

The resources committed to make the program possible

Inputs are everything the program has at its disposal before any work begins. Four standard categories: financial (grants, contracts, donations, earned revenue), human (staff hours, volunteer hours, consultant time, in-kind expertise), material (curriculum, facilities, equipment, technology, data), and relational (partnerships, community ties, regulatory permissions, brand standing).

QuestionWhat is the program committing to make this work?
TestSpecific enough to verify "is this adequately resourced?" Vague inputs ("funding, staff") signal a model that has not been costed.
Common errorListing what the program wants rather than what it has. Aspirational inputs produce aspirational logic models.
Example$400K Ford Foundation grant · 4 FTE instructors · partnerships with 12 employers · 12-week curriculum · 4,500 sq ft community space
02 · ACTIVITIES

What the program does with those inputs

Activities are the verbs of the logic model — what the program actually does to convert inputs into outputs. Train, deliver, coach, distribute, convene, refer, advocate, research. Activities should be scoped to match output scale; an output of 200 participants served implies activity capacity to deliver service to 200 people across the program's timeframe.

QuestionWhat does the program do, in concrete verbs?
TestA program officer could describe the activities to a peer in two minutes without referring back to documents. Specificity over jargon.
Common errorConflating activities with outputs. "Run training" is an activity. "Trained 150 participants" is an output.
ExampleRecruit participants · deliver 12-week training cohorts · run employer matching events · provide post-placement coaching for 6 months
03 · OUTPUTS

The countable products of activities

Outputs quantify what the program produced. Number of participants served, hours of training delivered, services provided, materials distributed, events held, reports published. Outputs answer how much did we do? They are necessary but never sufficient — a program that delivered 500 training hours achieved high output. Whether those hours produced any participant change is a different question, answered at the outcome layer.

QuestionWhat countable products did the activities produce?
TestEvery output number is dated, sourced, and verifiable from program records. No estimates.
Common errorReporting outputs as if they were outcomes. "Trained 200 participants" is an output. "200 participants gained employment" is an outcome.
Example200 participants enrolled · 160 completed all 12 weeks · 12 employer matching events held · 480 hours of post-placement coaching delivered
04 · OUTCOMES

The changes that result for participants

Outcomes are where impact measurement actually lives. Programs that confuse outcomes with outputs systematically over-report success. Outcomes are typically grouped by time horizon: short-term (changes in knowledge, attitude, or skill — the participant learned), medium-term (changes in behavior or practice — the participant applied), and long-term (changes in condition or status — the behavior produced sustained life change).

QuestionWhat changed for participants because of the activities?
TestEach outcome has a baseline measurement, a post measurement, and a clear unit of change.
Common errorVague outcome language ("improved", "increased", "strengthened") with no quantified change. If you can't measure it, it cannot anchor an evaluation.
Example120 participants placed in employment within 90 days · average wage $24/hr (vs $16 pre-program) · 80% job retention at 6 months
05 · IMPACT

The broader societal or systemic change the program contributes to

Impact is contribution, not attribution. A single workforce program does not produce regional economic mobility by itself — it contributes to it alongside other programs, employers, policy environments, and economic conditions. The honest logic model names impact as the system-level outcome the program is part of moving, without claiming sole credit. Impact-level evidence usually requires multi-year tracking and cross-program data, which is why programs that try to claim impact in a 12-month grant cycle fail under scrutiny.

QuestionWhat broader change is the program contributing to alongside other actors?
TestThe impact statement is plausible at multi-year scale and acknowledges co-contributing factors. No single-program-saves-the-world claims.
Common errorOverclaiming. Impact is contribution, never attribution. A program contributes to reduced regional underemployment; it does not solve regional underemployment.
ExampleReduced regional underemployment for adults without four-year degrees · increased family economic stability for participant households · a replicable workforce model adopted by three peer cities

The if-then chain. The W.K. Kellogg Foundation's 2004 guide introduced the explicit causal logic that links the five components: if these inputs are committed, then these activities can be delivered. If these activities are delivered, then these outputs will be produced. If these outputs are produced, then these outcomes will follow for participants. If these outcomes occur at sufficient scale, then this broader impact will be contributed to.

The chain forces program designers to articulate the assumptions linking each step — and to identify which links are evidence-based and which are aspirational. A logic model where every then is "this will obviously follow" has not done the work. A logic model that names two or three high-uncertainty links explicitly has identified what the evaluation needs to test.

SECTION 03 · BUILDER

Try the interactive logic model builder

Use this widget as a logic model template, a logic model generator, or a logic model creator — three names for the same job. It is useful whether you are learning how to do a logic model or how to make a logic model for the first time, or refining a draft for a funder submission. Type your program details into the five columns below. Click any cell to edit. Use + add to add rows. The if-then chain shows in the strip below — read left to right to test whether your logic holds. When you have a draft you want to keep, click Print to print or save as PDF. The builder is session-only — refreshing the page clears it, so print before you close the tab.

My program logic model

Click any cell to edit · Click + add to add rows · Click × to remove

PROGRAM NAME

01

INPUTS

resources committed

$400K Ford Foundation grant
4 FTE instructors
12 employer partnerships
12-week curriculum

02

ACTIVITIES

what the program does

Recruit participants
Deliver 12-week training cohorts
Run employer matching events
Provide post-placement coaching

03

OUTPUTS

countable products

200 participants enrolled
160 completed all 12 weeks
12 matching events held
480 coaching hours delivered

04

OUTCOMES

changes for participants

120 placed in employment within 90 days
Average wage $24/hr (vs $16 pre-program)
80% job retention at 6 months

05

IMPACT

broader contribution

Reduced regional underemployment for adults without four-year degrees
Increased family economic stability for participant households
Replicable model adopted by peer cities

This builder is intentionally minimal — five columns, editable cells, add and remove. For a logic model that stays current as program data flows in, the substrate behind it has to do more than render boxes. The architecture for that is described in section 11 (Where Sopact fits).

SECTION 04 · HOW TO BUILD

How to build a logic model: 5 steps

The five-step process below builds the model right-to-left — starting with impact and working backwards through outcomes, outputs, activities, and inputs. The reverse-order build is deliberate. The most common logic-model failure starts with available inputs and reasons forward into whatever fits, which produces logic models that justify the program but do not test it. Working backwards forces the team to articulate what change they are trying to produce before reasoning about whether the program design will produce it.

01

Start with impact and work backwards

Name the long-term societal or systemic change the program is contributing to. Be specific enough to be falsifiable. "Improve community wellbeing" is not specific enough. "Contribute to reduced regional underemployment for adults without four-year degrees by lifting their median wage above the regional self-sufficiency standard" is.

Impact is contribution, not attribution. A single program does not produce regional economic mobility by itself. Naming impact at the system scale, with explicit acknowledgment of co-contributing factors, is more credible than overclaiming.

OUTPUT: Impact statement — falsifiable, system-scale, contribution-framed, 1–3 statements.

02

Identify outcomes that would make the impact plausible

What short-term, medium-term, and long-term changes for participants would have to occur for the impact to follow? Short-term outcomes are changes in knowledge, attitude, or skill. Medium-term outcomes are changes in behavior or practice. Long-term outcomes are changes in condition or status.

Be honest about which outcome links are evidence-based and which are aspirational. The honesty becomes the evaluation design — the aspirational links are exactly what the evaluation needs to test. A logic model that pretends every link is established produces an evaluation that measures the wrong things.

OUTPUT: Outcomes inventory — 3–5 outcomes per time horizon, each with a measurable change unit and baseline.

03

Specify outputs that would drive those outcomes

What countable products of activities would be necessary to produce the outcomes? Outputs should be specific enough to count, dated enough to track, and large enough to plausibly move the outcomes downstream. An output of "10 participants served" is unlikely to drive an outcome of "regional underemployment reduction" — the scale mismatch reveals a gap in the if-then chain.

This step is also where most quality issues with logic models surface — confusion between outputs and outcomes. If a stated output sounds like a participant-level change ("participants gained confidence"), it is misclassified and belongs in outcomes.

OUTPUT: Output targets — countable, dated, scaled to the outcome targets they need to drive.

04

List activities that would produce the outputs

What does the program actually do to generate the outputs? Activities are the verbs of the logic model — train, deliver, coach, distribute, convene, refer, advocate, research. Match activity scope to output scale: an output of 200 participants served implies activity capacity to deliver to 200 across the program timeframe.

A program officer should be able to describe the activities to a peer in two minutes without referring to documents. Specificity over jargon. Activities written in foundation-speak ("strategic capacity-building convenings") usually mask less work than the language implies.

OUTPUT: Activity list — concrete verbs, scoped to deliver the outputs, sequenced for the program calendar.

05

Enumerate the inputs required to run the activities

Cost the program at sufficient specificity to answer "is this adequately resourced?" Four categories: financial, human, material, relational. Vague inputs ("funding, staff") signal a model that has not been costed. Specific inputs let funders and operators verify feasibility.

If the inputs cannot plausibly produce the activities at the required scale, the logic model has surfaced a real gap — either the activities need to scale down, or the inputs need to scale up. Either decision is more useful than discovering the gap mid-execution.

OUTPUT: Input inventory — specific by category, costed against activities, verifiable for adequacy.

The traditional version of this process took four to six months. Workshop facilitation, consultant engagement, draft cycles, board reviews. The structure of the work has not changed. The build time has, because the document mechanics — drafting, formatting, version control, stakeholder review packaging — have collapsed into hours rather than months. What stays the team's work is the assumptions, the outcome priorities, and the honesty about which links are evidence and which are aspiration.

SECTION 05 · WORKED EXAMPLES

Logic model examples across program types

Four worked logic model examples drawn from real program shapes — nonprofit workforce training, foundation grant program, public health initiative, and education intervention. Each runs through all five components with the level of specificity funders and evaluators expect. Patterns generalize: the shape repeats across sectors, even though the content does not.

EXAMPLE 01 · NONPROFIT WORKFORCE TRAINING

12-week technical training for 200 underemployed adults

A regional workforce nonprofit running a Ford Foundation-funded technical training program with employer placement and 6-month post-placement coaching.

Inputs$400K grant · 4 FTE instructors · 12 employer partnerships · 12-week curriculum · 4,500 sq ft community space
ActivitiesRecruit · deliver 12-week cohorts · run employer matching events · provide post-placement coaching
Outputs200 enrolled · 160 completed · 12 events held · 480 coaching hours delivered
Outcomes120 placed in 90 days · avg wage $24/hr (vs $16) · 80% retention at 6 months
ImpactReduced regional underemployment · family economic stability · replicable model adopted by peer cities

EXAMPLE 02 · FOUNDATION GRANT PROGRAM

$4M annual community foundation grant cycle

A community foundation running an annual grant program funding nonprofit work in education, health, and economic mobility across a six-county region.

Inputs$4M grant pool · 6 program officers · 24-member review panel · application platform · 14-month cycle
ActivitiesRFP release · LOI review · full application review · site visits · grantmaking decisions · grantee reporting cycles
Outputs180 LOIs received · 60 full applications · 24 grants awarded · 96 reports collected · 24 site visits
OutcomesGrantee orgs reach 18,000 participants · 12 grantees report sustained outcome change at 12 months · 80% grantee retention to next cycle
ImpactStrengthened regional nonprofit ecosystem · improved cross-sector coordination on shared outcomes · increased local philanthropic confidence

EXAMPLE 03 · PUBLIC HEALTH INITIATIVE

Maternal health intervention for 800 expectant mothers

A county health department running a CDC-funded maternal health initiative targeting late prenatal care entry and postpartum depression screening in a low-income service area.

Inputs$1.2M CDC grant · 6 community health workers · 3 clinic partnerships · validated PHQ-2 / EPDS instruments · transportation vouchers
ActivitiesOutreach to expectant mothers · early prenatal scheduling · home visits · PHQ-2 / EPDS screening · referral coordination
Outputs800 mothers reached · 720 entered prenatal care by week 12 · 800 PHQ-2 screens completed · 96 referrals to mental health services
OutcomesLate prenatal entry reduced 35% to 14% · postpartum depression diagnosis at 6 weeks rose from 4% to 11% (detection up) · 70% of referrals attended first appointment
ImpactReduced low-birthweight rate over 5 years · narrowed maternal mortality disparity for service-area zip codes · adopted by two neighboring counties

EXAMPLE 04 · EDUCATION INTERVENTION

Early literacy program for 1,200 K-2 students

A school district running an evidence-based early literacy intervention across 8 elementary schools, funded through Title I dollars and a Walton Family Foundation partnership.

Inputs$2.1M Title I + Walton funding · 24 reading specialists · evidence-based curriculum (Wilson, OG) · DIBELS assessment licensing · parent engagement coordinator
ActivitiesUniversal screening · tier 2/3 intervention groups · 90-min daily literacy block · parent literacy nights · benchmark assessments 3x/year
Outputs1,200 students screened · 480 receiving tier 2 · 120 receiving tier 3 · 24 parent nights · 3,600 benchmark assessments
OutcomesK students reading at grade level rose 42% to 71% · tier 3 students gained avg 1.8 grade-level equivalents · 65% parent engagement (vs 38% prior)
ImpactSustained literacy growth into grade 3+ · narrowed district reading-proficiency gap · approach replicated in two neighboring districts

Four sectors, four shapes, one structure. Notice what stays the same: every output is countable, every outcome has a baseline-to-post change, every impact statement is contribution-framed. Notice what varies: scale, time horizon, evidence standards, instrument choices. The logic model is the structural container. The program is the content.

SECTION 06 · VIDEO WALKTHROUGH

Two video views — the framework and the build

Two short walkthroughs cover the same material from different angles. The first explains the canonical structure — the five components and the if-then chain — for anyone new to logic models. The second walks through what AI-native construction looks like in practice, with the actual product running.

VIDEO 01 · OVERVIEW

Logic model — the framework explained

The five canonical components, the if-then chain, and the most common reviewer critiques. Good for orientation if you are new to logic models or revisiting after time away from the discipline.

VIDEO 02 · APPLIED

Building a logic model with Sopact AI

What AI-native logic model construction looks like in working software. Compresses the traditional four-to-six-month build into days while preserving the rigor of the components and the assumptions.

SECTION 07 · THE PARADIGM SHIFT

Logic models were built once. In 2026 they are kept alive.

The W.K. Kellogg Foundation's 2004 Logic Model Development Guide assumed the build was a one-time project. Four to six months of staff workshops, consultant engagement, draft cycles, board reviews — and then the diagram was filed. Programs revisited the model at major milestones, at most. The structure that emerged from that work was sound. The cost of getting there was high enough that the model rarely came back out of the drawer once executed.

That cost is what changed. The classical timeline was driven by document mechanics — drafting, formatting, version control, stakeholder review packaging — not by the actual thinking the team had to do about assumptions and outcomes. AI-native impact platforms collapse the document mechanics into hours. A program team can have a working draft logic model from a one-page program description and a 30-minute conversation. The team's thinking still has to do the load-bearing work — but the thinking now happens against a draft rather than against a blank page, and the iteration cycle compresses from weeks to days.

The shift is not "AI replaces the team's thinking." The shift is "AI handles the drafting and document mechanics so the team's thinking goes into the parts that matter — the assumptions, the outcome priorities, the honesty about which links are evidence and which are aspiration." The logic model that emerges has the same components, the same if-then chain, and the same Kellogg-canonical structure. It just arrives in days, and it stays current as program data flows in.

UNTIL ~2023 · BUILD

Four to six months of workshops
Consultant engagement and drafts
Board review cycles
Filed in a shared drive
Refreshed at major milestones
Disconnected from live program data

2026 · KEEP ALIVE

Working draft in days
AI handles drafting and mechanics
Team focuses on assumptions and priorities
Lives as a queryable record
Updates as data flows in
Connected to persistent program IDs

This shift has been Sopact's day job since 2014 — well before the generative AI category had a name and well before the term AI-native impact platform had a category to anchor to. The components did not need to change. The build infrastructure underneath them did.

SECTION 08 · BEST PRACTICES

AI changed everything in logic model construction. Two best practices follow.

For four decades the dominant best practice was commit to the six-month build and do it right. Stakeholder workshops, consultant facilitation, multiple draft cycles, board review. The advice was sound because the work of articulating assumptions, drafting components, and securing alignment took months when done manually. In 2024 and 2025 that quietly stopped being defensible. Substrate-layer platforms now generate a working logic-model draft from a program goal and a short interview, then keep that draft current as program data flows in. Once that becomes operationally cheap, the old best practice retires and two new ones replace it.

BEST PRACTICE 01

Start with what matters — outcomes first, gradually layer the rest.

The classical logic-model build started with whatever inputs the team could remember and reasoned forward into whatever activities they already ran. The diagram that emerged justified the existing program rather than testing it. The newer practice starts at the right end of the chain — name the impact the program is contributing to, name the outcomes that would make that impact plausible, and then work backwards through outputs, activities, and inputs. Only the parts the team can be specific about get drafted in detail at first. The rest gets filled in as evidence accumulates.

This is not a stylistic preference. It is the order that produces logic models that hold up under funder and evaluator review. Working backwards forces the team to answer "what are we trying to change?" before "what are we doing?" — which is the order honest evaluation runs in.

BEST PRACTICE 02

Let AI handle framework completion and reporting automation.

The parts of the classical logic-model build that took the most time were not the parts that required the team's hardest thinking. They were document mechanics — drafting, formatting, version control, packaging for stakeholder review, reconciling edits across drafts. That work is now suited to AI assistance. A program lead can describe the program goal in plain language; an AI-native impact platform can draft the full five-component chain with reasonable specificity; the team's review time goes into refining the assumptions and the outcome priorities rather than into wordsmithing the components.

The same dynamic applies to reporting. The traditional pattern wrote logic-model-aligned funder reports by hand at every cycle. The AI-native pattern generates draft reports from live program data joined to the logic-model structure — the team reviews and adjusts rather than starting from a blank document. Two disciplines, one substrate.

THE PRODUCTION-READINESS MOAT

Could you prompt your way to a logic-model draft for one program with Claude or ChatGPT? Yes. Could you vibe-code an impact substrate that keeps the model alive across five years of grantee data?

That is a fundamentally different problem. A working impact substrate has to handle three things at once that no notebook prototype handles:

01 · LONGITUDINAL

The same program ID at year five as at year one. Outcome cohorts traceable across grant cycles. Outputs and outcomes scored continuously, not just at proposal time and final report.

02 · MULTI-DIMENSIONAL

Quantitative outputs and qualitative narratives on one identifier. Participant survey scores, interview transcripts, validated instrument results, and uploaded documents all live on the same program record and join at write time.

03 · AUDIT-GRADE

Every outcome claim traces back to a specific piece of evidence. Citations down to the source — the survey response, the assessment score, the interview quote. Funders, boards, and auditors can verify any claim in the model.

This has been Sopact's day job since 2014 — well before the generative AI category had a name. The naming of the problem has changed. The architectural shape of the work has not.

The next section names the four structural principles that make these best practices operational rather than aspirational. The section after that traces them through four eras of logic-model tools so you can locate your current stack in the picture.

SECTION 09 · THE PRINCIPLES

Four principles of AI-native logic model practice

If the goal is a logic model that stays alive across the program lifecycle rather than a diagram filed at proposal time, four structural commitments do the work. None of these are AI in the generative sense — they are architecture decisions an AI-native impact platform makes at the substrate layer. Without them, the practice collapses back into the build-once-and-file-it pattern.

01

Persistent program ID

Each program receives one unique identifier the first time it enters the system. Every participant record, output count, outcome measurement, interview transcript, and uploaded document attaches to it for the entire program lifecycle — proposal through completion through follow-on cycles. Identity persists through funder changes, leadership transitions, and curriculum revisions. The logic model stays current because the underlying record does.

02

Clean-at-source capture

Validation, ID assignment, and structure are enforced at the moment of capture — not corrected later in a spreadsheet. Every output count has a date and a source. Every outcome measurement has a baseline. Every qualitative response is coded against the logic model's outcome categories in real time. The reporting stage stops being a cleaning project. Funder reports come from the data rather than being reconstructed from exports two months after the cycle closed.

03

Multi-modal evidence

Text, voice, video, image, document, rating scale, and behavioral telemetry live in the same program record on the same ID. Long PDFs from participants become structured variables. Interview audio becomes coded themes. Assessment scores become time series. The artificial separation between "qualitative outcome" and "quantitative output" dissolves because the substrate accepts both shapes natively and joins them on the participant ID.

04

Continuous model refresh

The logic model itself runs as a view on live data rather than a static document. Output counts update as participants enroll. Outcome scores update as assessments complete. The if-then chain stays visible — and the links that are not holding up under live data surface as alerts rather than as surprises at the year-end report. The model becomes the discipline it always claimed to be.

SECTION 10 · TOOLS

Four eras of logic model software and tools

Logic model software is not a single market — it is four eras of tooling stacked on top of each other. Most organizations run a combination from at least two. Knowing which era each tool belongs to clarifies why some categories are commoditized and why AI-native impact platforms are still being defined.

ERA DOMINANT TOOLS WHAT IT SOLVED WHAT STAYED HARD
FOUNDATION TEMPLATES
(pre-2010)
Kellogg Foundation 2004 Logic Model Development Guide · CDC templates · United Way templates · PowerPoint and Word forms. Standardized the five-component structure. Free, accessible, well-documented. Worked for one-off proposals. Static at the moment of completion. No connection to program data. Maintained manually if at all.
DIAGRAM SOFTWARE
(2010s)
Lucidchart · Miro · Microsoft Visio · SmartDraw · Canva templates · Mural. Collaborative diagramming. Version history. Easier to update than printed templates. Logic-model templates built in. Each diagram still a static snapshot. No participant data behind it. Output counts and outcome measurements lived elsewhere — surveys, spreadsheets, evaluation reports — and never joined to the model.
EVALUATION & CRM PLATFORMS
(late 2010s)
DevResults · Salesforce Nonprofit Cloud · Apricot by Bonterra · Civicore · Tableau dashboards · Smartsheet. Structured logic-model fields connected to participant records. Some longitudinal tracking. Built-in reporting. Logic model fields sat next to data but did not analyze themselves. Logic-model construction still required manual workshops. Reports still required manual assembly.
AI-NATIVE IMPACT
(2024 →)
Platforms with persistent program IDs, AI-assisted logic-model drafting, multi-modal evidence capture, continuous model refresh. Sopact Sense is in this category. Compresses logic-model build from months to days. Joins quantitative outputs to qualitative narratives on shared IDs. Generates draft funder reports from live data. Migration from era-three platforms requires real work — typically two to four weeks of program record standardization before the first clean cycle.

Era-four platforms do not replace the era-two diagramming market. Lucidchart and Miro remain the right tools when you need to draw a logic model for a board deck. What the AI-native layer adds is the substrate underneath the diagram — the persistent program ID and clean-at-source capture that let the model stay current rather than aging out within weeks of completion.

SECTION 11 · WHERE SOPACT FITS

What Sopact Sense actually does for logic models

Sopact has been building substrate-layer infrastructure for impact data since 2014 — well before AI-native impact platform became the category it is now. The product, Sopact Sense, is not a diagramming tool with a logic-model template bolted on. It is a purpose-built impact substrate that drafts the full logic-model structure from a program description, captures participant evidence on a persistent program ID, codes qualitative responses against the outcome categories, and keeps the model alive as data flows in.

Three layers of analysis run continuously on the same program record. Intelligent Cell extracts summaries, themes, sentiment, and rubric scores from a single response, transcript, or document. Intelligent Row generates a per-participant brief from everything that participant has submitted across the program lifecycle. Intelligent Column links themes and outcome measurements across the entire participant population, surfacing pattern shifts that would take weeks to find by hand. The three together replace the surveys-plus-spreadsheets-plus-PowerPoint stack with one connected system, with the logic model as the structural backbone.

For programs managing 50–5,000 participants over a multi-year lifecycle — workforce programs, foundation grant cycles, public health interventions, education initiatives — the structural fit is direct. For a one-off proposal logic model, Sopact Sense is overbuilt; a Lucidchart diagram is the right choice. The deeper product architecture is described on the Sopact Sense pillar; the upstream theory framework sits at theory of change; the data-collection layer that feeds outcome measurement is at data collection methods.

SECTION 12 · QUESTIONS

Frequently asked questions

Eighteen questions that come up on logic-model planning calls, framed for the practitioner audience this guide is written for. Each answer is short enough to act on.

What is a logic model?

A logic model is a visual diagram showing how a program's inputs, activities, outputs, outcomes, and impact connect in an if-then chain. It is the standard tool program designers, evaluators, and funders use to articulate what a program does, what it produces, and what change it is meant to create. The W.K. Kellogg Foundation's 2004 Logic Model Development Guide is the most widely cited version, and the five-component structure — inputs, activities, outputs, outcomes, impact — has been the canonical shape for two decades.

What are the components of a logic model?

A logic model has five canonical components in left-to-right order. Inputs are the resources committed to the program — funding, staff, materials, partnerships, time. Activities are what the program does with those inputs — workshops delivered, services provided, curriculum taught. Outputs are the direct, countable products of activities — number of participants served, hours of training delivered, documents produced. Outcomes are the changes that result for participants — short-term changes in knowledge or attitude, medium-term changes in behavior, long-term changes in condition. Impact is the broader, longer-term societal or systemic change the program contributes to.

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

Inputs are what goes into the program — resources committed before any work happens. Outputs are what comes out of the activities — countable products of the work done. Inputs are about resourcing the program. Outputs are about quantifying the work the program produced. A grant of $200,000 is an input. The 150 participants who completed the training funded by that grant is an output.

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

Outputs are the countable products of activities — how much was delivered. Outcomes are the changes that resulted — what changed for participants because of the delivery. 150 participants trained is an output. 90 of those participants placed in jobs within 90 days at a wage above their previous earnings is an outcome. The output question is "what did we do?" The outcome question is "what changed because we did it?"

What is the difference between a logic model and a theory of change?

A theory of change is the narrative reasoning about why a program should work — the assumptions, the causal pathways, the contextual factors. A logic model is the operational diagram of how the program will work — inputs flowing through activities into outputs, outcomes, and impact. Theory of change answers why and under what conditions. Logic model answers what and in what sequence. Strong programs build both: theory of change first to articulate the reasoning, logic model second to operationalize the delivery. See theory of change for the upstream framework.

What is the W.K. Kellogg Foundation logic model?

The W.K. Kellogg Foundation logic model is the version published in the foundation's 2004 Logic Model Development Guide, which became the most widely adopted logic model framework for nonprofits, public health programs, and education initiatives. It uses the five-component structure (inputs, activities, outputs, outcomes, impact) and introduces the if-then chain — the explicit logic that if these inputs are committed, then these activities can happen; if these activities happen, then these outputs result; and so on through outcomes and impact.

What is the if-then chain in a logic model?

The if-then chain is the causal logic that connects the five components of a logic model. Reading left to right: if these inputs are committed, then these activities can be delivered. If these activities are delivered, then these outputs will be produced. If these outputs are produced, then these outcomes will follow for participants. If these outcomes occur at sufficient scale, then this broader impact will be contributed to. The if-then chain forces program designers to articulate the assumptions linking each step — and to identify which links are evidence-based and which are aspirational.

How do you build a logic model?

Build a logic model in five steps. 1) Start with the impact and work backwards — name the long-term societal or systemic change the program is contributing to. 2) Identify the outcomes that would have to occur for that impact to be plausible. 3) Specify the outputs that would have to be produced to drive those outcomes. 4) List the activities that would produce those outputs. 5) Enumerate the inputs required to run those activities. The reverse-order build prevents the common failure mode of starting with available inputs and reasoning forward into whatever fits.

What is a logic model example for a nonprofit?

A workforce-training nonprofit logic model: Inputs include $400K grant funding, 4 instructors, partnerships with 12 employers, a curriculum, and a community space. Activities are recruitment, 12-week training cohorts, employer matching events, and post-placement coaching. Outputs are 200 participants enrolled, 160 completing the program, 12 employer matching events held, and 6 months of post-placement coaching delivered. Outcomes are 120 participants placed in jobs within 90 days, average wage of $24/hour (vs $16 pre-program), 80% retention at 6 months. Impact is reduced regional underemployment, increased family economic stability for participants' households, and a replicable model for peer nonprofits. Four full worked examples appear in the Examples section above.

What software is used to build logic models?

Logic model software falls into four eras. PowerPoint and Word templates from foundations like Kellogg and CDC are still used for one-off models. Diagram tools like Lucidchart, Miro, and SmartDraw handle the visualization layer with logic-model templates built in. Evaluation platforms like DevResults, Salesforce Nonprofit Cloud, and Tableau dashboards include logic-model fields but do not automate construction. AI-native impact platforms — Sopact Sense in this category — replace the six-month logic-model project with an outcome-first design that generates the full inputs-to-impact chain from a short program goal and keeps it updated as program data flows in.

Can AI build a logic model?

AI can do meaningful work on logic models — and cannot do all of it. Generative AI tools like ChatGPT, Claude, and Perplexity can draft a logic model from a program description, suggest outcomes from impact statements, and identify gaps in the if-then chain. They cannot maintain that logic model as live program data flows in, validate outputs against actual program delivery, or join the model to participant-level outcomes. The strong pattern is partnership: an AI-native impact platform manages the persistent program record and the data joins; the generative model drafts and refines the logic-model content.

How long does it take to build a logic model?

Traditional logic-model projects ran four to six months — staff workshops, consultant engagement, multiple draft rounds, board approval cycles. The classical W.K. Kellogg Foundation development guide assumed this timeline because the manual work of articulating assumptions, drafting components, and securing stakeholder alignment took months. AI-native platforms compress the initial build to days. The shift is not "AI replaces the team's thinking" — it is "AI handles the drafting and document mechanics so the team's thinking goes into the parts that matter, the assumptions and the outcome priorities."

What is a logic model in grant writing?

In grant writing, a logic model is the diagram that demonstrates to funders how the proposed program will work — how the grant funding (inputs) will be converted into activities, outputs, outcomes, and impact. Most major foundations and federal funders require a logic model as part of proposal submissions. A strong grant-writing logic model is specific, evidence-based on the if-then links, and clearly distinguishes outputs from outcomes — the most common reviewer critique.

What is a logic model in program evaluation?

In program evaluation, a logic model is the foundation document that defines what the evaluation will measure. The model identifies which outputs the evaluation will count, which outcomes it will assess change against, and which impact-level indicators it will track over time. Evaluation plans that lack a logic model tend to drift toward measuring whatever data is convenient to collect rather than whatever data answers the question "did the program produce its intended changes."

What are inputs in a logic model?

Inputs in a logic model are the resources committed to make the program possible. Categories include financial inputs (grants, contracts, donations), human inputs (staff, volunteers, consultants), material inputs (curriculum, facilities, equipment, technology), and relational inputs (partnerships, community ties, regulatory permissions). Strong logic models list inputs at sufficient specificity that a reader can answer "is this program adequately resourced?" Vague inputs ("funding, staff") signal a logic model that has not yet been costed against the work it proposes.

What are outputs in a logic model?

Outputs in a logic model are the direct, countable products of program activities — quantifying what the program produced. Examples: number of participants served, hours of training delivered, services provided, materials distributed, events held, reports published. Outputs answer "how much did we do?" They are necessary but not sufficient — strong programs distinguish outputs from outcomes because output achievement does not by itself demonstrate impact. A program that delivered 500 training hours achieved high output. Whether those hours produced learning, behavior change, or placement is an outcome question.

What are outcomes in a logic model?

Outcomes in a logic model are the changes that result for participants because of program activities. Outcomes are typically grouped by time horizon. Short-term outcomes are changes in knowledge, attitude, or skill (a participant learned the concept). Medium-term outcomes are changes in behavior or practice (the participant applied the concept). Long-term outcomes are changes in condition or status (the behavior change produced a sustained life change). Outcomes are where impact measurement actually lives. Programs that confuse outcomes with outputs systematically over-report success.

What is impact in a logic model?

Impact in a logic model is the broader, longer-term societal or systemic change the program contributes to — the fundamental shift the program is part of producing alongside other actors and forces. Impact is typically beyond the reach of any single program in isolation. A workforce program contributes to regional economic mobility. A literacy program contributes to community educational attainment. A health intervention contributes to disease-burden reduction. Impact is contribution rather than attribution — the program is one of many factors moving the larger system.

SECTION 14 · NEXT

Build your logic model in days, not months. Then keep it alive.

A 30-minute walkthrough on your actual program — your inputs, your outcomes, your impact. Working draft logic model from a program description and a conversation. Persistent program ID. Continuous refresh as participants enroll. No deck. No generic demo. Your real program, on one substrate.