The auditor is coming, and the quality manager is opening folders
The surveillance audit is next month. The auditor will pick a sample of projects and ask to see the project quality plan, the design reviews at key stages, evidence of verification, and how changes were controlled. The practice does all of this in some form. But the evidence is in meeting minutes on one job, an email on another, and nowhere on a third, where the review was done over coffee and never written down.
The quality manager spends days chasing project leads to find or recreate records. Everyone agrees to do it properly next time.
Why quality records drift
- The quality procedure lives in a manual, separate from the tools engineers use every day.
- Nothing prompts a design review when a project reaches the relevant stage.
- Records use different formats on each project.
- Verification is recorded in the check process, which is not linked to the quality file.
- Only the quality manager looks at the whole picture, and only before audits.
Smaller projects are often the weakest point. A large scheme has a project manager who holds formal reviews because the client expects them. A small extension or a quick appraisal gets the same review in principle, but in practice it happens as a conversation that leaves no trace.
What the scramble costs
| Effect | Who pays |
|---|---|
| Days of audit preparation | Quality manager and project leads |
| Records recreated after the fact | Weaker evidence and a poor habit |
| Audit findings for missing records | Corrective actions and more admin |
| Reviews skipped under pressure | The design itself, occasionally |
The last row matters most. Records are not only for auditors. A review that is prompted and recorded is more likely to happen when deadlines are tight.
How we build quality into the workflow
- We map your quality procedure: what each project needs, at which stage, and who signs it.
- New projects get a short quality plan form, pre-filled from the project setup.
- When a project reaches a stage gate, from your fee or drawing register data, the lead is prompted to hold and record the design review.
- Reviews are recorded in a standard form with attendees, points raised and actions, which are tracked to closure.
- Verification records come from your calc check tracker or drawing checking, linked rather than copied.
- A quality dashboard shows projects with overdue reviews or open actions.
- For an audit, any sample of projects produces a pack of its quality records in one step.
We do not write your procedure or advise on what the standard requires. We make the procedure you already have easier to follow and easier to evidence.
We usually map the procedure with your quality manager, then test the workflow on a few live projects with their leads. The aim is a record that takes minutes to keep, because anything heavier gets skipped as soon as a deadline looms.
The next audit
The auditor picks a sample and the quality manager opens each project's quality record, complete, dated and consistent. Preparation takes a fraction of the effort.
Between audits, the dashboard shows which reviews are overdue, so the quality manager can nudge before they become findings.
Do audits feel like this?
- Audit preparation means chasing project leads for records.
- Design reviews happen but are not always written down.
- Records look different on every project.
- Nothing prompts a review at the stage gate.
- Actions from reviews are not tracked to closure.