How to Write a Project Quality Plan

A project quality plan defines how quality is planned, assured, and controlled for a specific regulated project — who owns what, which standards apply, how quality gates work, and how deliverables are verified. It is where project management meets GxP: the plan that keeps a delivery project inside the quality system.

1. 1

   Define scope, standards, and quality objectives

   Define the scope of the plan, the standards and regulatory expectations it operates under, and the quality objectives the project is accountable for. Objectives should be specific enough to be assessed at closeout — a qualified facility with a defined set of validated processes by a stated date — rather than aspirational statements about excellence that no gate could ever fail.

2. 2

   Assign quality roles and responsibilities

   Assign the quality roles and the authority attached to each, distinguishing who performs, who reviews, who approves and who can stop work. Include the interfaces with the receiving operational quality unit, because a project quality function that operates in parallel to the site quality system produces deliverables the site must later adopt, and adoption is where the gaps surface.

3. 3

   Define quality gates and deliverables

   Define the quality gates, what each requires, and the deliverables that pass through them — specifications, design reviews, risk assessments, commissioning and qualification documentation, and the traceability that binds them. State which deliverables are subject to quality approval rather than review, since that distinction determines where the project’s schedule has real dependencies.

4. 4

   Define document, change, and deviation control

   Define how documents, changes and deviations are controlled during the project, and how that regime hands over to the operational one. Projects generate changes at a rate no operational change-control process is sized for, so a project-specific approach is normal — but the criteria for what constitutes a change, and the assessment it receives, cannot be looser than the operational standard for anything affecting a critical aspect.

5. 5

   Approve and maintain

   Approve the plan with both project and quality signatories and maintain it as the project evolves. A plan written at authorisation and never revisited becomes inconsistent with how the project is actually running, and the inconsistency is what an auditor finds: the plan describes gates that were bypassed or documentation standards nobody applied, which is worse than having described the approach honestly.