Project-based businesses: quality plans per project without drowning in paperwork.
ISO Cloud Consulting editorial teamIn a project-based business every project needs a quality plan, but not a new manual. Use one standard template with fixed headings, tailor its depth by a simple risk score, define inspection and hold points, brief subcontractors, plan handover from day one, and feed lessons into the next bid.
Why do project businesses struggle with quality plans?
In a project-based business, every project is a small company with its own customer, supply chain and deadline. The quality system has to work at that level, without every project manager writing a new manual.
Engineering contractors, installers, fit-out companies, system integrators and event producers all face the same tension. If the quality plan is too heavy, project managers ignore it. If there is no plan, every project relearns the same lessons at the client's expense.
What goes in a standard project quality plan?
The answer starts with one standard template. A project quality plan of a few pages, with fixed headings: scope and requirements, organization and responsibilities, risks, inspection and test points, subcontractors, documents and records, and handover. The headings never change. What changes is how much goes under each one.
How do you tailor the plan by risk?
That leads to tailoring by risk. Not every project deserves the same effort. Score each project at the start on a handful of factors: value, technical novelty, client requirements, safety and the amount of subcontracted work.
A low score gets a light plan, half a day to prepare. A high score gets the full plan, a kick-off review and a mid-project audit. Writing that rule down saves enormous time, and it is exactly the risk-based thinking the standard asks for.
How should inspection and hold points work?
Next, inspection points. For each stage of work, decide what is checked, by whom, and where the record goes. Mark the hold points, where work must not continue until inspection is signed. Clients notice a contractor who manages hold points properly.
How should subcontractors be managed?
Then subcontractors. On many projects, most of the work is done by subcontractors. They need to be approved, briefed on the plan, and asked for the records you will need at handover. Write those record requirements into the order, not into an email at the end.
When should handover be planned?
Handover should be planned from day one. List what the completion pack must contain, and fill it as the project runs. A handover pack assembled in the final week is always incomplete, and it is the last impression the client has of you.
How do lessons learned pay for the system?
Finally, lessons into the next bid. At project close, a one-page review. What cost more than planned, what went wrong, what the client praised.
Then make it a required input to the next estimate of a similar job. That is where the quality system pays for itself, in better pricing.
What stays at company level?
One last design point. The company level still matters. Policy, objectives, the approved subcontractor list, competence records, internal audit and management review all sit above the projects.
Internal audits should sample projects, not just head office. Pick one active project and one closed project each quarter, and check them against their own plans. That tells you far more about how your company really works than any audit of the manual.
Can you get help designing it?
We help project-based businesses design the template and the tailoring rule; the consulting page explains how we work. For the company-level documents, see the ISO 9001:2026 Complete QMS Documentation Kit, and for sector guidance, ISO 9001 for engineering firms.
