Nonprofit Programme Assumptions Log
This is a practical guide to building a assumptions log for a nonprofit programme project — a register of the assumptions the plan depends on, to be validated, adapted to the realities of delivering a nonprofit or grant-funded programme.
What a Assumptions Log is
A assumptions log is a register of the assumptions the plan depends on, to be validated. For the full concept and how it works in general, see Project Assumption. On a nonprofit programme project it plays the same role, tuned to this kind of work.
Why it matters for a Nonprofit Programme project
Nonprofit Programme projects live or die on delivering a nonprofit or grant-funded programme. A well-built assumptions log gives the team a shared, explicit reference for exactly that — reducing ambiguity, aligning stakeholders, and making problems visible early enough to act. Skipping it, or doing it generically, is how nonprofit programme projects drift into avoidable delay and cost.
What to include
- Assumption
- Impact if wrong
- Owner
- Validation status
Nonprofit Programme-specific considerations
Tailor the assumptions log to the risks that most often derail nonprofit programme projects:
- Funding constraints
- Volunteer coordination
- Impact measurement
Example
On a real nonprofit programme project, the assumptions log would be shaped by delivering a nonprofit or grant-funded programme. In particular, it should explicitly account for the project’s biggest risks — funding constraints, volunteer coordination, impact measurement — rather than treating them as afterthoughts.