What this is
What is an annual safety objectives record?
What is an annual safety objectives record?
It is the yearly document that sets the site's safety goals with a defined measure, baseline, target, owner and target date for each one. Built against ISO 45001 cl.6.2, it sits inside the Safety Programme Management programme and is expected to mix leading measures — things people can influence directly — with lagging ones like injury rate.
What's the difference between a leading and a lagging safety objective?
A lagging objective targets an outcome that has already happened by the time it's measured, such as reducing lost-time injuries. A leading objective targets something predictive and controllable now — inspection closure rate, near-miss reporting volume, training completion. ISO 45001 doesn't mandate the split, but a set of objectives built only on lagging measures gives the site nothing to act on before the harm occurs.
How does an objectives record connect to the risk register?
Each objective in this template can link to a specific risk assessment via Risk Assessment and Risk ID. The Linked To Risk field then asks directly whether the objective is tied to a real, named risk — objectives that aren't tend to be the ones abandoned mid-year once attention moves elsewhere.
Scope
When is an annual safety objectives required?
This plan 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 site is setting its safety goals for the coming year and needs owners, measures and target dates against each one
- A safety management plan already exists and this is the step that turns its intent into specific, measurable targets
- A new record is needed; each one gets its own ID in the form OBJ-2026-000
- You are running the Safety Programme Management programme and this is the annual target-setting step inside it
- A linked record needs this one to exist — the objectives feed the Management Review Record and reference the Safety Management Plan and risk register
Do not use it for
- Safety Management Plan, which sets out how safety is managed across the site as a whole — the structure the objectives sit inside, not the targets themselves.
- Safety Program Review, which reviews how a specific programme, such as PPE or working at height, is performing against its own plan — narrower than a site-wide objectives set.
- Site Safety Rules, which is the short list of rules everyone on site must follow — a worker-facing document, not a management target.
- Management Review Record, which records the review meeting itself; objectives feed into it but the meeting record is a separate document.
- Anything outside KnowSafe, which belongs in the workspace that owns that process.
Compliance mapping
Which ISO 45001 cl.6.2 requirements does this satisfy?
The template is built against ISO 45001 cl.6.2, with the Balance check section folding in the worker-participation obligations of clause 5.4 and the management review feed of clause 9.3.
| Clause | Requirement | Where it lands |
|---|---|---|
| 6.2.1 | Establish safety objectives at relevant functions and levels, consistent with the policy | Header |
| 6.2.1 | Objectives should be measurable where practicable, monitored and communicated | Objectives |
| 6.2.2 | Determine what will be done, resources required, who is responsible and target dates | Objectives |
| 6.1.1 | Integrate actions to address risks and opportunities into objective-setting | Objectives |
| 5.4 | Consult workers in setting and reviewing objectives | Balance check |
| 9.1 | Determine the leading and lagging measures used to evaluate performance | Balance check |
| 9.3 | Feed objective progress and outcomes into management review | Balance check |
What it does not cover
- Linked To Risk, which scores No when an objective sounds specific but doesn't tie back to any named entry in the risk register.
- Resource Committed, which stays Partly when a target date and owner exist but no budget or headcount was ever actually assigned to hit it.
- Balance Acceptable, which is marked Too lagging heavy when every objective in the set targets an outcome — injury rate, incident count — rather than a controllable input.
- Committee Consulted, which scores No when the objectives were drafted centrally and circulated for information rather than discussed with the safety committee before being set.
- Reported To Management Review, which is left No when the year closes and progress against the objectives was never actually put in front of senior management.
Global
Annual Safety Objectives requirements by country
ISO 45001 objective-setting is voluntary in form everywhere, but the pressure to set defensible, balanced objectives comes from different directions depending on where the site sits.
OSHA Recordkeeping, 29 CFR 1904, alongside voluntary ISO 45001 adoption
No statutory requirement to set annual safety objectives, but OSHA recordable data is the lagging measure most US objectives sets default to because it's already being collected.
US sites building this record should treat the Balance check section as the corrective — the data that's easiest to pull, OSHA recordables, is exactly the lagging half of the set, not the whole of it.
Framework Directive 89/391/EEC, Art. 6(3), plus national transposition
Employers must plan prevention as a coherent system, which regulators and auditors increasingly read as requiring objectives that address causes, not just outcomes.
An EU site with an all-lagging objectives set is more exposed to a finding under national OHS inspection regimes that specifically test for preventive planning.
ISO 45001:2018 cl.6.2 and cl.9.3
Certification bodies test whether objectives were actually reviewed in management review, not just whether they were set.
Reported To Management Review being left No is the single field in this template most likely to produce a certification nonconformity on its own.
How to complete it
How to complete an annual safety objectives, step by step
Most fields here are short entries, but a handful carry a judgement call that decides whether the objectives set is defensible rather than decorative.
Marking Indicator Type as Leading is a self-declaration with nothing in the form to check it. 'Reduce incidents by 10%' tagged Leading doesn't become predictive by relabelling — the judgement call is whether the Measure field actually describes something controllable now, not an outcome restated as an input.
Both fields are binary or Pass/Partial/Fail with no defined evidence requirement. Circulating a draft for comment and running an actual discussion where objectives changed as a result are very different levels of consultation that the scoring alone doesn't distinguish.
The field is a raw number with no formula tying it to Baseline and Target elsewhere in the same row. A defensible score is calculated from the two; an indefensible one is a percentage someone felt was about right going into the review.
Status covers Deferred, Open and Overdue as valid end-states scored at zero, but nothing in the template forces a deferred objective into next year's record. The judgement call sits with whoever closes this year's set: does it show what didn't get done and why, or does the objective simply not reappear.
What auditors find
Most common annual safety objectives findings
The recurring gaps sit in objectives that are internally consistent but disconnected from what the balance check and the risk register are supposed to enforce.
| Finding | Clause | What fixes it |
|---|---|---|
| Every objective in the set is tagged Lagging, so Balance Acceptable is scored Too lagging heavy despite each individual objective looking complete. | ISO 45001 cl.9.1 | Require at least one leading-tagged objective per major risk area before the set can be submitted for approval. |
| Linked To Risk is answered Yes without a corresponding Risk Assessment or Risk ID entered against the objective. | ISO 45001 cl.6.1.1 | Make Risk Assessment a required field whenever Linked To Risk is Yes, rather than leaving the link optional. |
| Resource Committed is Yes with no budget line or headcount change anywhere else in the site's records for the period. | ISO 45001 cl.6.2.2 | Cross-check resourcing claims against the site's actual budget cycle before accepting a Yes. |
| Committee Consulted is Yes based on the objectives being emailed to the committee, not discussed at a meeting. | ISO 45001 cl.5.4 | Require a meeting date or minute reference before scoring consultation fields above Partial. |
| Progress Percent is updated once, at year-end, rather than tracked through the year against the stated Target Date. | ISO 45001 cl.9.1 | Set a reporting cadence for Progress Percent tied to the Target Date, not a single end-of-year entry. |
| Reported To Management Review is left No with no follow-up action raised, so the gap closes itself by omission next cycle. | ISO 45001 cl.9.3 | Treat a No here as a required agenda item for the next Management Review Record rather than a closed field. |
Case in point
Case in point: the objectives set that hit every target and still missed the point.
A site closed its year with four objectives, all Complete, all Progress Percent at or above target. All four were lagging: reduce lost-time injuries, reduce recordable incidents, reduce near-miss under-reporting complaints, reduce first-aid cases. Balance Acceptable was still scored Too lagging heavy, and the safety committee had raised that in the first quarter without the set being revised.
By year-end, the numbers had improved — largely because activity on site had dropped due to a slow order book, not because of anything the objectives drove. Nothing in the set would have distinguished 'we managed this' from 'less happened this year,' because nothing leading was ever being tracked to compare against.
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.
3 sections
- Reference
- SAF-122
- Archetype
- Plan
- Record ID
- OBJ-2026-000
- Scoring
- Progress percent
- Direction
- High is good
- Singleton
- No
- Basis
- ISO 45001 cl.6.2
- Links
- Links Site; feeds Management Review
- Tags
- Programme, Governance
- Sections
- 3
- Fields
- 36
- Follow up fields
- 0
- Repeating sections
- 1
- Links out
- 2
Header
10 fieldsObjectives ID*
Auto sequence. Format OBJ-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
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Year*
Set By*
Approved By*
Site 2*
Site ID 2*
Format SITE-000.
Links to FDN-001 Site ID
Mix Your Measures
Objectives built only on injury rate encourage under reporting. Pair every lagging target with leading measures people can actually influence.
Objectives
Repeats14 fieldsObjective*
Indicator Type*
- Leading3 pts
- Lagging2 pts
Measure*
Baseline*
Target*
Owner*
Target Date*
Resource Committed*
- Yes3 pts
- Partly1 pt
- No0 pts
Linked To Risk*
Objectives that do not connect to a real risk tend to be abandoned.
- Yes3 pts
- Indirectly1 pt
- No0 pts
Risk Assessment
Risk ID
Format RSK-2026-00000.
Links to FDN-012 Risk ID
Progress Percent
Status
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Commentary
Balance check
12 fieldsLeading Objectives*
Lagging Objectives*
Balance Acceptable*
- Yes3 pts
- Too lagging heavy1 pt
- Too leading heavy1 pt
Worker Input Sought*
- Pass2 pts
- Partial1 pt
- Fail0 pts
- N/Aexcluded from denominator
Committee Consulted*
- Yes3 pts
- No0 pts
Communicated To Workforce*
- Pass2 pts
- Partial1 pt
- Fail0 pts
- N/Aexcluded from denominator
Reported To Management Review*
Next Review Due*
Set By*
Signature*
Site Manager*
Second Signature*
SAF-122 · record IDs look like OBJ-2026-000 · Links Site; feeds Management Review
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 the objectives balanced, tied to real risk and actually discussed at management review is the work that slips.
Holds the objectives set against the site's risk register and safety management plan, and flags a set that's drifted all-lagging before Balance Acceptable gets scored.
Tracks whether objectives were actually reported to management review as required, so a Reported To Management Review left No surfaces before an audit finds it.
Keeps resourcing commitments made against each objective visible alongside the site's actual operating budget and headcount plan.
Coordinates the crew across these workspaces, rolls objective progress 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
Annual Safety Objectives definitions and key terms
- Leading indicator
- A measure that predicts safety performance and that people can influence directly — inspection completion, training currency, near-miss reporting rate.
- Lagging indicator
- A measure of harm or loss that has already occurred — injury rate, lost time, recordable incidents — useful for trend, not prevention.
- Balance check
- The section of this template that forces an explicit judgement on whether a site's objectives set mixes leading and lagging measures acceptably, rather than leaving the mix to chance.
- Objective progress percent
- A live, per-objective completion score used instead of a one-time pass or fail, letting the record be reviewed mid-year rather than only at year-end.
- Worker participation (in objective-setting)
- The requirement under ISO 45001 cl.5.4 that objectives be set with input from the people they affect, not handed down from management alone.
FAQ
Frequently asked questions about annual safety objectives
How many objectives should a site set in a year?+
The template doesn't cap the number — Objectives is a repeating section — but more objectives than the site can resource tends to produce a set where Resource Committed is honestly Partly or No across the board. A shorter list that's fully resourced outperforms a long one that isn't.
Does every objective need to link to a named risk?+
Not strictly — Risk Assessment and Risk ID are optional fields — but Linked To Risk is a required, scored field precisely because objectives disconnected from a real risk are the ones this template's help text flags as most likely to be abandoned.
Who has to sign off the objectives set?+
Set By and Site Manager both carry a signature field at the end of the record, alongside Approved By in the header. The template distinguishes who drafted the set from who approved it and from who ultimately signs as accountable.
What if the safety committee disagrees with a target management wants to set?+
The template doesn't resolve that for you — Committee Consulted only records that consultation happened, not its outcome. In practice, a disagreement that isn't reflected anywhere in Commentary or a revised Target tends to resurface at the next management review.
Can objectives be changed mid-year?+
Yes, and Status supports it — Deferred and Overdue are valid states, not automatic failures. What the template doesn't do automatically is carry a changed objective's history forward, so a revision should be captured in Commentary at the point it happens.
Is Progress Percent the same as the site's safety performance?+
No. It scores how the objectives set is tracking against its own targets, not how safe the site is overall — a well-managed set of weak objectives can show near-complete progress and still tell you very little.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Safety Programme Management
Regulatory Inspection Record
Records a visit by a regulator, including what was inspected, what was said and any orders issued
Management Review Record
Records the periodic review of the management system by senior leadership, covering performance, risks, resources and improvement
Interested Party Register
Holds the parties whose needs shape the management system, from regulators and customers to neighbours and the workforce
Safety Management Plan
Sets out how safety is managed across the site, covering roles, processes, resources and how performance is measured
Safety Program Review
Reviews how a specific programme, such as PPE or working at height, is performing
Site Safety Rules
The short list of rules everyone on site must follow, including visitors and contractors
More in Programs
Safety Management Plan
Sets out how safety is managed across the site, covering roles, processes, resources and how performance is measured
Safety Program Review
Reviews how a specific programme, such as PPE or working at height, is performing
Site Safety Rules
The short list of rules everyone on site must follow, including visitors and contractors
PPE Program Plan
Sets out what protective equipment is required for which task, how it is selected, issued, maintained and replaced
Hearing Protection Program Plan
Sets out how noise exposure is controlled, including monitoring, protection, training and hearing tests
Contractor Safety Plan
Sets out the safety requirements contractors must meet on your site, and how they are checked
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.6.2 Safety objectives and planning to achieve them
- ISO 45001:2018 — cl.9.3 Management review
- EU Framework Directive 89/391/EEC, Art. 6(3)
- OSHA Recordkeeping, 29 CFR 1904
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.