CAPM Practice: Determine how to document project controls of predictive, plan-based projects

A late milestone should be documented in the performance report (which tracks milestone status against the baseline). If the delay caused actual problems (blocking other activities, affecting stakeholders), it may also warrant an entry in the issue log. Both documents serve different but complementary purposes in tracking project status.

**Why not A:** While the performance report should include milestone status information, this answer alone is incomplete. The correct answer (C) indicates that both the performance report and the issue log may be appropriate, depending on whether the delay caused downstream problems.

**Why not B:** Recording the late milestone as a new risk in the risk register is not appropriate because the event has already occurred — it is no longer a risk (uncertain future event) but a realized issue. Risks are uncertain future events; the late milestone is a known, past occurrence.

**Why not D:** While the issue log is appropriate if the delay caused other problems, this answer alone is incomplete. The late milestone should also be documented in the performance report to track milestone status against the baseline, making the combined answer (C) the most complete response.