What this is
What is a recognition and reward record?
What is a recognition and reward record?
A recognition and reward record is a record used in KnowSafe that captures recognition given for good safety practice, a good catch or a difficult stop work call. It is built against ISO 45001 cl.5.4 and forms part of the Safety Culture and Engagement programme.
Why does the record score 'Not Tied To Injury Free Periods'?
Rewarding a period without injuries teaches people not to report, because the fastest way to protect an injury-free streak is to stop admitting when something goes wrong. Scoring this field pushes managers to confirm, on every record, that the recognition is for a specific behaviour rather than the absence of a reported incident.
What counts as 'required courage or difficulty'?
It distinguishes a routine good catch from a moment that cost the person something socially or professionally, such as stopping a job a senior person wanted to continue. The form scores the harder case higher because it is the behaviour most likely to be suppressed without visible recognition.
Scope
When is a recognition and reward record required?
This record 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
- The event or activity this record covers has occurred, or is about to
- A new record is needed; each one gets its own ID in the form REW-2026-000
- You are running the Safety Culture and Engagement programme and this is one of its steps
- A linked record needs this one to exist: links Observations, Hazard reports
- Someone has just done something worth reinforcing and the recognition needs to happen this week, not at the next review cycle
Do not use it for
- Safety Climate Survey, which measures how people actually experience safety here, covering trust, reporting, pressure and whether stopping work feels possible.
- Felt Leadership Tour Record, which records a senior manager spending time on the floor talking about safety, and what they heard.
- Safety Conversation Record, which records a short two way conversation about how a job is going and what makes it harder to do safely.
- Behaviour Based Observation, which watches and scores a task against a checklist; recognition is a response to something already reported, not a scoring exercise.
- Anything outside KnowSafe, which belongs in the workspace that owns that process
Compliance mapping
Which ISO 45001 cl.5.4 requirements does this satisfy?
ISO 45001 cl.5.4 requires participation of workers to be genuine, and a large part of what makes it genuine is whether the organisation visibly reinforces the behaviours it says it wants.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 45001 cl.5.4 | Worker participation, including reporting hazards and stopping unsafe work, is actively reinforced rather than merely permitted. | What happened |
| ISO 45001 cl.5.1 | Leadership demonstrates commitment by ensuring good safety behaviour is recognised promptly, not left to chance. | Recognition given |
| ISO 45001 cl.5.3 | The person recognising and the person recognised are both identifiable, so recognition can be traced back to a real event. | Header |
| ISO 45001 cl.7.4 | The story behind a good catch or stop-work call is communicated beyond the individual, reinforcing the behaviour site-wide. | Recognition given |
| ISO 45001 cl.10.2 | Where the recognised event ties to a hazard report, that link is captured rather than the two records existing in isolation. | Related records |
| ISO 45001 cl.10.3 | Recognition data feeds continual improvement, rather than being logged purely as a count of good deeds. | Recognition given |
| ISO 45001 cl.9.1 | The organisation can monitor whether recognition is proportionate to the difficulty or courage involved, not just given for visibility. | What happened |
What it does not cover
- A voucher given for a routine catch with no story attached, which trains people to expect a transaction rather than genuine acknowledgement.
- Recognition given weeks after the event, which the form itself scores lower than a prompt personal thanks.
- 'Not Tied To Injury Free Periods' marked as partly tied and left that way, which is the exact pattern this record exists to catch and stop.
- A stop-work call recognised with no note of what would have happened otherwise, which loses the detail that makes the story worth repeating.
- Recognition confined to the same one or two names on a site, which suggests good catches are being missed or under-recognised elsewhere, not that recognition is scarce.
Global
Recognition and Reward Record requirements by country
ISO 45001 cl.5.4 is the anchor, but how directly the law expects an organisation to reinforce, rather than simply permit, worker participation varies by jurisdiction.
Health and Safety at Work etc. Act 1974, s.2(6); HSE guidance HSG65, Managing for Health and Safety
HSE guidance treats a positive, engaged safety culture — not just compliant paperwork — as evidence of effective management arrangements.
A visible pattern of prompt, behaviour-based recognition is the kind of cultural evidence HSE inspectors look for when assessing whether a management system is more than paper.
OSHA Voluntary Protection Programs (VPP) criteria; OSH Act 1970 General Duty Clause s.5(a)(1)
There is no statutory requirement to run a recognition scheme, but VPP criteria explicitly value programmes that reinforce reporting and stop-work behaviour as leading indicators.
Sites pursuing or maintaining VPP status can point to this record as direct evidence supporting that element of the application.
ISO 45001:2018 cl.5.4 and cl.5.1
Certification auditors look for evidence that leadership commitment to worker participation is active, not declared.
A dated run of recognition records, spread across catch types and people rather than concentrated on a few, is the artefact that demonstrates cl.5.1 leadership commitment in practice.
How to complete it
How to complete a recognition and reward record, step by step
Filling in the fields is quick. The judgement calls are what decide whether recognition reinforces the right behaviour or quietly rewards the wrong one.
'Prevented A Potential Injury' describes what happened, but scoring recognition on that basis alone means a good catch that turned out to prevent nothing gets treated as less deserving. The behaviour — noticing and acting — is what should drive the decision to recognise, not how close the near miss actually was.
The form scores promptness highly, which creates a mild incentive to record recognition as prompt even when it wasn't. Cross-checking the record's creation date against the event date is the only reliable way to know whether recognition is actually landing on time.
'Recognition Type' has six options, but a good catch or a stop-work call is easier to notice and recognise than someone quietly helping a colleague or raising an improvement suggestion. A programme that only ever recognises the dramatic cases is missing most of the behaviour it claims to reinforce.
This field is easy to mark Confirmed by default, since nobody wants to admit the recognition was really about hitting a milestone. Treat a run of records where this is never marked Partly tied with some suspicion — it usually means the question isn't being asked seriously, not that the practice has been eliminated.
What auditors find
Most common recognition and reward record findings
The patterns below turn up repeatedly once a site has been running this record for a few months.
| Finding | Clause | What fixes it |
|---|---|---|
| Recognition is given almost exclusively for 'Good catch' and 'Stop work call', with 'Helped a colleague' and 'Improvement suggested' rarely used. | ISO 45001 cl.5.4 | Prompt supervisors during the monthly review to look specifically for the quieter categories, since they are just as much a target behaviour as the dramatic ones. |
| 'Given Within A Week' is marked Later or No on a majority of records for one site. | ISO 45001 cl.5.1 | Investigate whether recognition is being batched into a monthly meeting instead of given at the point it's earned; the form's own scoring says prompt and personal beats formal and late. |
| 'Shared With The Wider Site' is marked No on almost every record. | ISO 45001 cl.7.4 | Add a briefing slot or noticeboard routine specifically for sharing recognised stories, since a private thank-you does not reinforce behaviour beyond the individual. |
| The same manager appears as both 'Recognised By' and the countersigning 'Site Manager' across most records. | ISO 45001 cl.5.3 | Route the second signature to a different manager by default so the countersignature functions as an actual check rather than a formality. |
| 'Not Tied To Injury Free Periods' is marked Partly tied on several records, all of which still proceed to a Complete status. | ISO 45001 cl.5.4 | Treat a Partly tied answer as a hold, not a pass — it should trigger a conversation with the manager before the record closes, since it flags the exact pattern the template exists to prevent. |
| 'Required Courage Or Difficulty' is answered Routine on almost every record at a site, despite the catalogue description centring on difficult stop-work calls. | ISO 45001 cl.9.1 | Check whether harder stop-work moments are being logged elsewhere, such as in coaching or hazard records, without a matching recognition record ever being raised. |
Case in point
Case in point: the stop-work call that took three weeks to get a thank-you
A machine operator halted a filling line after noticing a guard had been left off following maintenance, overriding a supervisor who wanted to keep production running. The stop-work call was logged as a hazard report the same day, but no recognition record followed.
Three weeks later, at a routine safety meeting, someone mentioned the story in passing and a manager finally raised a recognition record, marked 'Given Within A Week' as No, honestly. By then the operator had told two colleagues that raising it hadn't seemed to matter, which is exactly the message a delayed thank-you sends, whatever the record eventually says.
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.
4 sections
- Reference
- SAF-171
- Archetype
- Record
- Record ID
- REW-2026-000
- Scoring
- Recognitions given
- Direction
- High is good
- Singleton
- No
- Basis
- ISO 45001 cl.5.4
- Links
- Links Observations, Hazard reports
- Tags
- Behavioural, Recognition
- Sections
- 4
- Fields
- 28
- Follow up fields
- 0
- Repeating sections
- 0
- Links out
- 3
Header
14 fieldsRecord ID*
Auto sequence. Format REW-2026-000.
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.
Worker*
Person ID*
Format PER-0000.
Links to FDN-003 Person ID
Recognise Behaviour, Not Injury Free Time
Rewarding a period without injuries teaches people not to report. Recognising a good catch or a difficult stop work call teaches the opposite.
Recognition Type*
Good catch, stop work call, hazard report, helping a colleague, improvement suggestion, or consistent good practice.
Recognised By*
Individual Or Team*
What happened
4 fieldsDescription*
Prevented A Potential Injury*
- Yes3 pts
- Possibly2 pts
- No1 pt
Required Courage Or Difficulty*
Stopping a job that a senior person wanted to continue deserves more recognition than anything routine.
- Yes4 pts
- Some2 pts
- Routine1 pt
Linked Record ID
Thread key
Related records
1 fieldHazard Case ID
The good catch being recognised.
Links to SAF-013 Case ID
Recognition given
9 fieldsForm Of Recognition*
Personal thanks, public recognition, team briefing mention, or a formal award. Personal and prompt beats formal and late.
- Personal thanks from a manager4 pts
- Public recognition3 pts
- Written note3 pts
- Voucher or gift2 pts
- Team celebration3 pts
Given Within A Week*
- Yes3 pts
- Later1 pt
- No0 pts
Shared With The Wider Site*
- Yes3 pts
- No1 pt
Story Used In Training Or Briefing
- Yes3 pts
- No1 pt
Not Tied To Injury Free Periods*
- Confirmed3 pts
- Partly tied0 pts
Recognised By*
Signature*
Site Manager*
Second Signature*
SAF-171 · record IDs look like REW-2026-000 · Links Observations, Hazard reports
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The form is the easy part. Keeping it current, routing it to the right owner and holding the evidence together is the work that actually slips.
Holds the recognition and reward record library against your registers, routes each record to its owner, and keeps the link back to the hazard report or observation it recognises.
Pulls stories marked for training or briefing use into the next induction or toolbox talk, so a good catch keeps teaching after the recognition itself has faded.
Flags when 'Shared With The Wider Site' is consistently No and surfaces recognised stories into the site's regular briefing cadence instead.

