3.4 Common Traps in 7 PRINCE2 Practices

Progress — Are We Still on Track?

The Progress practice establishes how to monitor and compare actual achievement against the plan, forecast ahead, and control deviations. It is the engine of the manage by exception principle: each management level delegates authority within set tolerances and only escalates when those tolerances are forecast to be breached.

Tolerances — Seven Performance Targets (7th-Edition Trap)

A frequent 7th-edition trap: tolerances can be set against seven performance targets, not six. The 7th edition added sustainability to the list.

Tolerances are delegated downward: the Project Board sets project tolerances; the Project Manager works within stage tolerances and sets Work Package tolerances for Team Managers. When a level forecasts it will exceed its tolerance, that is an exception, and it is escalated upward.

Controls and the Four Reports

PRINCE2 uses two control types. Time-driven controls occur at regular intervals (e.g., a weekly Highlight Report). Event-driven controls occur when a specific event happens (e.g., the end of a stage triggers an End Stage Report). Mixing these up is a classic trap.

Which Report, From Whom, To Whom

High-Frequency Traps

• Exception is a forecast, not a fact. An Exception Report is raised when a level is predicted to breach tolerance — waiting until it has already happened is wrong.
• Checkpoint vs. Highlight. Checkpoint Reports flow up from Team Manager to Project Manager; Highlight Reports flow up from Project Manager to Project Board. Candidates reverse these.
• Daily Log vs. Lessons Log. The Daily Log holds informal issues/notes; the Lessons Log captures lessons for reuse — they are different products.
• Six vs. seven tolerances. If an option omits sustainability, it is using outdated 6th-edition wording.
• Tolerance direction. Tolerances are delegated down; exceptions are escalated up. Reversing the direction is a deliberate distractor.

More Cross-Practice Traps

Beyond Progress, several traps span the whole domain. Drill these distinctions until they are automatic.

Ownership Traps

The Senior User specifies and confirms benefits and accepts the products; the Executive owns the Business Case and ultimate justification; the Senior Supplier speaks for those building the products. Mixing up Senior User and Executive responsibilities is one of the most-missed Foundation points.

Document Confusion Traps

• PID vs. Project Brief. The Project Brief is the lightweight basis created in Starting Up; the PID is the detailed baseline created in Initiating. The PID extends the Brief, it does not replace its purpose.
• Issue Report vs. Exception Report. An Issue Report describes a single formal issue and its options; an Exception Report describes a forecast tolerance breach for a whole stage or project.
• Quality Register vs. product register. The Quality Register tracks quality-control events and results; do not confuse it with the list of products and their statuses.
• Configuration / change. In the 7th edition, what older notes call 'configuration management' is handled within the Issues practice and the Digital and Data Management Approach.

When a question offers two plausible documents, ask when in the lifecycle and for what decision each is used — that almost always separates the right answer from the distractor.

Terminology Currency Traps

Because the 7th edition changed several names, many practice questions exist specifically to catch out-of-date revision. Treat any of these older terms as a warning sign: 'Change theme' (now Issues), 'Organization theme' (now Organizing), 'Configuration Management Strategy' (folded into the Issue Management Approach and Digital and Data Management Approach), and 'six tolerance areas' (now seven, with sustainability added). When two options say almost the same thing but one uses current 7th-edition wording, choose the current term — the exam is sat against the latest syllabus.

Two More Progress Traps

First, distinguish event-driven from time-driven controls precisely. A Highlight Report is time-driven (it goes out every fortnight regardless of what happens), whereas an End Stage Report and an Exception Report are event-driven (they are produced because a stage ended or a tolerance was forecast to breach). A question that calls the Highlight Report 'event-driven' is wrong.

Second, remember that stage boundaries are management decisions, not arbitrary calendar dates. PRINCE2 stages exist so the Project Board can make a go/no-go decision with current information; a project must have at least two management stages (the initiation stage plus one or more delivery stages). Candidates sometimes assume stages are fixed monthly periods — they are sized around control and risk, so a high-risk project has shorter stages and more decision points.