Work package

A work package is a formal set of instructions used by the project manager to assign responsibility for the creation of one or more products to a team manager or team member.

Purpose

The purpose of a work package is to provide all the necessary information to enable the delivery of specific products in a controlled and agreed manner. A work package typically includes:

• A description of the work to be done
• Relevant product descriptions
• Techniques or methods to be used
• Any agreed tolerances (e.g., time, cost, scope)
• The date of agreement between the project manager and team manager
• Reporting arrangements (e.g., frequency and format of checkpoint reports)
• Required quality criteria and quality control responsibilities

Work packages help ensure clear expectations, accountability, and alignment between the project manager and delivery teams.

Timeline

Work packages are a key control tool used to delegate and monitor product delivery throughout the stage:

• In the PRINCE2 product map, work packages are shown in dark red, highlighting their role in delivery.
• They are primarily used during the controlling a stage process, where the project manager delegates work to team managers or team members.
• Team managers and team members actively use work packages to guide and report on delivery.

Note: Work packages can also be created during the initiation stage, especially if controlling a stage is applied early for managing product development.

Source data

The work package is compiled using a combination of product-related details and control requirements defined in the project’s management products:

• The main content of a work package comes from the relevant product descriptions.
• Additional input is derived from existing commercial agreements between the customer and supplier (if applicable).
• The quality management approach provides guidance on required quality activities.
• The issue management approach defines how product changes will be managed.
• The stage plan provides key timelines, dependencies, and resource allocations for scheduling the work package.

Format

The format of a work package depends on the context, the people involved, and whether the work is delivered internally or by an external supplier.

• A work package can be a formal document or contract.
• It may also be presented as a slide deck (e.g. PowerPoint) with links to relevant product descriptions.
• In some cases, it may be delivered orally, especially when assigning tasks to internal team members — though it’s always wise to document it to avoid misunderstandings.
• For external suppliers, a work package should be a formal, written instruction aligned with the terms and conditions of the contract. Each work package serves as a mini-contract or formal agreement in such cases.

Quality criteria

To ensure effective delegation and delivery, each work package should meet the following quality standards:

• The work package is clearly defined and fully understood by the team manager or team members.
• A baselined product description exists for each product, with clear and agreed quality criteria.
• Work standards (e.g. methods, tools, quality expectations) are agreed upon in advance.
• All necessary people interfaces are identified so the team manager knows who to contact.
• There is clarity on how to escalate issues and risks during delivery.
• Agreement is reached on any constraints, including time, cost, effort, and scope.
• Dates and effort estimates are consistent with the stage plan for the current management stage.
• Reporting arrangements are defined, including the format and frequency (e.g. Checkpoint reports).

Tips

Here are a few practical reminders to help you keep work packages useful and effective:

• The work package should never be a surprise to the team manager — they should have already contributed to the stage plan and reviewed the product descriptions.
• A simple one-page cover sheet can work well to summarise the work package and link to the detailed product descriptions.
• Focus on delivering to the quality criteria defined in the product descriptions — what matters most.

—o—

Written by Frank Turley.

If you have questions or doubts after using this wiki, you can ask for help on the Facebook or LinkedIn study groups.