What if our Theory of Change changes later?

How to update and revise your Theory of Change as your project evolves.

Last updated: February 18, 2025

Theory of Change Updates

Managing Evolution and Adaptation

Understanding when and how to update your Theory of Change to reflect learning, changing contexts, and evolving strategies.

The Dynamic Nature of Change

1

Living Document

Your Theory of Change is designed to evolve:

  • It represents your best understanding at a point in time
  • Implementation experience provides new insights
  • Contexts and conditions change over time
  • New evidence may challenge initial assumptions
  • Stakeholder perspectives may evolve
  • Project scope or focus may shift
  • Learning should inform continuous improvement
2

Update Flexibility

The platform supports this evolution:

  • Updates can be made whenever necessary
  • Minor refinements can be implemented directly
  • Documentation of changes is automatically maintained
  • Version history is preserved for reference
  • Learning notes can be attached to elements
  • Comparison between versions is available

You can update your Theory of Change at any time. Significant updates will require a new review and approval cycle to ensure accuracy and traceability.

Types of Updates

1

Minor Updates

Small changes that don't alter the fundamental approach:

  • Clarifying language or descriptions
  • Refining indicator metrics
  • Updating baseline information
  • Adding supporting documentation
  • Correcting errors or inconsistencies
  • Improving visual presentation
  • Adding explanatory notes
  • Updating implementation timelines
2

Significant Updates

Substantial changes that modify core elements:

  • Adding or removing key activities
  • Changing expected outputs or outcomes
  • Modifying causal pathways between elements
  • Revising fundamental assumptions
  • Altering domain categorizations
  • Changing primary stakeholder groups
  • Expanding or narrowing project scope
  • Restructuring the overall logic model

When considering whether an update is minor or significant, ask yourself: "Does this change how we understand what we're doing, why we're doing it, or how we think change will happen?" If yes, it's likely a significant update requiring review.

When to Update Your Theory of Change

1

Regular Review Points

Scheduled opportunities to consider updates:

  • Annual planning cycles
  • Mid-term and final evaluations
  • After significant monitoring milestones
  • During strategy refresh periods
  • At project phase transitions
  • When preparing new funding proposals
  • During organizational learning events
  • When stakeholder feedback is systematically collected
2

Responsive Update Triggers

Situations that may prompt unscheduled updates:

  • Significant context changes (political, environmental, economic)
  • New evidence challenging key assumptions
  • Unexpected implementation barriers or opportunities
  • Stakeholder feedback revealing gaps or misconceptions
  • Monitoring data showing unexpected results
  • Resource changes affecting implementation scope
  • New partnership opportunities
  • Emergent risks or challenges

While updating is important, avoid excessive changes that create instability or confusion. Aim for a balance between responsiveness to new information and maintaining consistent direction in your work.

The Update Process

1

Documenting Rationale

Before making changes, document:

  • What specific elements need updating
  • Why the update is necessary
  • What evidence supports the change
  • Who has been consulted about the change
  • How the change affects other elements
  • What implications exist for implementation
  • How progress measurement may be affected
  • How historical data will be handled
2

Making Updates

Follow these steps when implementing changes:

  • Enter edit mode for your Theory of Change
  • Make the necessary modifications
  • Add explanatory notes to document rationale
  • Save your changes as a draft
  • Preview the updated version
  • Request review if changes are significant
  • Submit the updated version

For minor updates, the review process may be abbreviated. However, significant changes will go through the full review and approval workflow to ensure quality and alignment.

Review Requirements for Updates

1

Minor Update Review

The streamlined process for small changes:

  • Notification to your LEVEL Account Manager
  • Technical review for consistency
  • Documentation of changes in the system
  • Confirmation of continued compliance
  • Update to version history
  • Notification to team members
2

Significant Update Review

The full process for substantial changes:

  • Complete review by team members with permissions
  • Technical assessment by your LEVEL Account Manager
  • Verification of evidence supporting changes
  • Evaluation of impacts on reporting and compliance
  • Formal approval by organizational management
  • Update to version history with detailed change log
  • Notification to all stakeholders

When initiating a significant update, schedule a consultation with your LEVEL Account Manager first. They can provide guidance on the review process, highlight potential compliance implications, and help you plan for a smooth transition.

Maintaining Continuity Through Changes

1

Version Management

Practices for effective handling of multiple versions:

  • Clear naming conventions for versions
  • Comprehensive documentation of changes
  • Preservation of previous versions
  • Clear indication of current operational version
  • Mapping between corresponding elements across versions
  • Transition plan for implementation changes
  • Communication strategy for stakeholders
2

Reporting Considerations

Addressing reporting needs when changes occur:

  • Document how indicators relate across versions
  • Plan for data continuity where possible
  • Note reporting breakpoints where continuity isn't possible
  • Provide context notes explaining shifts in reporting
  • Maintain historical data with version references
  • Consider parallel tracking during transition periods
  • Update reporting templates and guides

When making significant changes to outcome pathways or indicators, consider the implications for your ability to demonstrate progress over time. Where possible, maintain comparable measurement approaches or document clearly why and how measurement approaches have changed.

Learning Through Updates

The update process itself creates valuable learning:

  1. Document the journey from initial design through each iteration
  2. Capture key insights that prompted changes
  3. Note assumptions that proved accurate or inaccurate
  4. Track shifting contexts and their influence on your approach
  5. Identify recurring themes in updates that may indicate systematic issues

The history of your Theory of Change updates tells an important story about your learning and adaptation. This narrative can be as valuable as the current version, demonstrating how your understanding of change processes has evolved based on experience and evidence.

Was this article helpful?