6.4 Common Traps in Management Products

High-Frequency Confusions

Foundation questions cluster around a handful of look-alike products. Learn each boundary precisely.

Project Brief vs PID

The Project Brief is lightweight and created in Starting up a Project to justify initiating the project. The PID is the comprehensive baseline created in Initiating a Project to manage the whole project. The Brief feeds into the PID; they are not interchangeable. A trap answer treats the Brief as the document the board uses to authorise the project — in fact the board uses it to authorise initiation, and authorises the project against the PID.

Report vs Record

Reports are point-in-time snapshots: once an instance is issued it is fixed forever, and the next period produces a new instance (Highlight Report week 1, week 2, and so on). Records (registers and logs) are living documents updated in place throughout the project. A question that says a document is "updated continuously" points to a record; one that says it is "issued at a frequency" points to a report.

More Traps to Avoid

Daily Log vs the Registers

The Daily Log is the project manager's informal diary — notes, observations, reminders, and minor actions that do not warrant a formal register entry. Significant risks go in the Risk Register, formal issues, changes, and off-specifications go in the Issue Register, and quality activities go in the Quality Register. A trap answer files a formal risk in the Daily Log; the correct answer escalates it to the Risk Register.

Issue Report vs Exception Report

An Issue Report captures the details of one specific issue that has been raised and needs analysis or a decision. An Exception Report is produced only when a stage or the project is forecast to breach tolerance. Many issues never become exceptions; an exception is a forecast that something will go out of the agreed limits. Reading the trigger word — "a problem was raised" versus "forecast to exceed tolerance" — decides the answer.

Tailoring traps

A recurring distractor insists a management product must always be a separate formal document. PRINCE2 7 explicitly allows products to be merged, split, or held in a tool, provided the purpose is met. On a small project the Business Case may sit inside the Project Brief; the registers may be tabs in one spreadsheet. The correct answer respects the purpose, not a fixed format.

Removed products

Because PRINCE2 7 dropped several 6th-edition products, a trap may name a product that no longer exists as a standalone item, such as Configuration Item Records or the Product Status Account. The current artefact is the Product Register. If an option cites a removed product as the right answer, treat it as a distractor.

Ownership traps

Finally, watch ownership: the project manager maintains the Business Case but the Executive owns it; team managers produce Checkpoint Reports, not the project manager. Matching the product to the wrong role is one of the most common ways an otherwise-correct-looking option is wrong.

Worked Trap Examples

Seeing the trap in action fixes the boundary better than memorising it. Work through these.

Trap: "The board authorises the project using the Project Brief."

Tempting, because the Brief is presented to the board early. But the board authorises initiation from the Brief and authorises the project from the PID. The Brief is too lightweight to be the success baseline. The correct answer names the PID.

Trap: "A forecast slip means the project manager updates the Issue Register and waits."

Logging the issue is correct as far as it goes, but a forecast tolerance breach obliges the project manager to escalate by raising an Exception Report to the board. Stopping at the register understates the action required.

Trap: "The Lessons Report is only produced at project closure."

Lessons are captured in the Lessons Log throughout, and a Lessons Report can be produced at any stage boundary as well as at closure, so that learning is shared while the project is still running. An answer that confines it to closure is too narrow.

Quick-reference disambiguation table

Keep this table in working memory. Most trap questions in this domain are simply one row of it disguised in a paragraph of context, and recognising the row strips the disguise away.