PDC Initiation Practice Test

The idea being tested is what an assumption log is and how it functions early in a project. An assumption log is a living record that captures beliefs or statements taken as true for planning—things you’re counting on to shape the scope, schedule, and budget. Each entry notes the assumption, who owns it, its current status, and the potential impact if it turns out to be false. It also includes how you plan to validate the assumption and what actions you’ll take if validation isn’t met.

Using it in initiation helps the team surface uncertainties that could alter the plan down the line. By documenting these assumptions up front, you make implicit risks explicit, so you can decide how to address them early—whether through validation activities, contingency plans, or alternative approaches. It also provides a clear communication point for stakeholders about what the plan hinges on and what evidence is needed to confirm or adjust those beliefs.

An assumption log complements the risk register but serves a distinct purpose: it tracks what you’re taking for granted rather than identified risks with defined probabilities and responses. For example, you might assume key resources will be available when needed or that external systems will integrate without issue; the log records these, who’s responsible, how they’ll be checked, and what to do if they prove inaccurate.