What this is
What is an observation trend review?
What is an observation trend review?
It is a periodic roll-up of individual safety observation records, run to show what the site's observation programme is actually surfacing over weeks or months rather than one shift at a time. It aggregates volume, coverage, at-risk themes and cross-references them against incident cause codes and open risk assessments, then decides whether a programme action is warranted.
How is this different from a single Safety Observation record?
A Safety Observation (SAF-041) captures one moment on one task. This review does not re-observe anything; it works entirely from the observations already logged, looking for the pattern across dozens or hundreds of them that no single record can show on its own.
Why does the review score 'systemic cause suspected' rather than just counting at-risk behaviours?
A raw count of at-risk behaviours tells you volume, not cause. Flagging whether a theme looks systemic — the same barrier recurring across different people and tasks — is what turns the review into something CAPA can act on, rather than a tally that gets filed and forgotten.
Scope
When is an observation trend review required?
This review is one step in the Safety Culture and Engagement programme. Using it to record a single observation, a leadership walk, or a committee's own governance produces data that does not belong in a trend view and makes the real trend harder to see.
Use this template when
- A reporting period (monthly or quarterly) has closed and observation data needs rolling up
- A trigger event — a spike in incidents, a near miss cluster — calls for an off-cycle look at observation themes
- The safety committee needs a data-backed input for its own meeting agenda
- A CAPA or risk assessment review needs evidence that a theme is recurring, not isolated
- Management review needs a summarised culture and behaviour position rather than raw observation counts
Do not use it for
- Safety Observation, which a short record of how a task was actually done, noting both safe practice and risk.
- Behaviour Based Observation, which looks at a specific set of behaviours agreed with the workforce, such as line of fire, body position and tool use.
- Leadership Safety Walk, which a senior leader spends time in the workplace talking with workers about how the work really goes.
- Committee Effectiveness Review, which reviews whether the committee itself is improving safety, not what the observation programme is finding.
- Anything outside KnowSafe, which belongs in the workspace that owns that process
Compliance mapping
Which ISO 45001 cl.9.1 requirements does this satisfy?
ISO 45001 clause 9.1 requires monitoring, measurement, analysis and evaluation of OH&S performance, but it does not prescribe an observation trend review by name. The clause map below shows which part of that requirement each section is standing in for.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 45001 cl.9.1.1 | Determine what needs to be monitored and measured, and evaluate OH&S performance | Volume and coverage |
| ISO 45001 cl.9.1.1 | Ensure monitoring and measurement equipment and methods are calibrated and suitable, applied here to observer reliability | Volume and coverage |
| ISO 45001 cl.9.1.1 | Analyse and evaluate OH&S performance data and determine appropriate indicators | Findings by theme |
| ISO 45001 cl.9.1.2 | Evaluate compliance and take action where trends indicate a systemic issue | Cross reference |
| ISO 45001 cl.10.2 | Investigate and determine causes where nonconformity or an adverse trend is identified | Cross reference |
| ISO 45001 cl.10.3 | Determine and implement action for continual improvement based on analysis results | Outcome |
| ISO 45001 cl.9.3 | Inputs for management review include results of participation and consultation, and monitoring results | Outcome |
What it does not cover
- Observation Quality Concern, which left as No against a completion percentage sitting at 100 with no theme variation across the period.
- Systemic Cause Suspected, which answered No despite the same Most Common Barrier appearing against multiple Behaviour Category entries.
- Themes Match Incident Causes, which answered Yes with no Cause Code entered against it.
- Programme Action Required, which marked No while Areas Not Covered lists a location with a known open risk assessment.
- Risk Assessment Review Needed, which marked Yes with no linked Risk Assessment record entered.
Global
Observation Trend Review requirements by country
Observation programmes and trend analysis are a management-system practice rather than a directly legislated activity, so the weight this review carries shifts with how each jurisdiction treats systemic monitoring evidence.
ISO 45001, clause 9.1 (monitoring, measurement, analysis and evaluation)
Certification bodies expect documented evidence that performance data is analysed for trends, not just collected — an observation programme with no periodic review is a common audit finding on its own.
This review is the artefact an auditor looks for when checking that clause 9.1 analysis actually happens, rather than being asserted in the manual.
OSHA General Duty Clause, 29 U.S.C. 654(a)(1)
OSHA does not mandate observation trend reviews, but a documented pattern of at-risk behaviour that was identified and not acted on strengthens a General Duty Clause citation after an incident.
A completed review showing a theme was flagged, with no linked CAPA, is discoverable evidence that the employer knew and did not act.
Health and Safety at Work etc. Act 1974, s.2(1) and Management of Health and Safety at Work Regulations 1999, reg.5
Regulation 5 requires arrangements for the effective planning, organisation, control, monitoring and review of preventive measures — monitoring alone does not satisfy it without review.
This template is the review half of that pairing; observation logging without a periodic trend review leaves regulation 5 only partly answered.
How to complete it
How to complete an observation trend review, step by step
The fields are quick to fill in from existing observation data. The judgement is in deciding what the numbers are actually telling you.
A period with few at-risk findings and a high completion percentage can mean either a genuinely well-run area or observers who have stopped looking hard because it is socially easier. Observation Quality Concern exists to force that distinction rather than let a clean-looking dashboard pass unquestioned.
The same at-risk behaviour showing up five times across five unrelated tasks and areas is systemic; the same behaviour from the same three people on the same task is a coaching issue. Systemic Cause Suspected has to be answered against that distinction, not against the raw count of At Risk entries.
Themes Match Incident Causes answered Yes is the strongest single signal this review produces, but only if the Cause Code entered actually corresponds to a cause investigated with the same rigour as the observation theme — a loose match on category name alone overstates the case.
Areas Not Covered is a free-text field, not scored, which makes it easy to skip. An area consistently absent from observation coverage is itself a finding — a clean set of themes from the areas that were covered says nothing about the one that was not.
What auditors find
Most common observation trend review findings
The findings this review surfaces recur across sites running an observation programme for more than a couple of cycles. Six of the most common are below.
| Finding | Clause | What fixes it |
|---|---|---|
| Completion percentage near 100 with no observation quality concern raised | ISO 45001 cl.9.1.1 | Require a brief justification whenever completion exceeds a set threshold with zero at-risk findings, rather than accepting the number alone. |
| Same behaviour category recurring across periods with systemic cause marked No each time | ISO 45001 cl.10.2 | Flag a behaviour category automatically once it appears in three consecutive review periods, and require systemic cause to be re-examined rather than defaulted. |
| Themes match incident causes marked Yes with no cause code linked | ISO 45001 cl.9.1.2 | Make the Cause Code field mandatory whenever Themes Match Incident Causes is answered Yes or Partly. |
| Areas not covered left blank or vague when coverage was known to be partial | ISO 45001 cl.9.1.1 | Require a specific area or shift reference in Areas Not Covered whenever Areas Covered falls short of the site's active location count. |
| Programme action required marked Yes with no CAPA reference entered before the review closes | ISO 45001 cl.10.3 | Block the review from reaching Complete status while Programme Action Required is Yes and CAPA ID is blank. |
| Risk assessment review needed marked Yes with the linked risk assessment never actually revisited | ISO 45001 cl.10.2 | Route a Yes answer here to notify the risk assessment owner directly, rather than leaving it as a passive field on this record. |
Case in point
Case in point: the theme that matched an incident nobody had reopened
A quarterly review logged 'unsafe posture' as the top behaviour category for the third period running, with systemic cause marked No each time because no single incident had been directly attributed to it. During the cross-reference step, the reviewer checked the cause code register and found a manual handling injury from four months earlier coded to exactly that root cause — a code nobody had thought to compare against the observation theme until this review forced the comparison.
Nothing had been hidden; the incident record and the observation records simply lived in different places and nobody had been asked to hold them side by side. The fix was not a new inspection or a new form — it was making the Themes Match Incident Causes field mandatory to answer with evidence, so the comparison happens by default rather than by chance.
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.
5 sections
- Reference
- SAF-047
- Archetype
- Review
- Record ID
- OTR-2026-000
- Scoring
- Trend direction
- Direction
- High is good
- Singleton
- No
- Basis
- ISO 45001 cl.9.1
- Links
- Links Observations; feeds CAPA
- Tags
- Observation, Analysis
- Sections
- 5
- Fields
- 35
- Follow up fields
- 3
- Repeating sections
- 1
- Links out
- 4
Header
8 fieldsReview ID*
Auto sequence. Format OTR-2026-0000.
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
Period Covered From*
Period Covered To*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Reviewed By*
Committee Involved
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Volume and coverage
7 fieldsObservations Completed*
Target For Period*
Completion Percent*
Areas Covered*
Areas Not Covered
Gaps in coverage matter as much as the scores.
Observers Active*
Observation Quality Concern*
Scores near 100 percent usually mean observers are not looking hard enough.
- No2 pts
- Yes, scores implausibly high0 pts
Findings by theme
Repeats5 fieldsBehaviour Category*
- Bypassing a control0 pts
- Not using PPE0 pts
- Line of fire0 pts
- Shortcut under time pressure0 pts
- Improvised tool or method0 pts
- Unsafe posture1 pt
At Risk Count*
Trend Direction*
- Improving3 pts
- Stable2 pts
- Worsening0 pts
Most Common Barrier
What repeatedly makes the safe way harder than the unsafe way.
Systemic Cause Suspected*
- No2 pts
- Yes0 pts
Cross reference
6 fieldsThemes Match Incident Causes*
Where observation themes and cause codes agree, you have found something real.
- Yes3 pts
- Partly2 pts
- No1 pt
Cause Code
Cause Code ID
Links to FDN-010 Cause Code
Risk Assessment Review Needed*
Risk Assessment
Risk ID
Format RSK-2026-00000.
Links to FDN-012 Risk ID
Outcome
9 fieldsTop Three Themes*
Programme Action Required*
Raise the action record, then enter its reference here.
- Yes0 pts
- No2 pts
- N/Aexcluded from denominator
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Next Review Due*
Reported To Management Review
Reviewed By*
Signature*
SAF-047 · record IDs look like OTR-2026-000 · Links Observations; feeds CAPA
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
Aggregating the numbers is mechanical. Deciding whether a clean result is real, and making sure a flagged theme actually reaches CAPA, is the part that depends on someone following through.
Pulls the period's observation records automatically into this review, flags a completion rate that looks implausibly clean, and keeps the CAPA link live once a programme action is raised.
Cross-checks a recurring behaviour theme against training records for the areas involved, surfacing whether the pattern tracks to a skills gap rather than a hazard the observation programme alone can fix.
Tracks whether a theme flagged as matching an incident cause actually gets a risk assessment reopened, closing the loop this review is meant to start rather than leaving it as a one-off finding.
Coordinates the crew across these workspaces, 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
Observation Trend Review definitions and key terms
- Trend direction
- Whether a specific behaviour theme is improving, holding stable, or worsening across the reviewed period, scored per theme rather than for the site as a whole.
- Systemic cause
- A root cause that recurs across different people, tasks or areas, distinguishing a design or process failure from an individual lapse.
- Coverage
- The proportion of areas, shifts or tasks that observations were actually collected against during the period, as distinct from how many observations were completed overall.
- Cause code
- The standardised root-cause classification used across incident investigations, referenced here to cross-check observation themes against confirmed incident causes.
- Observation quality concern
- A flag raised when observation results look implausibly favourable, indicating the observations themselves may not be rigorous rather than that conditions have improved.
FAQ
Frequently asked questions about observation trend review
Who normally completes an observation trend review?+
The safety lead, working with the safety committee. It is built as a discussion document as much as a record — the committee's involvement is what turns raw numbers into an agreed set of themes.
Does this review replace individual observation records?+
No. It depends entirely on observations already logged through templates like Safety Observation and Behaviour Based Observation. Without a reasonable volume of those feeding in, this review has nothing to aggregate.
What happens if a theme looks systemic?+
Systemic Cause Suspected marked Yes should prompt a look at whether a risk assessment needs revisiting and whether a CAPA is warranted, rather than being logged and carried to the next period unchanged.
Why is there a field just for coverage gaps?+
A theme list built entirely from the areas that were easiest to observe is not a site-wide trend, it is a partial one. Recording what was not covered keeps that limitation visible rather than implied.
How does this feed CAPA?+
Programme Action Required, when answered Yes, is meant to result in a CAPA record referenced back on this template, so the action raised from a trend has a traceable owner and due date rather than sitting only as a note.
Can the review be run off-cycle?+
Yes. Beyond the monthly or quarterly interval, a trigger event such as an incident spike or a run of near misses is a valid reason to raise one early, using the same fields.
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 Observations
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
Peer Observation
Workers observe each other and give feedback directly, with no supervisor involved
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 — clause 9.1, Monitoring, measurement, analysis and performance evaluation
- ISO 45001:2018 — clause 10.2, Incident, nonconformity and corrective action
- ISO 45001:2018 — clause 10.3, Continual improvement
- Health and Safety at Work etc. Act 1974, s.2(1)
- Management of Health and Safety at Work Regulations 1999, regulation 5
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.