04 / Documentation
Documentation that describes what you actually do
Manuals, procedures, forms and records written around your operation, and structured so your team can keep them current after we've gone.
Documented information is one of the most consistent sources of audit findings, not because companies don't write things down, but because what's written drifts from what happens. Outdated master lists, uncontrolled forms in circulation, records that exist but can't be located during an audit.
The other failure mode is the opposite: a purchased template pack that describes a textbook company. An auditor walks the floor, compares it to the procedure, and writes a finding. Documentation only protects you when it's true.
What we write
The documentation set
Exactly what's needed depends on the standard and your scope. This is the usual shape of it.
- Scope and context
Scope statement, interested parties, and the process map that shows how work actually flows. The document auditors check against reality first.
- Procedures and work instructions
Written from watching and asking how the job is done, at the level of detail the people doing it will actually read.
- Forms and records
The logs, checklists and reports that generate your evidence — designed so filling them in is the natural way to do the work.
- Document control
Master list, revision control, approval and retention, so the system doesn't decay between audits.
- Standard-specific documents
Focus Material plans and downstream flowcharts for R2v3; risk registers, objectives and management review packs for ISO.
You own it, in formats you can edit
Everything we write is yours, in editable files, with a handover session so your team can revise it without breaking document control.
We're not interested in documentation you have to come back to us to change. A system that can only be maintained by its consultant is a system that decays the moment the engagement ends.
Already have documents? Often the right job is rewriting a subset rather than starting over. A short review tells you which are usable, which are dangerous, and which are missing.
Questions
Common questions
Do you sell document templates?
No. We write documentation as part of an engagement, built around your operation. Generic template packs are a common source of findings, because the procedure describes a company that isn't yours.
What format do we get?
Editable files your team can maintain, typically word processor and spreadsheet formats — along with a document control structure and a handover session.
Can you fix documentation we already have?
Yes, and it's often cheaper than starting fresh. We review what exists, keep what works, rewrite what doesn't and add what's missing.
How much documentation does the standard actually require?
Less than most people assume. Modern ISO standards specify required documented information and otherwise leave the level of detail to you. Over-documenting creates maintenance burden and more ways to be nonconforming.
Next step
Need documentation that survives an audit?
Send us what you have, or tell us you're starting fresh. We'll tell you honestly how much writing is actually required.