VanillaPM
Sign in Get started free Dashboard
Free template

Assumption log template

A free assumption log template in Excel and CSV — assumptions and constraints with source, owner, confidence, impact if wrong, an attention flag, validation date and what each became if it proved false.

Download Excel (.xlsx) Download CSV Free · no sign-up · opens in Word, Excel, Google Docs/Sheets and LibreOffice

What's inside

ColumnWhat goes in it
IDASM-001, ASM-002 …
Assumption or constraintWhat you are treating as true (or a fixed limit)
Typedrop-down Assumption, Constraint
Categorydrop-down Scope, Schedule, Cost, Resource, Technical, External, Regulatory
SourceWhere it came from: charter, workshop, contract …
OwnerWho will check it
Confidencedrop-down High, Medium, Low
Impact if wrongdrop-down High, Medium, Low
AttentionLow confidence + high impact = check it first · calculated
Validate by
Statusdrop-down Open, Validated, Invalid, Closed
If invalid: risk or change raisedThe risk or change request ID it became

The Excel file has three sheets: the blank register, a filled example from the Coral Ridge Resort sample project, and how to use each column. The CSV is the blank header row only.

What an assumption log is

Every plan rests on things you are treating as true without proof: the ground is as the survey says, the permit arrives in March, the exchange rate holds. The assumption log lists them, with the fixed limits you must work inside (constraints), so that each one is checked before it can hurt the project.

When to use it

From the business case and the charter onwards. Add to it whenever an estimate or a plan says "assuming…". Review it with the risk register.

How to fill it in

  1. Write each assumption as a statement that can be proved true or false.
  2. Record where it came from and who will check it.
  3. Rate your confidence and the impact if it's wrong. The Attention column flags the dangerous ones: low confidence and high impact mean Validate now.
  4. Set a date by which it must be validated.
  5. Close the loop: when an assumption turns out to be false, raise a risk or a change request and note its ID in the last column.

The Example sheet has three entries from the Coral Ridge sample, including an import-duty assumption that proved false and became a risk.

Common mistakes

  • Assumptions nobody owns, so nobody checks them.
  • Vague statements ("the site is suitable") that can't be proved either way.
  • Leaving false assumptions in the log without raising the risk or change they imply.

See it used on a real project: P1 · Develop a common vision