On a municipal runway-lighting upgrade, how should a new associate distinguish the project charter, the project management plan, and work performance data?
Select an answer to reveal the explanation.
Short Explanation
Three different jobs, three different docs. The charter says you may start; the plan says how you will run it; work performance data are what actually happened in the field. Mixing them up is like confusing a driver’s license with a roadmap and the odometer reading.
Full Explanation
On a municipal runway-lighting upgrade, associates should distinguish three concepts: the project charter authorizes the project; the project management plan describes how it will be managed; and work performance data are actual observations from execution. Keeping those layers separate prevents status emails from being mistaken for authorization or planning. Civic projects need all three working together without conflation.
They are not interchangeable labels for the same weekly status email. Work performance data do not authorize spending, and the charter is not a list of actuals. The project management plan is far more than a list of unresolved issues—it integrates subsidiary management approaches.
Exam caveat: CAPM predictive literacy requires crisp definitions of initiating, planning, and monitoring artifacts. Distractors often swap authorization, planning, and actuals.
Operational check: when reviewing runway-lighting documents, label each artifact by function—authorization (charter), how-to manage (plan), actuals (work performance data)—and ensure status reports compare data against plan baselines. When coaching juniors, ask them to sort sample documents into authorize / plan / actuals buckets until the distinction is automatic. Misfiling actuals as authorization is a frequent associate error.