Skip to content
PMPCAPM

Assumption Log

An assumption log is a project document used to record all assumptions and constraints identified throughout the project lifecycle.

Share:

Explanation

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

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 is a graphical representation of work remaining versus time in a Sprint or release, showing whether the team is on track to complete the planned work.

Resource Leveling

Resource leveling is a resource optimization technique in which adjustments are made to the project schedule to keep resource usage at or below a defined limit, often resulting in a longer project duration.

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.

Stakeholder Mapping

Stakeholder mapping is the visual representation of stakeholder relationships, influence, interest, or other attributes using grids, matrices, or diagrams to support analysis and engagement planning.

Relative Estimation

Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.

Cost Performance Index (CPI)

Cost Performance Index (CPI) is an EVM efficiency metric that measures cost performance as the ratio of earned value to actual cost: CPI = EV / AC.

Schedule Performance Index (SPI)

Schedule Performance Index (SPI) is an EVM efficiency metric that measures schedule performance as the ratio of earned value to planned value: SPI = EV / PV.

Earned Value Management (EVM)

Earned Value Management (EVM) is a methodology that integrates scope, schedule, and cost data to assess project performance and progress objectively.

Part of

Integration Management

Study full domain →

Test your knowledge

Practice scenario-based questions on this topic with detailed explanations.