How to prepare process documentation for an audit
Prepare process documentation for an audit by checking that every process map names an owner, a current approved revision, and the record that proves it was followed. See a worked CAPA process in QueryChart.
Auditors do not read your process maps for style. They test whether each one is current, owned, approved and backed by records, so prepare the documentation against those four questions.
The short version
- Auditors sample a record and walk back to the procedure, so prepare the trail, not the folder.
- Every map should show an owner for each step, an approved current revision, and labelled decision outcomes.
- Name the record each step produces; a step with no record cannot be evidenced.
- Look for the loop-back: a corrective action that is never verified is the usual finding.
Prepare for the questions, not for the folder
Most audit preparation is a tidy-up: collect the procedures, check the dates, print what is asked for. It fails at the first sampled record, because an auditor starts from the work and walks back to the document, not the other way round. They pick a corrective action from last quarter and ask which procedure governed it, who approved that revision, and where the evidence is.
So prepare along that trail. For each process in scope, confirm that the map shows who does each step, that the revision on display is the approved one, that every decision has labelled outcomes, and that every step that creates a record says which. A map that cannot answer those four points will be talked about at the closing meeting, whatever its layout.
The example below is a CAPA process, a favourite sampling target because it crosses owners, decisions and records. It is built in four passes, each one adding something an auditor will test: the trigger and its log entry, the root cause rather than the symptom, the approval before action, and a check that the fix worked.
A CAPA process, built along the audit trail
Follow the four things an auditor tests: the trigger is logged, the root cause is found, the action is approved, and the fix is verified.
The trigger is on the record
The chart opens on a raised issue and logs it in the register before anything else happens. An auditor sampling a CAPA starts at that entry, so the log row comes before the investigation, and "Full CAPA required?" is a labelled decision with a documented No.
The root cause, not the symptom
An investigator is assigned with a due date, evidence is gathered, and "Root cause identified?" sends a No back to widen the scope. That return line is what shows an auditor the process does not stop at the first plausible answer.
Approval before action
The plan is drafted, preventive action for similar processes is added, and "Approve plan and resources?" gates the work. A Revise branch loops back to the draft, so a rejected plan has a documented path rather than a quiet re-submission.
Verified, or it is not closed
Documents are updated and staff retrained before the effectiveness check, and "Actions effective?" sends a No back to root cause. Closure follows verification, which is the point most corrective-action findings turn on.
How it works
List the processes in scope with an owner
Write down every process the audit will touch and name one owner for each. A process with no owner has no one to answer the auditor, and it is the first gap they find.
Check each map shows who does each step
Open every chart and confirm each step sits in a named role or lane. In QueryChart the Vertical lane column holds the role, so a missing owner shows up as a step outside every lane.
Confirm the revision on display is the approved one
Compare the revision shown with the approval record. An approved chart that has been edited since is no longer the approved version, and the history should show when and by whom.
Give every decision labelled outcomes
Each decision needs two or more labelled branches, entered as Line text in the same order as Line to. An unlabelled branch cannot be followed from the page.
Name the record at every step that makes one
Add the record to the step text or its notes: the register entry, the signed plan, the verification report. If you cannot name the record, the auditor cannot be shown one.
Trace one real record backwards
Take a recent corrective action and walk it from the evidence back to the map, as the auditor will. Fix what you cannot trace before the audit rather than during it.
Mistakes to avoid
Preparing the folder, not the trail
A complete set of procedures proves that documents exist. The auditor tests whether work followed them, so prepare the path from a sampled record back to the map.
A map that shows the happy path only
If failure, rework and rejection are missing, the chart describes an ideal and the records describe the rest. Draw the loop-backs, since that is where the findings are.
Editing an approved chart the week before
A last-minute tidy-up creates a revision nobody approved. Make the change through review, or leave it and note it as a known improvement.
Related QueryChart feature
Open the CAPA example as your own chart
Open the CAPA process as your own chart, name the owner of each step, and add the record each one produces before your next audit.
Related guides
Frequently asked questions
What do auditors look for in process documentation?
Whether it is current, owned, approved and followed: an owner for each process, a revision with an approval record, decisions that can be traced, and records that show the work was done as described.
How early should I prepare process documentation for an audit?
Long enough before to fix what you find, which for most teams means starting a few weeks ahead. The tracing exercise in the last step usually turns up gaps that take time to close.
Do I need a flowchart for every process?
Not necessarily. Standards such as ISO 9001 ask for documented information where it is needed to operate and show control, not a chart for everything. Chart the processes where a picture shows ownership and decisions more clearly than prose.
Can I just show the auditor the chart on screen?
Often yes, if the revision, approval status and history are visible with it. A chart whose approval and change history are on the same page answers several questions at once.