The six pages of a project quality plan reviewers actually read

A project quality plan for a services or civils package runs to forty or fifty pages once the appendices are in. The principal contractor's reviewer does not read forty pages. They read six, in a fixed order, and they decide on the strength of those six whether the rest is worth their time. We have sat on both sides of that desk. This is the order the pages are read in and what each one has to prove before the reviewer turns to the next.

Why six, and why in this order

BS EN ISO 10005:2018, Quality management - Guidelines for quality plans, is the document a reviewer has in mind whether or not they name it. It is a guideline rather than a requirements standard, so nobody is certified to it, but clause 6 lists what a quality plan is expected to cover, from scope and inputs through responsibilities, documented information, externally provided products, production, identification and traceability, to inspection and release. ISO 9001:2015 clause 8.1 is where the requirement to plan the work comes from. The reviewer's job is to check that your plan applies your system to their contract, and the six pages below are where that is either demonstrated or not. Everything else in the plan is supporting material.

Page one: scope

The first page has to prove that the plan was written for this contract. It names the contract, the package, the physical extent, the sections or phases, and what is excluded. It cites the client's quality requirements document by reference and revision, and if the client has mandated their own plan format it says so and cross-references it. A reviewer reads the scope looking for one thing: evidence that the document in front of them is not the company quality manual with a different cover. Fifteen pages describing the document control procedure is the sign that it is. "Document control is to our procedure PR-001; the project document register is Appendix D" is the sign that it is not.

Page two: contract documents and standards

The table of documents that set the requirements: the contract form, the employer's requirements, the specification sections that apply to your package, the drawing register, and the standards that govern the work with their editions. This page has to prove that the standards are current, because it is the easiest place on the whole plan to find a fault. An electrical package plan issued this month that lists BS 7671:2018+A2:2022 tells the reviewer it was copied from an old job; Amendment 4 was published on 15 April 2026. A fire detection plan citing BS 5839-1:2017 is worse, because the 2025 edition renumbered the clauses and every clause reference downstream in the ITPs is now wrong. Check every line of this table against a current index before you issue, and put the date you checked at the foot of it.

Page three: organisation and authority

Named people, not job titles, for the project manager, quality manager, site managers by discipline, document controller, commissioning manager and the specialist subcontractors, with the organisation chart in an appendix. The page has to prove two things. First, that the people exist and the reviewer can find out whether they are competent, which is why "the Quality Manager will" without a name is returned. Second, who is allowed to sign what: who can sign each type of record, who can release a hold point, who can grant a concession, and who can stop work. If those authorities are not written down here, they will be argued about on the day a pour is waiting.

Page four: construction control and the ITP register

This is the page the reviewer spends longest on, and it is the one most plans get wrong. It has to prove that you know what will be inspected before you start. That means the inspection and test plan register for the package, listing every ITP, its revision and its approval status, as a live appendix rather than a table pasted in once. It means the definitions of hold, witness, surveillance and review as they will be applied on this contract, with the notice periods agreed with the client written down, typically 24 or 48 hours. It means the check sheets that record each ITP line, the method statement and briefing regime, and the calibration register for the instruments that will be used. A plan that says "inspections will be carried out to approved ITPs" and does not say which ITPs exist, or whether any are approved, has made a promise the reviewer cannot check.

Page five: nonconformity, concessions and corrective action

The page has to prove that when something goes wrong it will be recorded, contained and decided by the right person. How a nonconformity is raised and numbered, how the work or material is quarantined, the five dispositions and who can authorise each, and the rule that only the party whose requirement it is can grant a concession. Then how the cause is recorded and how corrective action is verified after an interval. Reviewers read this page with a particular fear in mind: the departure from specification that the site manager accepted on the contractor's behalf and that the client discovers at handover. If the plan says in plain words that the site manager cannot do that, the fear goes away.

Page six: records and handover deliverables

The last page the reviewer reads is the one about the end of the job. It has to prove that the argument about deliverables will not happen at practical completion. It lists the records the contract will produce, where they are filed and how long they are kept, and it lists the handover deliverables agreed with the principal contractor: certificates by discipline and the standard each is issued to, as-built drawings and their format, O&M manuals, the health and safety file contribution and client training. A plan that leaves this to "O&M manuals will be provided" has not defined the deliverables, and the reviewer knows from experience what that costs in the last three months.

What the reviewer does next

If the six pages hold up, the reviewer samples the rest: an ITP from the register against the acceptance criteria in the specification, a name from the organisation chart against the competence records, a standard from the table against the ITP that cites it. If the six pages do not hold up, the plan is returned with comments on those pages and the rest is not read. That is why the effort belongs on these six. A plan with a beautiful design control section and an ITP register that says "to follow" is a returned plan.

Keeping it alive

One more thing reviewers notice, later rather than sooner. A PQP still at revision 01 nine months into a contract has not been maintained. The ITP register grows, people change, standards move, and the plan is re-issued when they do, with a revision line that says what changed. The monthly review of the plan itself belongs in the audit and review section, and it belongs in the diary.

Our Project Quality Plan is the template with guidance in every section alongside a fully completed worked example for an M&E package, structured to ISO 10005:2018, with the six pages above written the way a Tier 1 reviewer expects to find them and the appendices set up as registers. It cross-references the procedures in the ISO 9001 Construction QMS so that the plan, the procedures and the forms say the same thing. If you are writing a plan from a blank page this week, read the full section-by-section guide first; it will save you a round with the reviewer.

Updated 17 September 2026: ISO 9001:2026 was published on 16 September 2026. At the date of this update the UK designation on the published index remains BS EN ISO 9001:2015+A1:2024 and BS EN ISO 10005:2018 is unchanged; the clause 8.1 reference above is to the 2015 edition.