01 · What breaks
Design for the failure modes, not only the happy path.
The value of theory of Change to data model guide depends on what happens when records are incomplete, evidence conflicts or the next action carries consequence.
One table for every diagram box
Make this visible in testing, ownership and review rather than leaving it as an implementation surprise.
Proxy indicators treated as outcomes
Make this visible in testing, ownership and review rather than leaving it as an implementation surprise.
Context and assumptions omitted
Make this visible in testing, ownership and review rather than leaving it as an implementation surprise.
Collecting fields nobody reviews
Make this visible in testing, ownership and review rather than leaving it as an implementation surprise.
02 · Minimum viable model
Start with outcome claim linked to programme evidence and the decisions around it.
The smallest useful model for this page connects the following records. Each field should have a purpose, owner and retention rule.
03 · Implementation sequence
Move through reviewable gates.
A complete small workflow is safer and more useful than a large collection of unfinished modules.
Mark the decisions the theory should inform
Agree the owner, evidence and exit condition before moving forward.
Identify units and relationships
Agree the owner, evidence and exit condition before moving forward.
Map outcomes to observable evidence
Agree the owner, evidence and exit condition before moving forward.
Define timing and attribution limits
Agree the owner, evidence and exit condition before moving forward.
Design the minimum source workflow
Agree the owner, evidence and exit condition before moving forward.
Test whether teams can maintain it
Agree the owner, evidence and exit condition before moving forward.
04 · Evidence
Measure whether the work became clearer.
Usage alone is not success. Review the quality, timeliness and decisions the system is meant to improve.
05 · Responsible automation
Let systems prepare. Keep consequence with people.
Systems can support
- Identify units and relationships
- Map outcomes to observable evidence
- Define timing and attribution limits
- Design the minimum source workflow
People should decide
- Accepting an outcome claim
- Interpreting contribution
- Changing the programme theory
- Deciding what not to collect
06 · Common questions
Practical questions teams ask.
Use these answers to clarify scope, compare approaches and identify the decisions your team needs to make before implementation.
How should a nonprofit use the Theory of Change to data model guide?
Moving from a Theory of Change to a data model means identifying the actors, activities, outputs, outcomes, assumptions and decisions that need records—then removing everything the programme cannot collect or use responsibly. The result is not a database version of every box in the diagram.
What fields or sections should the Theory of Change to data model guide contain?
Start with outcome claim linked to programme evidence. The minimum useful record set covers actor and unit of analysis, activity and service delivery, output and immediate result, outcome observation and timing, assumption, risk and context and indicator, source and decision owner. Remove any field that does not support a service, safeguard, decision or reporting obligation.
Who should complete and maintain the Theory of Change to data model guide?
The team that owns outcome claim linked to programme evidence should maintain the resource, with input from frontline, programme, MEL or data, technology and leadership roles as relevant. Keep one named owner responsible for version control, review decisions and updates.
How can the Theory of Change to data model guide be adapted for different programme sizes?
Keep the definition of outcome claim linked to programme evidence stable at every scale. A small programme can begin with one workflow and a few roles; a multi-state programme also needs delegated ownership, stronger permissions, shared definitions, integration rules and location-level quality review.
How can a team check that the Theory of Change to data model guide is complete and useful?
Keep the source, definition, time, owner, status and review decision together. Monitor outcomes linked to source records, indicators with owners and definitions, assumptions reviewed and unused collection removed, and preserve limitations instead of cleaning them out of the report.