Assumption Log
An assumption log is a project document used to record all assumptions and constraints identified throughout the project lifecycle.
Know it well enough for the exam? Questions on Assumption Log are scenario-based, not definitional.
Practice it freeExplanation
Assumptions are factors considered to be true, real, or certain without proof or demonstration. Constraints are limitations or restrictions that affect project execution. The assumption log captures both, providing a centralized reference that the project team can monitor and validate throughout the project.
The assumption log is first created during the Develop Project Charter process, where high-level strategic and operational assumptions are documented. As the project progresses through planning and execution, new assumptions and constraints are added. Each entry typically includes a description of the assumption or constraint, the basis for it, the potential impact if it proves incorrect, the responsible person, and the current status (open, validated, or invalidated).
Regularly reviewing and validating assumptions is essential to proactive risk management. An assumption that turns out to be false can become a risk or an issue. For example, if a team assumes a vendor will deliver components by a certain date and that assumption proves incorrect, the project schedule may be impacted. By tracking assumptions in the log and linking them to the risk register, the project manager ensures that potential problems are identified early.
Key Points
- •Records all assumptions and constraints throughout the project
- •First created during Develop Project Charter and updated continuously
- •Invalid assumptions can become risks or issues — must be monitored regularly
- •Each entry includes description, basis, impact, owner, and status
Exam Tip
Assumptions are things believed to be true but not proven. Constraints are known limitations. Both go in the assumption log. An invalidated assumption often becomes a risk — this is a common exam scenario.
Frequently Asked Questions
Related Topics
Risk Register
The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.
Issue Log
An issue log is a project document used to record and monitor all issues — problems, gaps, inconsistencies, or conflicts — that arise during the project and require resolution.
Develop Project Charter
Develop Project Charter is the process of creating the document that formally authorizes a project or phase and documents the initial requirements that satisfy stakeholder needs and expectations.
Project Management Plan
The project management plan is the document that describes how the project will be executed, monitored and controlled, and closed.
Most-studied PMP concepts
High-yield topics our learners drill most before exam day.
Change Control Board (CCB)
A Change Control Board (CCB) is a formally chartered group responsible for reviewing, evaluating, approving, deferring, or rejecting changes to the project, and for recording and communicating those decisions.
Burndown Chart
A burndown chart plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.
Burn-Up Chart
A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.
Resource Leveling
Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.
Deliverables
A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.
Power Interest Grid (Power/Influence Grid)
The power interest grid is a 2x2 stakeholder mapping tool that plots each stakeholder by power (ability to affect the project) and interest (concern about its outcome) to decide how to engage them: manage closely, keep satisfied, keep informed, or monitor.
Critical Path Method (CPM)
The Critical Path Method (CPM) is a schedule network analysis technique that calculates early and late start and finish dates for every activity to find the longest path through the project, the minimum project duration, and the float on every other path.
Weighted Shortest Job First (WSJF)
Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.
Risk Register
The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.
Part of
Integration Management
Practice Assumption Log
Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.