If you work in aviation, rail, energy, chemicals or a utility, the hiring manager reading your CV has one quiet question underneath all the others: will this person make the site safer, or riskier? Most candidates answer it with a line like "zero incidents in five years", which says almost nothing about their work. There are better ways to show a safety record, and every one of them is something you actually did.
Why "zero incidents" is the wrong headline
It feels like the strongest claim you can make. To an experienced safety reader it is often the weakest, for two reasons.
First, an incident-free period is a system outcome, not a personal one. It belongs to the crew, the maintenance regime, the design of the plant, the permit-to-work system and a fair amount of luck. Claiming it as your achievement suggests you see safety as an absence of bad news rather than something people build every shift.
Second, a low incident count can mean under-reporting. Anyone who has worked in a mature safety culture knows that a healthy site often shows more reported events, at least for a while, because people trust the system enough to speak up. A candidate who boasts of zero incidents invites an obvious follow-up: zero occurred, or zero reported? You do not want an interviewer wondering whether your team was afraid to tell you things.
You can still mention a site's record as context, for example "site with no lost-time injuries since 2020" (an illustrative line, not a target). Just keep it out of the achievement column, and never with your name attached as the cause.
Show what you did to make the work safer. Let the reader infer the outcome.
What a safety record looks like on paper
A safety record, on a CV, is the trail of things you contributed to. Most people in these roles have plenty of it and never write it down, because it felt like "just the job". Go through the categories below and note anything you can evidence.
Audits and inspections
Name the audit, your role and the result. Internal audits count, and so do regulator inspections, customer audits and certification audits against standards such as ISO 45001. "Prepared the maintenance base for its annual authority audit; closed all findings within the agreed window" is specific and checkable. If you led audits of other teams or contractors, give that its own line. Auditing others is a stronger claim than being audited.
Procedures you wrote or rewrote
Writing a procedure is some of the clearest evidence you can offer, because it means someone trusted your understanding of the hazard. Mention the type of document (method statement, isolation standard, permit-to-work procedure, emergency response plan) and what changed in practice because of it. If a procedure you rewrote was later adopted at other sites, say so plainly.
Near-miss reporting you encouraged
This is where you show culture instead of claiming it. If you introduced a simpler near-miss card, pushed to get reports from the night shift, or made sure every report got a reply, write that down. An illustrative line: "Introduced a weekly near-miss review at shift start; reporting rose clearly over the first quarter as the crew saw issues being fixed." Notice that the rise in reports is the good news here, and a safety manager will read it that way.
Investigations you led or supported
Root cause analysis is a skill hiring managers actively look for. Name the method if you used one (5 Whys, fishbone, a formal RCA framework), your role, and the kind of corrective actions that came out of it. Keep the details of the event itself off the CV. The method and the follow-through are the point.
Training you delivered
Toolbox talks, inductions for new starters, contractor briefings, emergency drills you organised. Delivering training is different from attending it, so keep the two apart. A course you sat belongs in your training section; a course you ran belongs under the role.
Showing safety culture through behaviour
Safety culture is the hardest thing to put on a CV because it lives in small decisions. The way through is to describe behaviour, not attitude. "Strong safety mindset" is filler that appears on thousands of CVs. Lines like these are not:
- Stopped a job because the permit did not match conditions on the ground, then reworked the sequence with the planner.
- Set up a short pre-shift briefing that always included one open question for the crew, not just announcements.
- Brought contractors into the near-miss process instead of keeping it staff-only.
- Replied personally to every report within 48 hours, so nobody felt their report had vanished.
A stop-work decision deserves a moment of thought before it goes on the page. It shows judgement, and most safety managers will read it that way. Write it plainly, without making the person or team you stopped look careless.
Before and after: rewriting the usual bullets
Here are a few typical bullets and stronger versions. The figures are illustrative only; use your own, and only ones you can back up with a document or a reference.
Before: Responsible for health and safety on site. Zero incidents during my tenure.
After: Ran the site safety programme for a crew of around 40, including weekly inspections, monthly toolbox talks and the contractor induction. Site gained ISO 45001 certification during this period.
Before: Excellent safety record.
After: Led three incident investigations using a structured root cause method; corrective actions included a redesigned isolation checklist now used across the region.
Before: Ensured compliance with all regulations.
After: Rewrote the confined-space entry procedure after an internal audit finding; no findings on that procedure at the following external audit.
The "after" versions give a reader something to ask you about, and that is the aim. A safety interview is a conversation about specifics, and your CV sets the agenda. Putting numbers on achievements in general is covered in our guide on how to quantify achievements on your CV; here, keep figures modest and verifiable.
If you were involved in an incident
Most people with long careers in high-hazard work have been close to something going wrong. You do not need to put an incident on your CV. If it comes up in an interview or a reference conversation, the honest answer is almost always the best one.
A structure that works:
- State briefly what happened and your role, without minimising or dramatising.
- Describe what the investigation found, including anything you got wrong.
- Explain what changed afterwards, in the system and in how you work.
Avoid blaming named colleagues, and do not share confidential investigation details or anything still under legal or regulatory review. "I can't go into the investigation itself, but I can tell you what we changed" is a perfectly professional line. Interviewers in these sectors know that a candidate who has learned from an event can be a safer hire than one who claims never to have seen one.
If an event led to formal action against you personally, check what the role legally requires you to disclose and answer accurately. Being found out later does far more harm than the event itself ever would.
Where it goes on the CV
Put safety evidence inside each role, as bullets next to your operational work, rather than in a separate safety box at the bottom. In these sectors safety is part of the job, and the CV should look that way. A short summary line near the top can flag it, for example: "Operations engineer with a track record in audit readiness and incident investigation."
Some things live elsewhere. Licences, tickets and medicals belong in their own section, which our guide to field and site-based roles covers. Professional registration is the gate for many regulated roles and has its own article. Keep the experience section for what you did.
If your LinkedIn profile already lists these projects, a tool like Postulit can pull them into a first CV draft, which you then tighten into safety evidence along the lines above.
The takeaway
Before your next application, open your CV and search for the word "zero". Replace every zero-incident claim with one thing you actually did: an audit you prepared, a procedure you wrote, a report you followed up, an investigation you led. Then read each bullet and ask whether a safety manager could question you on it for five minutes. If they could, it stays. If they could not, rewrite it until they can.