Documentation your staff can follow
Procedures, registers and forms written with the people who do the work, controlled from the first draft and kept to the size the job needs.
- Written with
- The person who does each job
- Controlled from
- Version 1, on the master list
- Language
- Arabic, English or bilingual, decided per document
- Standards
- 9001, 14001, 45001, 22000, HACCP, 27001 readiness
- Timeline
- Set from the gap report and the processes in scope
Management system documentation is the policies, procedures, registers and forms that describe how your organisation works and prove that it did. We write them with the person who does each job, keep them as short as the standard allows, and put them under document control from the first draft.
- 01 Enquiry
- 02 Gap analysis
- 03 Plan
- 04 Build
- 05 Embed
- 06 Internal audit
- 07 Close out
- 08 Management review
- 09 Handover
Documentation your staff can follow sits at step 4 of the readiness cycle. You receive the documented management system.
Bought documentation describes someone else
A downloaded template set describes an imaginary company. It passes a desk review and fails the first time an auditor asks a supervisor to walk through the procedure.
Staff do not follow documents that do not describe their work. The system becomes paperwork that sits beside the real operation, and the gap shows every time somebody is asked how a job is actually done.
The other failure is size. A procedure for every clause, a form for every procedure, and a manual that repeats the standard back to itself. Every extra document is one more thing to keep current, and the ones nobody reads are the first to go out of date.
Size is not rigour. The standards ask for documented information where the system needs it to work and where evidence is required. Anything past that is weight your team carries for no reason.
How much documentation you actually need
Less than most people expect. A small company can run ISO 9001 on a few dozen controlled documents. We tell you which ones the standard requires and which are your choice.
| Layer | What it is | Who decides it exists |
|---|---|---|
| Policy and scope | Short statements the standard requires you to hold as documented information, with your objectives beside them. | The standard |
| Procedures | Written where a process would go wrong without one. ISO 9001 itself asks for very few. | The risk in the process |
| Work instructions | At the point of work, for the tasks where a missed step causes a defect, a spill or an injury. | The supervisor who runs the job |
| Forms and registers | The records that prove the work happened, designed to be filled in at the point of work in seconds. | The standard, your customers and your regulator |
| Everything else | Material the standard does not ask for and nobody uses. It comes out, with the owner's agreement. | Nobody, which is why it goes |
What you hold at the end
The master document list
Every controlled document with its number, revision, owner and where it is issued. It is the first thing an auditor asks for.
Procedures, each with a named owner
The owner helped write it and can walk an auditor through it without reading from the page.
The registers
Risks, legal requirements, training, calibration and suppliers, whichever your standard and operation need, set up with live entries rather than empty headings.
The forms
Designed around the job, numbered and revision-marked, and tried on the floor before they are issued.
The document control procedure
Short enough to run. It says who approves, how old revisions come off the wall and how long records are kept.
Five steps to one controlled document
- 01
Process walk
We follow the work on the floor before writing anything. The draft starts from what happens, not from the clause.
- 02
Draft with the owner
The person who does the job reviews the draft in their own words. If they would describe it differently, the document changes.
- 03
Cut to size
Anything the standard does not require and the job does not need is removed.
- 04
Form design
Records are designed to be filled in at the point of work, in seconds, by the person standing there.
- 05
Control
Numbered, approved, issued and listed on the master list from version 1.
A manual nobody had opened in a year
A 60-person manufacturer holds a 400-page manual bought from a previous consultant. Nobody has opened it in a year.
We walk the processes first: goods in, production, dispatch and maintenance. Each procedure in the old manual is read against what the floor actually does. Where it matches, it stays and gets an owner. Where it describes a process the plant does not run, it goes.
The replacements are drafted with the supervisor or operator who does the work. Forms are rebuilt so they can be completed at the machine, and each one is tried on a shift before it is issued.
The client ends up with a set that is a fraction of the old size. Every procedure has an owner who helped write it, every form is in use on the floor, and all of it sits on one master list at a controlled revision.
What buyers ask first
Can you write it all without our staff?
We can, and it shows the first time an auditor asks a supervisor to walk through a procedure. The hours your people spend reviewing drafts are what make the documents true.
Do you use templates?
We start from structures we know work, and every document is rewritten around your process. A template gives the layout. The content comes from your floor.
Can you write in Arabic?
Yes. Documents can be bilingual or Arabic-only, and the language is decided per document by who uses it. A work instruction for the line is written in the language the line reads.
Can you keep what we already have?
Usually some of it. Anything that describes real work and has an owner is kept and brought under control. The rest is replaced, and the gap report says which is which before we start.
How long does it take?
It depends on how many processes are in scope and how much of the system already runs. The gap report counts the documents needed, and the implementation plan puts a date against each one.
Who keeps the documents current after you finish?
Your document owners, working to the document control procedure. Each document names its owner and the master list shows who approves a change. If you want a hand keeping it current, that is what surveillance support covers.
Before and after the documents
Gap analysis
Tells you what already exists before anything is written.
Read moreServiceDocument control
The rules that keep the set current once it is issued.
Read moreServiceInternal audit
Tests whether the documents match what happens on the floor.
Read moreITF TrainingDocument control course
Trains the person who will own your master list.
Read morePart of one system
Every division keeps records to the same standard, so the second one you need works the way the first one did.
Start from what already runs
A gap call tells us how much of your operation is already documented, on paper or only in people's heads. The documentation plan starts from that answer.