12.4 Work Packages & Reporting Cycle

The Work Package is the single most important management product for joining Controlling a Stage and Managing Product Delivery. It is both the instruction the PM gives to a Team Manager and the agreement that binds both sides while the work is done. Understanding its lifecycle — and the reporting cycle that runs alongside it — is essential for Practitioner scenarios that ask "what happens next?" or "who owns this product now?"

The Work Package lifecycle

The lifecycle has five steps. The first and last belong to the PM (under Controlling a Stage); the middle three belong to the Team Manager (under Managing Product Delivery).

A common exam trap is to compress steps 4 and 5 into a single 'handover'. They are distinct: in step 4 the Team Manager obtains acceptance and returns the products; in step 5 the PM receives the completed Work Package and integrates it. Until acceptance in step 4, the product is the Team Manager's responsibility; after step 5, it is the PM's.

The reporting cycle

The reporting cycle is the nervous system of the two processes. Two time-driven reports keep information flowing:

• Checkpoint Report — flows from Team Manager → PM at the frequency set in the Work Package. It covers work completed, work planned next, issues and risks for the Work Package, and the Work Package tolerance position. The PM consumes it during assess progress in Controlling a Stage.
• Highlight Report — flows from PM → Project Board at the frequency set in the Communication Management Approach. It summarises stage status, the tolerance position, issues and risks that the board needs to know about, and any decisions needed. It is the board's routine view of the stage; the Exception Report is the non-routine escalation.

Both reports are time-driven, meaning they are produced on a cadence (weekly, fortnightly, at the end of each sprint) regardless of whether anything notable has happened. This is deliberate: a quiet Highlight Report is itself a signal that the stage is on track. Event-driven reports in this part of PRINCE2 are the Issue Report, Risk update, and Exception Report — each is produced because something happened.

The tolerance cascade

Tolerances in PRINCE2 flow downward, and exceptions flow upward. The cascade is precise:

1. Project tolerance — set by corporate/programme management (or the Project Board if there is no higher layer) and recorded in the Project Plan. It defines the limits within which the Project Board may operate without referring back.
2. Stage tolerance — set by the Project Board when it authorises each stage (the output of Managing a Stage Boundary). It is a slice of the project tolerance delegated to the PM for that stage.
3. Work Package tolerance — set by the PM for each Work Package issued under Controlling a Stage. It is a slice of the stage tolerance delegated to the Team Manager.

If a Team Manager forecasts a Work Package tolerance breach, the Team Manager raises an Issue to the PM. The PM then decides whether the breach can be absorbed within the stage tolerance (corrective action under Controlling a Stage) or whether the stage tolerance itself is now forecast to be breached (Exception Report to the Project Board). The Team Manager never raises an Exception Report — that act belongs to the PM, because the PM is the person who holds the stage tolerance.

Who manages the team?

A rule that appears repeatedly in Practitioner questions is that the PM does not manage team members directly. The PM manages the stage; the Team Manager manages the team, via the Work Package. This is why the Work Package exists: it is the mechanism by which the PM directs work without becoming the line manager of the specialists. If a team member is underperforming, the PM raises it with the Team Manager (perhaps as an Issue); the Team Manager handles it. If a specialist product needs rework, the PM returns it to the Team Manager; the PM does not pick up the tools.

This separation is what makes PRINCE2 scalable to large projects. On a small project, the PM and Team Manager may be the same person, but the roles remain distinct — the PM still authorises a Work Package to the Team Manager, even if both hats are on the same head. The Practitioner exam rewards candidates who can name the role that owns each step, not the individual who happens to perform it.

Putting it together: a single cycle

Picture one full turn of the cycle. The PM authorises a Work Package. The Team Manager accepts it and begins execution, producing Checkpoint Reports each week. The PM reads them, assesses progress, and at the end of the month sends a Highlight Report to the Project Board. The board governs by exception — it does not respond unless the Highlight Report flags a tolerance concern or an Exception Report arrives. The Team Manager finishes the products, quality-checks them against the Product Descriptions, obtains acceptance, and delivers them back. The PM receives the completed Work Package, updates the Stage Plan, and the cycle begins again with the next Work Package. That is one heartbeat of Controlling a Stage and Managing Product Delivery working together.