Assumption Log in Project Management: PMP Exam Guide
Understand the assumption log for PMP exam questions. Learn how assumptions, constraints, and dependencies are tracked throughout the project lifecycle.
The Often Overlooked Assumption Log
Among the many project documents tested on the PMP exam, the assumption log might be the most underestimated. Candidates spend hours studying the risk register and stakeholder register but give assumptions a cursory glance. That is a mistake — assumptions are directly linked to risk, and PMP exam questions exploit this connection regularly.
An assumption is something believed to be true for planning purposes but not yet proven. Every project is built on assumptions, and every unvalidated assumption is a potential risk waiting to materialize.
What the Assumption Log Contains
The assumption log records two primary categories of information:
Assumptions
- Strategic and operational assumptions made during project initiation and planning
- Assumptions about resource availability, technology capabilities, and stakeholder behavior
- Assumptions about external factors: market conditions, regulatory environments, vendor reliability
Constraints
- Budget limitations imposed by the organization
- Regulatory deadlines or compliance requirements
- Technology restrictions or platform mandates
- Resource limitations (team size, skill availability)
While assumptions and constraints are distinct concepts, PMI groups them in the same document because both influence planning decisions and both require ongoing monitoring.
When Is the Assumption Log Created?
The assumption log is first created during the Develop Project Charter process — making it one of the earliest project documents. High-level assumptions documented in the business case and project charter are transferred to the log and refined as planning progresses.
This early creation is an exam point. If a question asks which documents exist at the end of initiation, the assumption log is one of them (along with the project charter and stakeholder register).
Assumptions and Risk: The Critical Connection
PMI treats assumptions as a primary source of risk. The logic is straightforward:
- An assumption is something you believe to be true but have not confirmed
- If the assumption proves false, your plans are invalidated
- Therefore, every significant assumption carries inherent risk
During the Identify Risks process, the assumption log is a key input. Risk identification includes analyzing each assumption and asking: "What happens if this is wrong?" The answer becomes a risk entry in the risk register.
Managing Assumptions Throughout the Project
Effective assumption management follows a cycle:
- Identify — Document assumptions as they arise, not just during initiation
- Validate — Test assumptions as soon as possible. An assumption validated early eliminates uncertainty.
- Monitor — Track assumptions that cannot be immediately validated. Set triggers or thresholds that indicate when an assumption needs re-evaluation.
- Update — When an assumption is validated or invalidated, update the log and assess the impact on project plans.
The assumption log is a living document. It is updated during multiple processes across all project phases, not just during planning.
PMP Exam Question Patterns
Assumption-related questions on the PMP typically follow these patterns:
- "The project plan was based on the assumption that..." — If the assumption proves false, the correct action involves reassessing impact and updating the risk register.
- "During risk identification, the team should review..." — The assumption log is always a correct input to the Identify Risks process.
- "Which document is created during Develop Project Charter?" — The assumption log is one of the outputs.
Assumptions vs. Constraints: The Exam Distinction
Assumptions are things believed to be true that may or may not hold. Constraints are known limitations that definitely restrict options. A constraint is not uncertain — it is a fact of life for the project. Both live in the assumption log, but they serve different analytical purposes.
For example: "The vendor will deliver hardware by March 1" is an assumption. "The budget cannot exceed $2 million" is a constraint. If the exam asks which is which, apply the uncertainty test.
Build solid assumption analysis skills with targeted practice on PMPprep. Understanding how assumptions flow into risk identification is a reliable way to earn points on the PMP exam.
Practice what you just learned
Test your knowledge with flashcards, mini exams, and full-length practice tests on PMPprep.
Start Studying Free