Make each assumption explicit and traceable
For each material budget driver, record what you expect, why you expect it, which period it affects, who can explain it, and what would cause you to revisit it. Distinguish confirmed information from an estimate. A number without its rationale is difficult to assess or update.
The examples below use fictional Northstar Works amounts for illustration; they are not benchmarks or approved planning inputs.
Illustrative assumptions register
Fictional annual plan examples; amounts are in USD and do not set local planning rules.
| Driver | Sample assumption | Rationale | Revisit when |
|---|---|---|---|
| Contractor support | $72,000 across six months | A project phase is expected to need two specialist contractors during the second half of the year. | The project schedule or specialist demand changes. |
| Software renewals | $24,000 for the annual renewal period | The estimate uses the current team subscription count and quoted renewal amount in this fictional example. | Seat needs or the renewal quote changes. |
| Team travel | $18,000 across four planned trips | The plan assumes four cross-site workshops, with attendance and travel timing still estimated. | A workshop is moved, cancelled, or added. |
Turn a vague estimate into a useful assumption
The difference is a testable reason, not extra wording.
Vague
“Travel will be higher this year.” This gives no driver, period, or way to revisit the estimate.
Useful
“The fictional plan includes four cross-site workshops at an estimated $4,500 each; revisit the total if a workshop is moved or cancelled.” The driver, basis, timing, and review trigger are visible.