What this is
What is a process audit, and how is it different from a clause-based audit?
What is a process audit, and how is it different from a clause-based audit?
A clause-based audit checks a management system standard clause by clause, usually within one department at a time. A process audit instead follows one process — permit to work, contractor management, whichever is due its turn — from its trigger through every function it touches, deliberately crossing department lines rather than stopping at them. It is slower to plan but tends to surface failures a clause audit walks straight past.
What counts as a handoff in this audit?
A handoff is any point where responsibility for the process moves from one function to another — production releasing product to quality, maintenance returning equipment to production, procurement passing a new supplier to quality for approval. Each one gets its own row: the two functions involved, what triggers the handoff, and whether responsibility and information were actually clear when it happened.
Who is qualified to carry out a process audit?
A trained auditor who is independent of the process being audited — not its owner, and ideally not someone reporting into the same function. ISO 19011 treats independence as a core principle precisely because a process owner auditing their own process tends to find what they already believe is there.
Scope
When is a process audit record required?
This audit is one step in a larger programme. Using it for work that belongs to a neighbouring template produces records that are hard to report on later.
Use this template when
- A specific process — not a whole management system — needs auditing end to end, including where it crosses departments
- The audit programme schedules this process for its turn, or a finding elsewhere points at a systemic gap in it
- The auditor assigned is independent of the process being audited
- A new record is needed; each one gets its own ID in the form AUD-2026-000
- A linked record needs this one to exist: it links to Job and Clause, and feeds Finding
Do not use it for
- Internal Audit Programme, which sets out what will be audited, when, by whom and against which standard, across the year — this record is one line inside that plan, not the plan itself.
- Internal Audit Report, which records a standard clause-by-clause audit rather than a single process walked end to end.
- Audit Plan, which sets the scope, criteria and people for a single audit before it runs — use it to plan this audit, not to record it.
- Audit Finding Record, which tracks one nonconformity through to closure once this audit has raised it — don't manage a finding's follow-up inside this form.
- Anything outside KnowComply's remit, which belongs in the workspace that actually owns the process being audited.
Compliance mapping
Which ISO 19011 requirements does this satisfy?
ISO 19011 does not certify anything; it sets the method by which any audit — including this one — is planned, evidenced and concluded. The mapping below follows the record's own sections.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 19011:2018 cl.6.4.2 | The auditor assigned to the audit is independent of the process under audit. | Header |
| cl.4 | Auditing rests on principles of integrity, independence and an evidence-based approach — they apply to how this record gets completed, not only to what it reports. | Header |
| cl.6.4.6 | Documented information for the process — its inputs, outputs, owner and interfaces — is reviewed before conclusions are drawn. | Process definition |
| cl.6.4.7 | Information is collected and verified by observing the process as it actually runs, not solely by interview. | Process as performed |
| cl.6.4.7 | Verification extends across the process's interfaces with other functions, not just its interior. | Handoffs |
| cl.6.4.9 | Audit conclusions weigh whether the process reliably achieves its intended outcome, not only whether it was followed. | Performance |
| cl.6.4.8 | Findings are generated against objective evidence and evaluated against audit criteria, recorded whether or not they were corrected immediately. | Findings |
| cl.6.4.9 / cl.6.7 | The audit is formally concluded — result, completeness and any follow-up action determined and signed off — before it is treated as closed. | Result |
What it does not cover
- An audit that stops at the department boundary, which leaves every handoff — where responsibility and information actually get lost — unexamined.
- A Practice Matches Documentation of Yes with no time spent watching the process run, which converts an audit into a paperwork check.
- A Deviation Cause left blank against an observed deviation, which stops the fix from ever being the right one.
- A Fail result with Fixed On The Spot marked Yes and no Finding ID raised, which lets a real nonconformity vanish without a record anyone can trace.
- An Auditor who is also the Process Owner, which breaks the independence the whole exercise depends on.
Global
Process Audit Record requirements by country
ISO 19011 is the method wherever the site sits; what changes by geography and scheme is how hard a process audit specifically gets checked for.
ISO 19011:2018
sets the generic method for planning, conducting and reporting any audit; it is not itself a certifiable standard
This record's structure — evidence, findings, conclusion — exists because 19011 requires it, not because a management-system standard alone does.
ISO 22000:2018 cl.9.2
requires internal audits at planned intervals to confirm the food safety management system conforms and is effectively implemented
A process audit like this one is one route a site uses to satisfy that clause, provided it actually covers the process end to end rather than one department's slice of it.
BRCGS Food Safety Issue 9, cl.3.4
requires an internal audit programme covering all processes and areas, with an announced and an unannounced element
A process audit that never leaves the desk fails this requirement even if the paperwork looks complete.
How to complete it
How to complete a process audit record, step by step
Filling in every field is the easy half. The judgement calls below are what decide whether the finished record would survive someone else reading it months later.
Pick the auditor who doesn't own the process, even when the process owner 'knows it best' and the schedule would be easier if they audited themselves.
Deciding Practice Matches Documentation needs firsthand observation of the process running, ideally at a handoff, not an interview taken at face value.
Fixed On The Spot closes the instance; it says nothing about recurrence. The judgement is whether the fix addressed the root cause or just today's occurrence — the latter needs a traceable Finding ID even if it was fixed on the spot.
From and To should reflect where responsibility actually sat, not whichever department is easier to name, and Delays Or Losses Observed should reflect a genuine pattern rather than one bad day being read as routine friction.
What auditors find
Most common process audit record findings
Patterns that show up repeatedly once process audit records are reviewed as a set, rather than one at a time.
| Finding | Clause | What fixes it |
|---|---|---|
| Handoff rows completed for only one direction of a process that crosses four functions. | ISO 19011:2018 cl.6.4.7 | Require one Handoffs row per interface actually identified in Process definition, not just the first one the auditor happened to see. |
| Process Documented marked Yes while Practice Matches Documentation is marked No, with Deviation Cause left blank. | cl.6.4.6 / cl.6.4.7 | Force Deviation Cause whenever Practice Matches Documentation is anything but Yes. |
| Auditor populated with the same name as Process Owner. | cl.6.4.2 / cl.4 | Cross-check Auditor against Process Owner at submission and block the record if they match. |
| Fail results in Findings with Fixed On The Spot marked Yes and no Photo Evidence attached. | cl.6.4.8 | Require Photo Evidence for any Fail regardless of whether it was fixed immediately — the record is the only proof the fault existed. |
| Score Percent reported without Completeness Percent, as if the score stood alone. | cl.6.4.9 | Surface Completeness Percent alongside Score Percent everywhere the score is reported, so a high score on a half-finished audit can't pass as clean. |
| Action Required marked No on a Result Band of Fail. | cl.6.4.9 | Block No on Action Required whenever Result Band is Fail; a failed process audit cannot close itself. |
Case in point
Case in point: the audit that passed because nobody asked what happened at the fence line
A site ran a process audit on its cutting-to-packing line. The auditor walked cutting room practice against the documented procedure, scored it, then walked packing the same way. Both scored well: Process Documented Yes, Practice Matches Documentation Yes, People Understand Their Part Yes. The audit was on track to close clean.
It was only when the auditor filled in a Handoffs row — From: Production, To: Packing, Handoff Trigger: batch release — that the gap appeared. Responsibility Clear At Handoff came back Ambiguous: packing assumed cutting had checked temperature before release, cutting assumed packing would check it on arrival. Neither had, for weeks. Two individually compliant departments made a process that, walked end to end, wasn't.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
7 sections
- Reference
- CMP-007
- Archetype
- Audit
- Record ID
- AUD-2026-000
- Scoring
- Weighted percent
- Direction
- High is good
- Singleton
- No
- Basis
- ISO 19011
- Links
- Links Job, Clause; feeds Finding
- Tags
- Audit, Process
- Sections
- 7
- Fields
- 57
- Follow up fields
- 9
- Repeating sections
- 2
- Links out
- 3
Header
12 fieldsAudit ID*
Auto sequence. Format AUD-2026-00000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date and Time*
Completed By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Area
The area within the site.
Exact Location
Drop a pin for anything hard to find.
Follow The Process, Not The Department
A process audit crosses departments deliberately. Most system failures live in the handoffs, which nobody owns and nobody audits.
Process Audited*
Process Owner*
Auditor*
Process definition
6 fieldsProcess Documented*
- Yes3 pts
- Partly1 pt
- No0 pts
Inputs And Outputs Defined*
- Yes3 pts
- Partly1 pt
- No0 pts
Owner Clearly Assigned*
- Yes3 pts
- Ambiguous1 pt
- No0 pts
Interfaces With Other Processes Defined*
- Yes3 pts
- Partly1 pt
- No0 pts
Performance Measures Defined*
- Yes3 pts
- Partly1 pt
- No0 pts
Risks And Controls Identified*
- Yes3 pts
- Partly1 pt
- No0 pts
Process as performed
6 fieldsPractice Matches Documentation*
- Yes3 pts
- Partly1 pt
- No0 pts
Deviations Observed
Deviation Cause
Documentation wrong, documentation impractical, training gap, or deliberate workaround. Each needs a different fix.
- Documentation wrong1 pt
- Documentation impractical1 pt
- Training gap1 pt
- Deliberate workaround0 pts
People Understand Their Part*
- Yes3 pts
- Partly1 pt
- No0 pts
Know Why Not Just How*
- Yes3 pts
- Partly1 pt
- No0 pts
Know What To Do When It Goes Wrong*
- Yes3 pts
- Partly1 pt
- No0 pts
Handoffs
Repeats6 fieldsFrom*
To*
Handoff Trigger*
Responsibility Clear At Handoff*
- Yes3 pts
- Ambiguous1 pt
- No0 pts
Information Complete At Handoff*
- Yes3 pts
- Partly1 pt
- No0 pts
Delays Or Losses Observed*
- None3 pts
- Some1 pt
- Frequent0 pts
Performance
6 fieldsMeasures Actually Used*
- Yes3 pts
- Collected not used1 pt
- No0 pts
Targets Being Met*
- Yes3 pts
- Partly1 pt
- No0 pts
Data Reliable*
- Yes3 pts
- Questionable1 pt
- No0 pts
Process Achieving Its Purpose*
- Yes3 pts
- Partly1 pt
- No0 pts
Improvement Opportunities Identified*
Waste Or Duplication Observed*
- None3 pts
- Some1 pt
- Significant0 pts
Findings
Repeats7 fieldsResult*
- Pass3 pts
- Pass with conditions2 pts
- Fail0 pts
Severity
- Minor3 pts
- Moderate1 pt
- Serious0 pts
Element Tag
Groups deficiencies by hazard type across every template.
Deficiency Detail
Photo Evidence
Fixed On The Spot
Finding ID
Raise a finding record where this needs tracking to closure.
Links to FDN-015 Finding ID
Result
14 fieldsItems Assessed*
Excludes anything marked N/A.
Items Failed*
Score Percent*
Calculated on submission. High is good. N/A items leave the denominator.
Result Band*
- Pass3 pts
- Caution1 pt
- Fail0 pts
Completeness Percent*
How much of the template was actually answered. A high score on a half completed form is not a high score.
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Next Audit Due*
Auditor*
Signature*
Process Owner*
Second Signature*
CMP-007 · record IDs look like AUD-2026-000 · Links Job, Clause; feeds Finding
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The form captures one audit. Keeping every process on its scheduled turn, routing findings to the right owner, and holding the evidence together across a whole programme is the work that actually slips.
Holds the process audit library against the schedule, tracks which processes are due their turn, and keeps Findings linked through to closure rather than left sitting in the record that raised them.
Where the audited process is incident management, risk assessment or permit to work, KnowSafe holds the underlying records this audit is checking against, so a Fail here can point straight back at the source.
When Maintenance planning is the process under audit, or Maintenance shows up on a Handoffs row, KnowMaintain holds the schedules and work orders the audit is comparing practice to.
Coordinates the crew across a process audit that spans departments, rolls the handoffs and findings into one view, and holds every write for approval before it touches a live record.
This template lives in KnowComply — audit and governance. Audit programmes, legal register, management review, risk and certification.
Meet KnowComply→Glossary
Process Audit Record definitions and key terms
- Handoff
- The point where responsibility for a process moves from one function to another — the specific moment this audit is built to examine, because it is where clause-based audits typically stop looking.
- Process owner
- The person accountable for how the process runs day to day. They are interviewed and observed during the audit but should not be the one conducting it.
- Root cause vs correction
- A correction fixes the instance in front of the auditor; a root cause fix stops the same deviation happening again elsewhere. Deviation Cause exists to force the second question, not settle for the first.
- Independence (auditing)
- The requirement that whoever conducts the audit has no stake in its outcome — not the process owner, and ideally not a peer in the same reporting line.
- Deviation
- Any point where what actually happens differs from what the documented process says should happen, whether or not it causes a fail.
FAQ
Frequently asked questions about process audit record
Does a process audit replace the clause-based Internal Audit Report?+
No — they answer different questions and normally run on separate schedules within the same programme. A clause audit confirms a management system standard is being met; a process audit confirms one process works end to end, including where it crosses departments a clause audit wouldn't naturally follow.
What happens to a Fail that gets Fixed On The Spot?+
Photo Evidence and Deficiency Detail should still be captured, and a Finding ID is only required when Fixed On The Spot is No — but many teams raise the finding anyway when the deviation is likely to recur, since fixing it on the spot says nothing about whether it happens again tomorrow.
How is the Score Percent actually calculated?+
It's calculated on submission from the scored fields across Process definition, Process as performed, Handoffs, Performance and Findings, with anything marked N/A dropped from the denominator. It is a weighted percentage, not a simple average — some fields carry more weight than others.
Can Area and Process Audited be left blank?+
Process Audited is required — every audit needs a defined process to be a process audit. Area is optional, useful mainly where the process runs across a specific physical zone rather than the whole site.
Who should be assigned as Auditor?+
Someone independent of the process, trained to conduct the audit, and not the same person named as Process Owner. Auditor Competency Record is the place that establishes someone is qualified to hold the role in the first place.
Can this template be adapted for a non-food site?+
Yes — the Area and Process Audited option lists ship food/manufacturing-flavoured out of the box (cutting room, boning hall, sanitation), but every field and option is editable. The structure — process definition, practice, handoffs, performance, findings — holds regardless of sector.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Internal Audit and Certification
Internal Audit Programme
Sets out what will be audited, when, by whom and against which standard, across the year
Internal Audit Report
Records an internal audit against a standard or process, with findings and evidence
Audit Plan
Sets out the scope, criteria, schedule and people involved for a single audit
Audit Finding Record
Records a single audit finding with its evidence, clause reference and classification
Audit Follow Up Record
Checks whether audit findings have actually been closed and the fixes work
Auditor Competency Record
Records an internal auditor's training, experience and audits performed
More in Internal Audits
Internal Audit Programme
Sets out what will be audited, when, by whom and against which standard, across the year
Internal Audit Report
Records an internal audit against a standard or process, with findings and evidence
Audit Plan
Sets out the scope, criteria, schedule and people involved for a single audit
Audit Finding Record
Records a single audit finding with its evidence, clause reference and classification
Audit Follow Up Record
Checks whether audit findings have actually been closed and the fixes work
Auditor Competency Record
Records an internal auditor's training, experience and audits performed
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- ISO 19011:2018 — Guidelines for auditing management systems
- ISO 22000:2018 cl.9.2 — Internal audit
- BRCGS Food Safety Issue 9, cl.3.4 — Internal audits
- ISO 9001:2015 cl.9.2 — Internal audit
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.