Coordinates the crew, rolls completion and exceptions into one view, and holds every write for your approval before it touches a record.
This template lives in KnowSafe — safety and compliance. Incidents, hazards, permits, inspections and the critical controls behind them.
Meet KnowSafe→Glossary
Recognition and Reward Record definitions and key terms
- Good catch
- An instance where a worker notices a hazard or unsafe condition and either fixes it or reports it before it causes harm, treated in behavioural safety as evidence the reporting culture is working.
- Stop-work call
- A decision, by any worker regardless of seniority, to halt a task believed to be unsafe; recognising this behaviour, rather than only permitting it in policy, is what makes stop-work authority real in practice.
- Positive reinforcement (safety culture)
- The deliberate practice of acknowledging desired safety behaviour promptly and specifically, on the evidence that recognition strengthens a behaviour more reliably than punishment suppresses its opposite.
- Injury-free milestone reward
- A once-common practice of rewarding a site or team for a period without a reportable injury, now widely discouraged because it creates a direct incentive to under-report incidents that would break the streak.
- Leading indicator
- A safety measure, such as recognitions given or hazards reported, that tracks activity believed to prevent harm, as distinct from a lagging indicator like injury rate which only shows harm that has already occurred.
FAQ
Frequently asked questions about recognition and reward record
What is the recognition and reward record template based on?+
It is built against ISO 45001 cl.5.4. ISO 45001 is the international standard for occupational health and safety management systems, and it is the backbone of most of the KnowSafe library.
What sections does the recognition and reward record contain?+
There are four sections: Header, What happened, Related records, and Recognition given. Together they hold 28 fields, 22 of which are required.
How often is a recognition and reward record raised?+
A new record is raised at the moment the event happens, rather than reconstructed afterwards. Each one is given an ID in the form REW-2026-000, so it can be traced and referenced from other records.
Which programme does the recognition and reward record belong to?+
It is part of Safety Culture and Engagement, a measured culture position with interventions matched to the maturity level a site actually has.
How is a recognition and reward record scored?+
Scoring is recognitions given, and high is good. The score exists to make the form tell you something, not to produce a percentage for its own sake.
Can the recognition and reward record template be changed?+
Yes. Every field, option, score and conditional rule is editable, and the links to other templates come with it. Most teams install it as it is, run it for a cycle, then adjust.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Safety Culture and Engagement
Improvement Suggestion Record
Captures an improvement idea from anybody, with what it would change and who could own it
Safety Observation
A short record of how a task was actually done, noting both safe practice and risk
Behaviour Based Observation
Looks at a specific set of behaviours agreed with the workforce, such as line of fire, body position and tool use
Leadership Safety Walk
A senior leader spends time in the workplace talking with workers about how the work really goes
Safety Coaching Record
Records a coaching conversation after an at risk practice was seen
Critical Task Observation
Watches a high risk task from start to finish against its procedure
More in Behavioural Safety
Safety Climate Survey
Measures how people actually experience safety here, covering trust, reporting, pressure and whether stopping work feels possible
Felt Leadership Tour Record
Records a senior manager spending time on the floor talking about safety, and what they heard
Safety Conversation Record
Records a short two way conversation about how a job is going and what makes it harder to do safely
Safety Culture Maturity Assessment
Places the organisation on a maturity scale from reactive through to generative, with evidence for the rating

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 45001:2018 cl.5.4 — Consultation and participation of workers
- ISO 45001:2018 cl.5.1 — Leadership and commitment
- ISO 45001:2018 cl.7.4 — Communication
- Health and Safety at Work etc. Act 1974, s.2(6) (UK)
- OSHA Voluntary Protection Programs (VPP) criteria (US)
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.