Quality register

The quality register is a log of all quality-related activities that occur during the project — such as workshops, reviews, testing, and product acceptance.

Initially, the quality register will be empty. The project manager populates it using information from the plans and product descriptions. As the project progresses, it becomes a central reference point for monitoring, tracking, and reporting on quality management.

Using the quality register allows the project manager to monitor progress easily by checking whether the target review date and actual approval date fields are completed. This helps ensure that quality controls are applied consistently throughout the project.

Relationship with reports

The quality register provides valuable input for the end stage report and the end project report. The quality register serves three key purposes:

• It gives an overview of planned quality activities, with a unique reference for each.
• It tracks the status of each activity and provides links to related quality records.
• It offers a complete history of all quality activities and outcomes by the end of the project.

Timeline

The quality register is maintained throughout the project lifecycle and helps track the planning, execution, and results of all quality-related activities:

• The quality register is created during the initiation stage once the project’s quality management approach and key products are defined.
• Most of the input comes from the stage plan and product descriptions, which identify when and how each product will be reviewed.
• Quality activities are planned during the managing a stage boundary process based on what needs to be delivered in the next stage.
• The register is then updated regularly during the controlling a stage process as quality activities take place.
• It acts as a control tool, helping the project manager identify whether quality reviews are delayed or failing and take corrective action.
• During closing a project, the quality register is reviewed to help prepare the end project report and the lessons report.
• The project manager maintains the quality register, with updates often supported by project support.

Source data

Throughout the project, the quality register is populated using planning inputs, actual performance data, and quality control documentation:

• The format and structure of the register are defined in the quality management approach. The project manager will review the most recent quality register template.
• Quality activities are added when preparing the stage plan, based on the schedule and product descriptions.
• Additional entries may be created or refined during the development of the team plan.
• The register is also updated with data from the actual execution of quality activities, including review and approval results.
• Links to quality records, such as signed-off review forms or test results, can be included for traceability.

Format

The format of the quality register should suit the size and complexity of the project, while supporting easy access, updates, and tracking.

• Can be a document, spreadsheet, or database — most commonly a shared spreadsheet.
• May be maintained as a standalone register or integrated into progress review minutes.
• Can also be a project management tool entry with links to quality records and product data.

Quality criteria

To ensure the quality register supports effective control, it should meet the following quality standards:

• Every planned quality activity is recorded in the quality register.
• Responsibility for maintaining the register is clearly assigned (e.g., project support).
• Actions are assigned to individuals or roles.
• Entries are uniquely identified and linked to the relevant product.
• Access is controlled, and the register is stored securely (physically or digitally) to protect sensitive information.

Tips

Here are some informal observations on how the quality register is (or isn’t) used in real-world PRINCE2 projects:

• In practice, many organisations don’t actively maintain a quality register, even though it’s recommended.
• Most teams rely on product descriptions for quality expectations and perform testing only when the product is ready.
• If a product fails quality tests, teams are instructed to correct the issues without formally tracking the outcome.
• When a product passes quality checks, it is accepted, and the team typically moves on to the next work package.

—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.