Process-based auditing follows how work produces a result and examines the connected environmental management arrangements along that route. It can reveal weaknesses between departments that a document-by-document review misses. The approach still needs defined objectives, criteria and a way to maintain coverage.
The internal audit guide explains audit fundamentals. The guide to audit evidence explains how to evaluate information. This article applies those ideas to a practical trail across a process.
Choose a process with a clear result
Define what the process is intended to achieve and where it begins and ends. Receiving materials, managing a change or responding to an incident can provide useful starting points.
Avoid treating a department name as a complete process description. Purchasing may contribute to several processes, while one material introduction can cross purchasing, engineering and operations.
State the environmental management question. For example, the audit might examine whether a new material receives appropriate consideration before ordering and whether the resulting arrangements reach users.
Map the relevant interactions
Identify inputs, decisions, activities, outputs and handovers. Consider who supplies information, who approves action and who uses the result.
Keep the map proportionate. It should guide enquiry, not become an elaborate diagram disconnected from the assessment. A short sequence can be sufficient where responsibilities are simple.
Include relevant outsourced interfaces. A contractor may carry out a task while the organisation retains decisions about specification, access or communication. The audit needs to understand the actual arrangement.
Connect criteria with the process
Identify the applicable EMS requirements and the organisation’s established arrangements at relevant points. A process trail can examine several criteria through one example.
Do not discard requirements coverage because the method is called process-based. Use a coverage map or working record to show which questions were assessed and which require another trail.
Conversely, avoid interrupting every interview to follow clause order. The audit can investigate how the process works, then evaluate the evidence against the relevant criteria.
Follow one example through the handovers
For a fictional workshop, select a recently introduced cleaning material. Trace who requested it, what information was obtained and how its environmental interactions were considered.
Then follow the decision into purchasing, delivery, storage, use and relevant output handling. Ask how affected staff received information and what verification occurred after introduction.
The example tests connected implementation. It does not establish that the material is suitable or legally authorised without appropriate technical evidence and applicable requirements.
Look for information lost between functions
A department may complete its own task while the next team lacks essential information. An approved specification may never reach receiving, or a revised instruction may not reach a contractor.
Examine what each recipient actually obtains and uses. Ask who confirms that the handover is complete and what happens when information is missing.
Do not infer the cause immediately. A weak interface can involve ownership, systems access, timing, competence or conflicting local arrangements. Establish the facts before writing the finding.
Compare intended and actual operation
Use documents to understand the planned process, then test it through records, interviews and observation. Differences can reveal either a weakness or an authorised variation that needs explanation.
Ask about workarounds and temporary conditions. The process used during a rush order or maintenance period may differ from the standard route.
Record relevant limits. If the selected example covers only one location or shift, consider what additional evidence is needed before reaching conclusions about a wider process.
Examine outcomes and evaluation
Ask how the organisation knows the process achieved its intended result. Completion of a sequence does not automatically demonstrate effective environmental management.
For the material example, the question might concern whether identified controls were implemented and whether early operating evidence supported the assumptions. Relevant monitoring or feedback can help.
Distinguish process effectiveness from a broad claim of improved environmental performance. The conclusion should match the objective, measures and evidence available.
Expand the trail where evidence justifies it
If a handover fails, examine whether similar cases or related processes share the weakness. Additional sampling can help understand extent.
Do not expand so far that the original objective is lost without a planning decision. Significant new issues may need a separate assessment or revised scope.
Explain any material change in the audit plan. Readers should understand why the assessor followed an unexpected trail and what that change means for coverage elsewhere.
Report the system connection
Describe the criterion, evidence and relevant interface in the finding. Avoid assigning a process failure automatically to the last person in the chain.
A report stating that staff need more awareness may be weak where the actual evidence concerns an approval system that does not distribute the required information. Describe the established gap and leave cause investigation open.
Include supported strengths as well. A reliable handover mechanism may be useful elsewhere, subject to checking local differences.
Use the result beyond one department
Share relevant conclusions with the functions that control the process and the management able to resolve cross-functional barriers.
Follow corrective actions through the same interfaces. A local procedure revision may not address a shared system problem or an unclear authority relationship.
Process-based auditing is useful when it makes these connections visible. It complements requirements coverage by showing how planning, decisions, work and evaluation operate together, rather than allowing each department’s completed document to stand in for the performance of the whole process.