DailyWF / Projects
Assumption Log
Track project assumptions before they become invisible sources of risk.
Project use
Use this when early project facts are still uncertain but decisions are already being made around them.
- Write each assumption as a testable statement, not a vague concern.
- Name the decision or plan that depends on the assumption.
- Assign an owner to validate, replace, or retire the assumption.
- Set a review date before the assumption can silently become accepted fact.
- Convert invalid assumptions into scope, schedule, cost, or risk changes.
Expected output
A project record that states the decision, owner, boundary, dependency, next checkpoint, and evidence needed to continue.
Common failure mode
Assumptions become hidden requirements and create surprise rework.
Use notes
| Best trigger | Use before a project decision becomes expensive to reverse. |
|---|---|
| Evidence | Keep enough context to explain the decision later without reconstructing conversations. |
| Review point | Review when scope, stakeholder expectation, timing, risk, or ownership changes. |
Related pages
- Discovery BriefDocument early investigation before the project is formally approved.
- Project CloseoutClose work formally and preserve ownership of remaining obligations.
- Project IntakeCapture a proposed project before committing time or budget.
- Dependency TrackerTrack decisions, inputs, vendors, systems, people, and approvals that can block delivery.
- Lessons LearnedCapture reusable learning from project execution.
Use this with a tool
Find related documents, copy a checklist, or request a missing workflow.