Theory of Change Annual Refresh Workshop Notes
Use this workshop notes template to capture annual Theory of Change updates, including changed assumptions, revised preconditions, and pathway decisions. It gives program leadership and evaluation teams a clear record of what changed and why.
Trusted by frontline teams 15 years of frontline software
Built for: Nonprofit · Public Sector · Education · Healthcare · Social Impact
Overview
This template captures notes from an annual Theory of Change refresh workshop. It is designed to record the current context, the assumptions the team still believes, the preconditions that need to be true, the pathways that were revised, and the decisions made about what to keep, change, or test next.
Use it when leadership, program, and evaluation teams need a shared record of how the program logic evolved over the year. It works well for annual planning, grant cycles, board preparation, and evaluation reviews where the team needs to explain why the theory changed and what evidence or experience informed the update. The template also helps separate discussion from outcome so the final notes are easier to act on later.
Do not use it as a generic meeting notes page for routine status updates. It is not meant for day-to-day project tracking, and it is not a substitute for a full logic model or evaluation plan. If the workshop is only about operational tasks, a simpler agenda or action-item template is a better fit. This template is most useful when the meeting is explicitly about revisiting the program’s causal story and documenting the refresh in a way that can be reused in strategy, reporting, and evaluation work.
Standards & compliance context
- If the workshop informs grant reporting or formal program documentation, keep the notes aligned with the organization’s approved terminology and record-retention practices.
- When the Theory of Change supports an evaluated intervention, document the rationale for changes so the audit trail between discussion and revision remains clear.
- If participant data or sensitive stakeholder feedback is discussed, avoid including unnecessary personal details in the notes and store only what the team needs for the record.
- For public-sector or regulated programs, confirm that any revised pathway or assumption does not conflict with required service standards, reporting rules, or approval processes.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
How to use this template
- Start by adding the workshop date, program name, and the version of the Theory of Change being reviewed so the notes are tied to a specific annual refresh.
- Record the agenda item for each part of the workshop, including context review, assumptions, preconditions, pathway changes, and any measurement or evidence questions.
- Capture the discussion in plain language, separating what the group observed from what they decided, and note any blockers, disagreements, or unresolved questions.
- Write each decision as a clear outcome statement, then list action items with an owner and due date so follow-up work does not get lost after the workshop.
- Review the notes at the end of the session with the group, confirm the next time the theory will be revisited, and save the final version for leadership and evaluation use.
Best practices
- Write the current context first so later changes to assumptions and pathways can be understood against the conditions that triggered the refresh.
- Distinguish between evidence-based changes and judgment calls, because the team will need that distinction when explaining the update to funders or evaluators.
- Capture one decision per line whenever possible so the record stays easy to scan and action items can be linked to the exact outcome.
- Assign every action item to a named owner with a due date, even if the task is only to gather more evidence or draft a revised pathway.
- Note unresolved disagreements explicitly instead of smoothing them over, since contested assumptions are often the most important follow-up from the workshop.
- Keep the summary focused on what changed, what stayed the same, and what will be tested next, rather than rewriting the entire Theory of Change.
- Use consistent language for assumptions, preconditions, outputs, and outcomes so the annual refresh can be compared to prior versions without confusion.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What is this template for?
This template is for documenting an annual Theory of Change refresh workshop. It captures the current context, the assumptions being tested, the preconditions that still hold, and any pathway changes agreed by the group. It is meant to produce a usable record for program leadership, evaluation teams, and other stakeholders who need to understand what changed and why.
When should we use this instead of regular meeting notes?
Use it when the meeting is specifically about reviewing and updating a Theory of Change, not for routine program check-ins. It is especially useful after a year of implementation, before a new planning cycle, or when external conditions have shifted enough to warrant a formal review. If the goal is only status reporting, a simpler agenda or general notes template is usually enough.
Who should run the workshop and fill this out?
A program lead, strategy lead, or evaluation lead usually facilitates the workshop and captures the notes. The best results come when the person recording the notes can distinguish between context, discussion, decisions, and follow-up actions. If the workshop includes many voices, assign one note-taker and one facilitator so the record stays clear.
How often should a Theory of Change refresh happen?
Annual review is the most common cadence, which is why this template is framed for a yearly workshop. Some programs may also refresh after a major funding change, policy shift, or evaluation finding that affects the logic model. The key is to revisit it often enough that the Theory of Change reflects actual practice rather than an old planning artifact.
What should we record as a decision versus a discussion point?
A decision is something the group agreed to change, keep, or test further, such as revising a pathway or updating a precondition. A discussion point is a topic that was explored but not resolved, such as a contested assumption or a data gap. Separating the two helps the team leave with a clear outcome and a clean list of action items.
What are the most common mistakes when using this template?
The most common mistake is writing only narrative notes and failing to capture the actual changes to assumptions, preconditions, and pathways. Another pitfall is skipping ownership, which leaves follow-up work vague and easy to miss. Teams also sometimes confuse the program strategy with the evidence base, so it helps to note whether a change is based on data, stakeholder feedback, or judgment.
Can this template be customized for different program types?
Yes. You can adapt the sections to match a grant-funded program, nonprofit initiative, public-sector intervention, or research-backed service model. The core structure should still preserve context, discussion, decisions, and action items so the workshop output remains easy to review later. You can also add prompts for equity considerations, outcomes, or measurement questions if those matter to your team.
How does this connect to evaluation or reporting tools?
This workshop record can feed directly into evaluation plans, board updates, grant reporting, and strategy documents. It helps teams explain why indicators, outcomes, or pathways changed over time, which is useful when aligning with monitoring and evaluation work. If your team uses a separate logic model or theory-of-change diagram, this notes template provides the change log behind that artifact.
Related templates
Go deeper on the topic
-
Healthcare employee engagement ideas to reduce burnout, boost retention, and improve patient outcomes in your health system.
-
Boost healthcare employee engagement with proven ideas that reduce burnout, improve retention, and elevate patient care.
-
Hospital recognition programs boost staff morale, reduce turnover, and improve patient care for stronger healthcare outcomes.
-
See how automated credential checks, labor rules, and real-time coverage tracking give charge nurses a schedule they can trust before every shift.
Ready to use this template?
Get started with MangoApps and use Theory of Change Annual Refresh Workshop Notes with your team — pricing built for small business.
