Your organization makes assumptions before almost every grant application. Staff estimate how much the project may cost, whether a partner will participate, how many people can be reached, whether a donor will accept a certain approach, and how much time remains before the deadline. An assumption log helps your NGO or CBO make those guesses visible before they quietly become “facts” inside the proposal.
Capture assumptions before they enter the draft
Your team should record uncertain items during opportunity research and concept development. This is especially important when a decision depends on information that has not yet been verified. Once an assumption is written into a narrative or spreadsheet several times, people can forget that it was originally provisional.
Use an assumption log table
| Assumption | Why it matters | How to verify | Action if false |
|---|---|---|---|
| Partner will join | Affects scope and credibility | Written confirmation | Replace partner or redesign |
| Target of 1,000 people is feasible | Affects budget and results | Prior delivery and recruitment data | Reduce target or add capacity |
| Donor allows staff-time match | Affects co-financing plan | Official guidance or clarification | Find another match source |
| Equipment can arrive in 8 weeks | Affects implementation timing | Supplier lead time | Rephase activity or source locally |
Prioritize assumptions by decision impact
Your organization does not need to investigate every uncertainty with the same intensity. Focus on assumptions that affect eligibility, budget size, partner roles, beneficiary targets, major procurement, or organizational liability. Low-impact assumptions can remain provisional longer, while high-impact assumptions should be verified before leadership approves the bid.
Detailed example: an assumption that changes the entire funding model
Imagine your NGO is considering a USD 500,000 grant that requires a 20% contribution. The proposal team assumes that existing staff salaries can count toward half the match. That assumption is used to make the opportunity appear financially feasible.
If the donor later confirms that staff time is not eligible, your organization may suddenly need USD 50,000 in new cash or another approved contribution source. By logging the assumption early, the executive director can see that the financial model remains provisional and refuse to approve full drafting until the rule is verified.
Update or retire assumptions
Once an assumption is verified, mark the evidence and convert it into a confirmed requirement or fact. If it proves false, update every affected document instead of leaving the old value in the narrative, budget, workplan, or partner notes. The log should reduce inconsistency, not simply record uncertainty.
Assumption log checklist
- Material assumptions are recorded before drafting expands.
- Each assumption has a verification method.
- High-impact assumptions have short verification deadlines.
- False assumptions trigger updates across all affected files.
- Verified assumptions are converted into confirmed evidence.
- Leadership can see which proposal elements remain uncertain.
- Old assumptions are not silently carried into later applications.
What boards and institutional donors are likely to expect
Boards should know when a major application rests on unverified financial, partner, or delivery assumptions. Institutional donors may also test whether the applicant understands the basis of its targets and costs. A clear assumption log strengthens internal judgment because it shows where confidence is justified and where more evidence is still needed.
What to do next
Use the Should We Apply? Grant Checker to test whether unresolved assumptions are serious enough to change the bid decision. For practical funding intelligence, subscribe to Africads Grant News.
Frequently asked questions
What should go into a grant assumption log?
Record any material point the team is treating as true but has not yet verified, such as partner participation, eligible co-financing, target feasibility, supplier lead time, or donor interpretation.
Which assumptions should be verified first?
Prioritize assumptions that can change eligibility, budget, scope, partner roles, targets, or organizational liability. Low-impact uncertainties can remain provisional longer.
Who should own assumption verification?
Assign the person or function closest to the evidence: finance for cost and match assumptions, MEL for target and baseline assumptions, program for delivery assumptions, and partnership leads for partner commitments.
What happens when an assumption proves false?
Update every affected document and reconsider the bid if the change is material. Do not leave the old assumption embedded in the narrative, budget, workplan, or partner notes.
Should verified assumptions remain in the log?
Yes, but mark them as confirmed and record the evidence. That creates an audit trail showing how the proposal moved from uncertainty to verified fact.
Conclusion
An assumption log keeps uncertainty visible long enough for leadership to act on it. Your NGO should verify the assumptions that can change the bid, record the evidence behind confirmed decisions, and prevent provisional ideas from becoming permanent proposal facts.