Here's a moment every quality consultant should sit with: eighteen months after your engagement ends, a certification body auditor is at your former client's conference table, holding a procedure with your fingerprints all over it, asking the quality manager a question about it. You are not there. Your work is — and it's being audited.
Every deliverable you produce will eventually be evaluated by someone who wasn't in the room when you produced it: a CB auditor, an OEM's supplier-quality engineer, the owner's new operations director, or the consultant who replaces you. The consultants with decade-long reputations are the ones whose work passes that exam in absentia. It's a learnable skill, and it comes down to a few disciplines.
The template smell
Certification auditors read hundreds of quality manuals a year, and they can identify a purchased template by the end of page one. The tells are always the same: procedures describing roles the company doesn't have ("the Quality Director shall..." — in a nine-person shop), processes that don't exist ("design outputs shall be verified against design inputs" — at a build-to-print machine shop that excluded design), and that unmistakable mid-paragraph voice shift where boilerplate meets a pasted-in company name.
An auditor who spots template content doesn't just discount the document — they recalibrate their sampling for the whole audit, because a paper system copied from a binder predicts records that won't match reality. Your client pays for that recalibration in audit-day friction and findings, and your name is on the invoice they'll remember.
The discipline: every procedure describes this company, verifiably. Real job titles, actual process steps, the exclusions this client genuinely takes with their actual justification. Faster method than writing from scratch, better than templating: interview the person who does the work, write down what they said, then close the genuine gaps between that and the requirement. The procedure then has a property no template can fake — the employees describe their work the same way the document does. That agreement between paper and interview is precisely what a stage 2 audit samples for.
Findings that carry their evidence
Whether it's a gap assessment, an internal audit you deliver as a service, or a supplier evaluation — a finding that says "Training records were incomplete" is an opinion with no survival value. Under later scrutiny nobody can establish what you looked at, what "incomplete" meant, or whether it got fixed.
A finding that survives names four things: the requirement (specifically — the clause, the customer flow-down, the client's own procedure), what was examined (which records, what period, what sample), what was found, and what would close it. That structure isn't bureaucracy; it's what lets a stranger — auditor, successor, skeptical owner — reconstruct your reasoning and arrive at your conclusion. Work a stranger can re-derive is the definition of audit-proof.
It also, not incidentally, protects you. When a client disputes a finding six months later ("you never told us that"), the finding with its evidence trail settles the conversation. The finding without one becomes your word against their memory.
Version your deliverables like you'd tell clients to
There's a special irony in a consultant teaching document control out of a laptop folder containing GapAssessment_Final_v2_USE-THIS-ONE.docx. When your client's auditor asks which revision of the assessment drove the corrective action plan, and the honest answer involves archaeology through your email sent-items, the physician has failed to heal himself.
Deliverables need what controlled documents need: an identity, a revision, a date, and a record of what changed. When the assessment is revised after client feedback, that's a new revision with a note — not a silent overwrite. This is exactly the discipline you're being paid to install; practicing it on your own work products is both credibility and, eventually, legal cover. (It's also, full disclosure, a thing we're building directly into Norma's consultant platform — versioned assessments that seal at completion, so which version said what, when stops being a question at all.)
Write for the reader who signs, and the reader who checks
Every deliverable has two audiences with opposite needs. The owner reads one page and decides whether to fund the plan; the quality manager and the eventual auditor read every appendix. Serve both explicitly: a one-page summary in operational language — what's strong, what's exposed, what it costs to fix, in what order — followed by the full findings with their evidence, cross-referenced. What kills reports is the compromise middle: forty pages uniformly pitched at nobody in particular.
And in the summary, resist the consultant's occupational hazard: grading on effort. If the corrective action process doesn't close the loop, say so in the summary the owner reads — not softened into "opportunities exist to enhance the effectiveness of..." on page thirty. The auditor who eventually visits will not soften it, and the client will remember which of you told them first.
The quiet compounding return
Deliverables that survive audits change your business model. A CB auditor who walks a client system and finds it coherent, honest, and traceable doesn't refer you — they can't, impartiality rules — but the client walks out of that audit telling every owner they know who built their system. Your work gets audited in front of witnesses a few times a year, forever. Build accordingly: the audit room is the one marketing channel where you're always represented by exactly what you actually did.