A logic model is a simple visual diagram showing how your nonprofit connects inputs, activities, outputs, and outcomes. Think of it as your theory of change in a single image. It answers the question: "If we do X, Y, and Z, then this change happens."
The beauty of a logic model is that it forces clarity. You can't hide vague thinking in a logic model. Either the cause-and-effect chain makes sense, or it doesn't.
Why Logic Models Matter
Logic models aren't just academic exercises. They're tools that help you:
- Align your team Everyone agrees on what you're trying to do and why.
- Identify measurement gaps What you thought you were measuring might not match your actual outcomes.
- Explain your work simply New staff, board members, and funders understand your approach instantly.
- Plan strategically When you see your entire theory on one page, decisions become clearer.
- Build partnerships Potential partners see exactly where collaboration makes sense.
The Five-Box Logic Model
The standard format uses five boxes connected by arrows. Don't overthink this. The boxes are:
1. INPUTS What resources do you have? Staff, funding, volunteers, partnerships, facilities, curriculum. Be specific. "A $200,000 annual budget" not "significant resources."
2. ACTIVITIES What do you do with those inputs? Teach classes. Provide counseling. Distribute food. Host workshops. Run support groups. List your core activities, not peripheral ones.
3. OUTPUTS Who do you reach and in what numbers? "Serve 150 youth per year." "Conduct 200 counseling sessions." "Reach 5,000 people through awareness campaigns." Outputs are countable and immediate.
4. OUTCOMES (Short-term) What changes happen as a direct result? "Participants increase their reading level by one grade." "Clients reduce substance use." "Parents report improved financial knowledge." Outcomes are the changes you seek.
5. IMPACT (Long-term) What lasting change happens? "Youth graduate high school on time." "Families achieve housing stability two years after program." "Graduates maintain employment." Impact is what happens far down the road, often outside your direct reach.
The Cause-and-Effect Chain
The arrows connecting your boxes tell a story. The logic model says: Because we have these inputs, we can do these activities. Because we do these activities, we reach this many people. Because we reach them with this approach, they experience these outcomes. And because of these outcomes, they eventually achieve this impact.
Each arrow must be defensible. If there's no reasonable path from activity to outcome, you've identified a gap in your theory. That's exactly what you want to find.
Running a Logic Model Workshop
You can build a logic model with your team in a single 2-hour session. Here's how:
Pre-Workshop (30 minutes before) Invite 5-10 people representing different parts of your organization: program staff, board member, executive director, finance person if possible. Send them a simple one-page overview of what you're doing. No one should walk in cold.
Intro (10 minutes) Explain the five boxes and show a simple example from another nonprofit in your sector. Not your organization yet—just the concept.
Round 1: Inputs (15 minutes) On a large sheet of paper or whiteboard, write "INPUTS" and brainstorm. What resources does your organization have? Budget? Staff? Partnerships? Community relationships? Write everything down. Don't edit yet.
Round 2: Activities (20 minutes) Given those inputs, what do you do? What are your core programs and services? Be specific. "We run job training" isn't specific enough. "We run a 12-week digital marketing skills program taught by industry professionals" is better.
Round 3: Outputs (15 minutes) Who do you serve and how many? How many people participate in each activity? What's the reach?
Break (5 minutes)
Round 4: Outcomes (25 minutes) This is the hardest part. If your programs work as intended, what changes do participants experience? Not outputs (they showed up). Changes (their knowledge, skills, attitudes, behavior, or circumstances shift). Ask: "Six months after the program, what's different about participants?" Use data you already have or participant feedback.
Round 5: Impact (15 minutes) Fast forward two or five years. If your outcomes happen, what's the lasting result? This is aspirational. You don't have data yet. But what's the long-term change you're working toward?
Review and Refine (15 minutes) Look at the entire model. Does the story make sense? Are the arrows logical? Do you believe that if all these pieces happen, the impact will follow? Refine language. Remove jargon.
Common Mistakes in Logic Models
Mistake 1: Confusing Outputs and Outcomes "We serve 200 people" is an output. "Participants increase their skills by 30%" is an outcome. Your model should have both, but don't mix them.
Mistake 2: Making It Too Complicated Five boxes maximum. If you need more boxes, you're doing multiple things. Break it into separate models.
Mistake 3: Using Vague Language "Increase well-being" is too vague. "Participants report 25% improvement in mental health scores" is specific. Funders and your team need specificity.
Mistake 4: Ignoring Context Logic models exist in a context. External factors (the economy, policy changes, community conditions) affect your outcomes. A good logic model acknowledges these.
Mistake 5: Never Updating It Your organization changes. Your programs evolve. Your logic model should too. Review it annually. Doesn't have to be perfect—it just has to be true.
From Logic Model to Strategy
A logic model isn't your strategic plan. But it informs it. Once you have a clear model, you can ask strategic questions:
- Where is our measurement weakest? (That's where to invest in data collection.)
- What activities don't connect to outcomes? (Maybe we should eliminate them.)
- Where could we partner? (Another organization might fill a gap.)
- What do we need to invest in? (If an activity is critical but underfunded, that's a resource question.)
See the lecture on Qualitative Impact Data to deepen your measurement approach once you have a logic model in place.
Making It Visual
After your workshop, someone should clean it up and make it visual. You don't need fancy design software. Canva, Google Drawings, or even PowerPoint will work. The goal is something you can use in:
- Staff onboarding documents
- Board presentations
- Grant proposals
- Strategic planning sessions
- Community presentations
Once it's clean and visual, share it. Reference it. Let it guide decisions. A logic model only matters if people actually use it.
The Messy Middle
After your workshop, you might realize the model doesn't quite capture what you do. That's normal. Messy models are real models. Overly clean models are usually oversimplified. Your model should spark conversation, not end it.
Use it as a working document. Post it in the office. Ask for feedback. Refine it quarterly. After a few months of use, you'll have something that actually represents your organization.
Frequently Asked Questions
Do we need a different logic model for each program?
Maybe. If your programs are totally separate with different outcomes, yes. If they're interconnected or serving the same population with different services, one organization-wide model might work. Start with one master model. If it gets too complicated, break it into program-specific models.
What if our activities don't clearly lead to outcomes?
That's the insight you wanted. That gap tells you something. Maybe your theory of change needs rethinking. Maybe you need a different activity. Maybe the activity is right but you're measuring the wrong outcome. Use this as a chance to strengthen your program design.
Should we include external factors?
Some organizations add a "context" box on the side noting external factors (policy, economy, community conditions) that affect the model. This is helpful if those factors significantly influence your outcomes. Otherwise, keep the core model simple.
How often should we update our logic model?
Review it annually or when your organization makes major changes. You don't need to rebuild it from scratch. Usually, minor tweaks to language or outcomes are sufficient. Major overhauls are rare unless your mission fundamentally shifts.
Can we use a logic model for a new program we're launching?
Absolutely. In fact, this is an ideal use. Build the logic model before you launch. It forces you to clarify what you expect to happen. Then use it to guide measurement and evaluation from day one.