Which artifact captures assumptions and constraints to be tracked through the project lifecycle?

• A. Risk Register
• B. Issue Log
• C. Change Log
• D. Assumption Log

Answer: (D)

Tracking assumptions and constraints as they evolve throughout the project is the key idea. The Assumption Log is the central place to capture each assumption and each constraint, along with who owns them, why they’re important, potential impacts, and current status. As new information comes in, updating this log lets the team reassess validity, adjust plans, and respond proactively, keeping planning aligned with reality across the lifecycle.

This fits best because it specifically serves as a record for what is assumed or constrained, ensuring nothing slips through the cracks. The Risk Register, by contrast, focuses on uncertain events and their responses; the Issue Log tracks current problems needing resolution; and the Change Log records approved changes to baselines. While some assumptions might turn into risks, the Assumption Log is the appropriate repository to monitor them from the outset.