5.1Internal QHSE audit
The essentials in 30 seconds
- Verify, don't punish: the internal audit checks the system's compliance and effectiveness to improve — never to punish.
- Independent and factual: an auditor independent from the audited area, findings based on evidence (shop floor + documents).
- A report that drives action: clear gaps (requirement + evidence + severity) + strengths + follow-up of actions.
Threaded mini-case — Hakim audits the Algiers workshop
Hakim, QHSE officer in a 40-person SME in Algiers, must audit the shipping area before the management review. Instead of checking up on his colleagues, he announces the scope, prepares his guide from the internal framework, observes the shop floor, asks open questions and records 3 evidenced gaps plus 2 strengths. This section tells how he moves from endured control to the audit that drives progress — and the thread continues in 5.2, 5.3, 5.4 and 5.5.
This same case returns in the lesson, diagram, script and 48h challenge — and continues in 5.2, 5.3, 5.4 and 5.5.
1. The audit: verify, don't punish
An internal audit is a methodical, independent examination: an auditor who has not worked in the audited area verifies compliance (framework, regulations, procedures) and effectiveness (do the arrangements really work?). It is announced and planned (annual programme), conducted by sampling: you don't check everything, you probe smartly.
Hakim gets his programme approved by management: scope, objectives, framework. As he never audits his own work, the workshop welcomes him without fear — and shows instead of hiding.
2. The process: opening, shop floor, evidence
The typical flow: opening meeting (scope, method), shop floor + documents (observe, question, trace), closing meeting (gaps presented with no surprises). Questions are open ("show me how…"), never traps: a defensive auditee hides, one who trusts shows.
Hakim observes the floor markings, questions two operators, cross-checks with the posted instruction: every finding rests on a fact, not an impression.
3. The report that drives action
The report formalises the gaps (requirement + evidence + severity: major / minor), the strengths (to share) and the response deadlines. A 20-page unreadable report is useless: 5 clear gaps beat a tome. Follow-up verifies that corrective actions are closed (see 5.2).
Hakim keeps his report to 2 pages, presents it to the workshop, then schedules verification in one month: closed or replanned.
🔎 Concrete example — A 5S audit that transforms
Hakim's 2-page report.
Scope: shipping area, internal 5S framework.
Findings: 3 gaps (worn markings, hidden extinguisher, missing instruction) + 2 strengths (workstations kept tidy, labelled bins).
-> 3 dated actions, 1-month check: closed.Result: gaps + strengths + deadlines: the report fits in 2 pages and drives action.
Lesson: auditing your own area is forbidden (independence bias).
Section vocabulary
- Internal audit
- A methodical, independent examination verifying that a system complies with frameworks and is effective.
Simple example: Hakim audits shipping against the internal 5S framework, planned over the year.
What it is not: a surprise check to punish an operator.
Reflex: is my auditor independent from the audited area?
- Framework
- What reality is compared against: standard, procedures, regulations, requirements.
Simple example: Hakim records the gap between the markings required by the instruction and the worn floor.
What it is not: the auditor's personal opinion with no reference text.
Reflex: which exact text requires what I observe?
- Audit finding
- A factual result based on evidence (observation, document, cross-checked account).
Simple example: Dated photo of the hidden extinguisher + missing instruction at the workstation.
What it is not: "the workshop is careless" with no evidence or reference.
Reflex: each gap = requirement + evidence + severity.
- Independence
- Never audit your own work; guarantee objectivity and credibility.
Simple example: Hakim gets his own office audited by a trained colleague from another area.
What it is not: auditing yourself "because you know best".
Reflex: cross areas in the annual programme.
- Audit report
- A short document: gaps, strengths, deadlines — followed up until closed.
Simple example: Hakim's 2 pages: 3 gaps, 2 strengths, 3 dated actions.
What it is not: a 20-page tome filed with no follow-up.
Reflex: does each gap have an owner and a deadline?
In practice — Conducting an internal audit
- Plan the audit: scope, objectives, framework (standard, procedures, regulations), programme over the year; appoint an objective, independent auditor (not their own work).
- Prepare (study the framework and documents, audit guide) then conduct on the shop floor: observe, question, examine evidence — gather facts, not impressions.
- Establish the findings: nonconformities (gaps against the framework), sensitive points, strengths; formalise a report and present it.
- Ensure follow-up: nonconformities lead to corrective actions (5.2) whose implementation the audit will verify. Stay constructive (improve, not punish).
Ready-to-say script — open the audit without putting backs up (1 min)
"I have no preconceptions: I compare what I see with the framework we approved together. Show me how you do it, with the workstation documents. Everything I note, I show you before closing — strengths too. The goal is to leave with 2 or 3 useful actions, not reproaches."
Say at the opening meeting, calmly; note scope and method on the board.
Copy-paste template — audit finding sheet
SCOPE / DATE: _______________
FRAMEWORK (exact requirement): _______________
EVIDENCE (observation / document / exchange): _______________
GAP (major / minor): _______________
STRENGTH noted: _______________
PROPOSED ACTION + OWNER + DEADLINE: _______________Small business / tight budget
Hakim audits in 1 hour: one area, a one-page framework, 3 findings maximum — paper and photos are enough.
Algeria SME
Hakim crosses areas (production audits shipping and vice versa) to guarantee independence without hiring.
Document audit
When the shop floor is out of reach: sample 5 complete files (requirement + evidence + trace) instead of re-reading everything.
Certification preparation
Rehearse the external process internally (opening, shop floor, closing): gaps found before D-day are worth gold.
✓ Best practices
- Audit independently from the area (never your own work).
- Keep only proven facts (shop floor + documents).
- Stay constructive: clear gaps + strengths + follow-up.
✗ Common pitfalls
- Turning the audit into punishment (fear, cover-ups).
- Auditing yourself (independence bias).
- Issuing a tome-like report with no follow-up (no action closed).
Key takeaways
- The internal audit is a methodical, independent examination verifying that a system complies with frameworks and is effective, to identify gaps and improve.
- Purpose: verify and improve — not punish or find culprits. A progress tool (the Check phase of PDCA) comparing reality with the framework on facts.
- The auditor is objective and independent (never their own work), factual (evidence: observation, interviews, documents, shop floor) and constructive.
- A methodical process: planning, preparation, conducting, conclusions, report, follow-up. Nonconformities lead to corrective actions (5.2).
48h challenge — apply tomorrow
Audit 1 workstation for 30 minutes (finding sheet above): 1 framework, 2 observations, 1 open exchange. Give back 1 gap + 1 strength to the team.
- I can explain audit = verify to improve, not punish.
- I can word a gap (requirement + evidence + severity).
- I ran 1 mini-audit with sheet and feedback.
Frequently asked questions
Can you audit your own workshop?
No: independence builds credibility. You know your own workarounds too well to see them, and the team dare not contradict their direct supervisor. Good practice: cross areas (production audits shipping and vice versa) with trained auditors, even in a small structure.
How do you ask good audit questions?
Openly and through evidence: "show me how…", "which document proves…?". The closed question ("this is compliant, isn't it?") makes people recite, the trap question ("why did you fail?") makes them hide. Open questions show reality — including good practices to share.
Hakim must audit his own workshop, which he knows well. What should he do?