SHARE Knowledge Hub

Process Safety Objectives, Targets and Indicators

A process-safety objective describes the major-accident outcome to prevent and the barrier standard to sustain. A target sets a defined threshold and response; an indicator supplies evidence from the field. Counts of completed inspections or low injury rates are weak assurance unless they reveal whether containment, shutdown, relief and emergency barriers are available and effective.

Updated 2026-10-19UK focus

Understanding Process Safety Objectives, Targets and Indicators

A process-safety objective describes the major-accident outcome to prevent and the barrier standard to sustain. A target sets a defined threshold and response; an indicator supplies evidence from the field. Counts of completed inspections or low injury rates are weak assurance unless they reveal whether containment, shutdown, relief and emergency barriers are available and effective.

Why this matters at work

A high-high trip that acts correctly can show a genuine demand caused by an upstream control weakness and successful performance of the final protection. Count the demand and investigate its cause; do not automatically count it as failure of the trip. Conversely, failure to act during a functional test can reveal a failed protection function without any release. Define the chosen risk-control outcome, demand, precursor, failure, operating mode and attribution before classifying the indicator as leading or lagging.

Keep the three questions separate: was the work done on time, did the function initially meet its requirement, and was each failure safely corrected and verified? Later repair does not convert an as-found failure into an original pass. Report each critical overdue or failed function with its scenario, current exposure, restriction, owner and competent restoration evidence. Do not call an overdue item a demonstrated failure merely because it is untested; call its condition unproven.

How organisations manage this in practice

Establish a sponsor, indicator steward, technical reviewers and site owners. Control definitions, data sources, calculation, tolerances and changes. Review whether measures alter priorities or operating conditions. A dashboard that is produced on time but never triggers investigation, resources or restriction is not functioning as a risk control.

Map measures to each scenario and look for unmeasured barriers or excessive dependence on one layer. Preserve distinctions between preventive and mitigative functions in aggregation. Review whether investment and management attention follow the same balance, particularly when mitigation performance is easier to count than prevention quality.

Use the monthly cycle to test each role: the steward explains data quality, the owner interprets risk and the action owner demonstrates correction. Escalate when one person is asked to mark their own performance without independent review or lacks authority to change the condition.

Measure both prevention of loss of control and mitigation of consequences. Containment, process control and shutdown indicators should sit alongside detection, isolation, fire protection, drainage and emergency response where those barriers are claimed. A strong emergency metric cannot compensate for deteriorating prevention.

SHAREsimulate

How can I practise this topic in 3D?

The dashboard counts injuries but misses failing barriers
3D workplace practiceSHAREsim

The dashboard counts injuries but misses failing barriers

All related inspection points 1 across 1 location
Crown Fuels terminal 1 inspection point

Practice in the SHAREhub environment. Browser practice is separate from workplace competence and formal learning records.

What are process safety objectives, targets and indicators?

They are the measurable aims and evidence used to track whether major accident controls are being maintained.

Objectives define what the organisation is trying to improve or maintain, such as reducing loss-of-containment events, strengthening critical-control verification or eliminating overdue safety-critical maintenance. Targets define the expected performance level. Indicators show whether the system is moving towards or away from control.

The best indicators are linked to scenarios and barriers. A training completion percentage is weak if it does not prove competence in a safety-critical task. A better indicator might be the percentage of sampled isolations where the isolation plan, lock/tag, zero-energy verification and handback were all correct.

TermMeaningProcess safety example
ObjectiveA desired improvement or control state.Improve overfill-prevention barrier reliability.
TargetA specific expected performance level.100 percent proof tests completed by due date.
Leading indicatorA measure of control condition before harm occurs.Safety-critical maintenance overdue rate.
Lagging indicatorA measure of events, failures or harm after something has occurred.Loss-of-containment events and high-potential near misses.
Trigger levelA threshold that prompts action.Any overdue safety-critical test triggers immediate asset-specific escalation and a hold/release decision against the credited barrier standard. Track non-critical backlog separately.
Data ownerPerson accountable for quality and response.Maintenance manager owns proof-test indicator.
Action ruleWhat happens when data shows weakness.Stop, restrict, escalate, investigate or resource.

Start with the credible scenario, such as overfill of a fuel tank, then identify the controls relied on to prevent or mitigate it. Choose a leading measure of the control system, such as proof tests completed to standard, and a lagging measure of failure, such as high-level demands or loss of containment. Give each measure a definition, owner, source, threshold and action. A green percentage can hide one overdue test on the only independent trip; the decision must be barrier-specific.

Source: HSE developing process safety indicators HSG254

Source: HSE COMAH 2015 guidance

A weak indicator can hide a real harm path: an overfill trip is bypassed, the dashboard averages it with healthy equipment, transfer continues, and fuel can escape into a vapour cloud that ignites or harms people and the environment. The stop trigger belongs to the individual critical barrier, not a fleet-wide green percentage. Source: HSE developing process safety indicators HSG254

How can the hierarchy of controls link process-safety targets to stronger major accident controls?

Eliminate, Reduce including substitution, Isolate, Control, personal protective equipment (PPE) and Discipline (ERICPD) is a prompt for decisions. HSE’s five-level hierarchy prioritises elimination, substitution, engineering controls, administrative controls and PPE. They are related frameworks, not identical laws; apply them to the actual task and check the resulting control.

Eliminate the overfill scenario where a redesigned transfer or reduced inventory can remove it. Record that decision as an objective and verify the field configuration; an indicator cannot compensate for an avoidable hazard.

Substitute or reduce fuel inventory, transfer rate or operating envelope where technically justified. Track the actual limit and changed assumptions, not merely a generic “risk reduction” target.

Isolate and engineer with independent high-high shutdown, containment, relief and alarms. Measure proof-test quality, bypass hours, defect age and demand response against a performance standard. An impaired critical barrier triggers a hold even if the aggregate dashboard is green.

Control, PPE and Discipline: procedures, competence, sampling and management review sustain stronger controls. PPE addresses residual task exposure, not tank overfill. ERICPD is a planning prompt; HSE’s five-level hierarchy orders elimination, substitution, engineering, administration and PPE, and neither is a substitute for the scenario-specific barrier test.

Source: HSE hierarchy of controls

Source: HSE developing process safety indicators HSG254

How should indicators be designed from major accident scenarios?

Start with the scenario, identify the barrier, then choose measures that show whether the barrier is healthy.

A common weakness is starting with available data instead of starting with risk. The better route is: major accident scenario -> barrier function -> performance standard -> evidence source -> leading indicator -> lagging indicator -> trigger level -> management action.

This method prevents dashboards from becoming collections of easy numbers. The organisation may have excellent completion of generic inspections while missing the fact that critical alarms are overridden or that proof tests are overdue.

Design stepQuestionExample
ScenarioWhat high-consequence event are we trying to prevent?Tank overfill leading to vapour cloud explosion.
BarrierWhich control interrupts the event?Independent high-high level trip.
Performance standardWhat must the barrier do?Detect high level and stop transfer on demand.
Evidence sourceWhere does data come from?Proof-test record and bypass register.
Leading indicatorWhat shows health before failure?Proof tests due, completed and failed.
Lagging indicatorWhat shows barrier demand/failure?Overfill near miss or trip failure.
Trigger/actionWhat requires escalation?Any failed test or overdue red action.

What does a process safety dashboard look like in practice?

A worked dashboard shows how indicators become management questions rather than decorative numbers.

Crownway Fuels Ltd builds a dashboard for fuel storage and transfer risk. The top scenario is overfill leading to loss of containment, vapour cloud, fire, environmental harm or escalation. The dashboard combines leading indicators such as proof testing, alarm health, MOC backlog and operator competence with lagging indicators such as loss-of-containment events, high-potential near misses and emergency shutdown demands.

The dashboard is useful only because every red or amber measure has a named owner, trigger rule and action expectation. If an indicator is red but no one acts, the measure becomes false reassurance.

IndicatorTypeManagement action
Barrier overdue testsLeadingEscalate any overdue safety-critical barrier test, assess restriction of operation and verify recovery date.
Critical alarms bypassedLeading/weak signalReview bypass authorisation, temporary controls, expiry date and operator briefing.
MOC overdueLeadingHold start-up or operation where open actions affect safe limits, procedures, training or barriers.
Relief valve inspection statusLeadingCheck inspection/test due dates, blocked isolation controls, defect status and risk acceptance.
Containment eventsLagging/weak signalClassify actual and potential severity, investigate causes and update barrier actions.
Proof-test completionLeading — planned activityReport tests completed on time / tests due in the stated period. Record overdue, deferred and not-verified states separately by safety-critical function; a denominator must not hide a missing critical test.
Proof-test failures and protective-function demandsLagging/control outcome and learningReport failed tests, actual demands and response failures separately from completion. Identify the affected barrier/scenario, immediate restriction, technical owner and verified recovery before release.
Weak signalsMixed early-warning and realised control-failure evidenceTrend operator concerns, repeated permit findings and temporary repairs as warnings. Classify small leaks and failed functions as actual control outcomes too; do not relabel them as purely proactive activity.
Action qualityAssuranceSample whether actions remove system weakness, have evidence and are verified in the field.
Independent overfill trip proof tests overdueLeadingEscalate to site leader and restrict affected transfer if barrier unavailable.
Standing high-level alarmsLeading/weak signalReview alarm rationalisation, maintenance and operator response.
Safety-critical maintenance backlogLeadingRisk-rank and resource backlog; review deferral approvals.
MOC actions overdue before start-upLeadingHold start-up until a safe basis is demonstrated and competently accepted; any restricted alternative needs evidence, limits and expiry and cannot waive a duty.
Loss of containment eventsLaggingInvestigate, update barriers and share learning.
Emergency shutdown demandsLagging/learningReview initiating causes, barrier response and proof-test assumptions.

Operational example: decisions and evidence

Task material and setting: Crownway Fuels Ltd reviews fuel-storage overfill indicators for tank transfer operations.

People and prerequisites: Process-safety lead owns the scenario; instrument specialist owns trip performance; operations owns transfer and alarm response; senior manager owns resources and thresholds.

Before: Link each objective to tank limits, independent trip, alarm, transfer procedure, containment and emergency response; define data source and denominator.

During: Review overdue proof tests, bypass duration, high-level alarms, MOC backlog and near misses together; investigate any red barrier signal in the field.

Hold or stop: Pause the affected transfer if independent overfill protection is unproved or an alarm/limit discrepancy cannot be resolved, regardless of overall score.

Completion and hand back: Close defects with proof-test and field evidence, revise the threshold if it failed to reveal the problem, and record the management decision.

Evidence: Indicator specification, data extract, barrier standard, alarm/trip test, action owner, stop/release decision and trend review.

Source: HSE developing process safety indicators HSG254

Source: HSE COMAH 2015 guidance

Illustrative monthly numbers: 99 of 100 planned proof tests completed on time is a proactive completion measure. Report one overdue independent trip by asset and scenario, and report failed tests/demands separately as control outcomes. A small leak or failed protective function may already be lagging control-failure evidence while warning of a worse event. State coverage and data-quality limits; 99% completion cannot release the sole unproved credited barrier.

Where do process safety indicators fail?

Indicators fail when they measure easy activity, hide weak signals, lack triggers or are not linked to decisions.

A dashboard can look mature while saying very little. Counting audits, training or inspections does not prove safety-critical barriers are healthy. A site can be green on activity and red on risk if the indicators do not test the controls that prevent major accidents.

Another failure is poor data quality. If bypasses are not recorded, near misses are under-reported or actions are closed without verification, the dashboard becomes a confident lie.

Failure modeHow it developsWhat competent management does
Activity counted as controlNumber of inspections replaces evidence of barrier effectiveness.Measure quality and critical-control outcome.
Lagging-only dashboardSerious events are rare until multiple barriers fail.Use leading indicators linked to scenarios.
No trigger levelRed data creates no defined response.Set thresholds, owners and escalation rules.
No data ownerQuality and response are unclear.Assign accountable owners for each indicator.
Administrative close-outActions close in system but risk remains.Require evidence and effectiveness checks.
Injury rate substitutionPersonal safety data hides process risk.Separate personal and process safety indicators.
Cherry-picked reportingBad news is filtered before leadership review.Use independent assurance and worker voice.

What evidence should sit behind each indicator?

Each indicator should have a definition, data source, owner, trigger, action rule and quality check.

A process safety indicator without a definition is vulnerable to gaming and misunderstanding. People need to know exactly what is counted, what is excluded, where the data comes from, who verifies it and what action is required when the indicator changes.

Good evidence also shows data quality. If the indicator says 100 percent of checks are complete, assurance should sample whether the checks were meaningful and whether failed checks created actions.

Evidence itemWhat good looks likeWeakness to challenge
Indicator definitionClear scope, inclusion/exclusion rules and calculation.Different sites count the same item differently.
Data sourceReliable system, register, inspection or field evidence.Manual spreadsheet with no owner.
OwnerNamed person accountable for data quality and response.No one owns amber or red status.
Trigger thresholdsGreen/amber/red criteria and escalation rules.Colour chosen subjectively.
Action recordActions linked to risk, owner, date and verification.Actions closed without evidence.
Assurance sampleData periodically checked against field reality.Dashboard accepted at face value.
Review minutesLeaders challenge trend and resource decisions.Dashboard noted with no decision.

How should indicators support management review?

Indicators should help leaders decide what to stop, resource, investigate, escalate or improve.

Management review should not be a passive report-out. Leaders should ask what the indicators mean for the risk profile, which barriers are degrading, whether weak signals are repeating and whether actions are reducing risk. The review should compare leading and lagging data, because a lagging event may expose a leading indicator that was missing or ignored.

For high-hazard sites, indicators should be tied to risk appetite and tolerance. Certain barrier degradations should never sit quietly in amber for months.

Review questionWhy it mattersPossible action
Which barriers are trending worse?Identifies weakening control before incidents.Escalate, resource or restrict operation.
Which red actions are overdue?Tests accountability and risk acceptance.Senior intervention and temporary controls.
Which indicators may be misleading?Challenges false assurance and data gaming.Audit data quality and definitions.
What do weak signals suggest?Connects small events to major scenarios.Investigate themes and update risk register.
What has improved because of action?Tests effectiveness, not effort.Verify and standardise improvements.
Are objectives still risk-led?Changes in plant, people or inventory may alter priorities.Update objectives after risk profile change.

What do learners commonly misunderstand?

The common mistake is listing KPIs without explaining whether they are leading, lagging, risk-led or actionable.

A strong answer explains how a good indicator is selected from a credible scenario and barrier. It describes what the measure tells the organisation, what it does not tell the organisation and what action follows.

A weak answer says 'measure training, audits and accidents' without explaining barrier health, trigger thresholds, data quality or management response.

Learner questionStrong answer should includeWeak answer to avoid
What is a leading indicator?A measure of control health before harm occurs.A target that makes safety better.
What is a lagging indicator?A measure after an event, demand, failure or harm.Only injury rate.
Why use barrier indicators?They test controls that prevent major accidents.Because they are easy to count.
What is a bad KPI?One that counts activity without risk insight or action.Any KPI that is red.
How should a dashboard be reviewed?With triggers, owners, data quality and decisions.Present numbers to leaders.

How should the control be managed and reviewed?

For a GB workplace, HSE guidance supports identifying the actual risk, taking practical protective steps and reviewing whether they work. Name the decision owner, check the control during the real task and correct a failed arrangement. Apply the separate Northern Ireland duties and guidance where the work is in NI.

GB management guidance: HSE managing health and safety

What training and competence are needed?

Training should help people design risk-led indicators, interpret trends and act on weak signals.

Training should be role-based. General awareness creates a baseline, but supervisors, managers, advisers and senior leaders need different levels of decision-making, verification and escalation competence.

RoleWhat to demonstrateWho checksRecord and reassessment
Operators and supervisorsExplain the overfill scenario and red-barrier stop rule.Process-safety lead tests a live dashboard scenario.Briefing, decision and reassessment.
Instrument and maintenance specialistsValidate proof-test, bypass and defect measures.Technical authority samples records and field status.Test basis, result and repair closure.
Analysts and advisersDefine indicator, denominator, threshold and data quality.Independent reviewer traces a measure to its barrier.Specification and validation.
Senior leadersChallenge green averages against a single critical failure and fund action.Board reviews a red barrier scenario.Decision, resources and closure.

Source context: HSE developing process safety indicators HSG254

What do the acronyms and key terms mean?

Acronyms should be understood before they are used in assessments, briefings, audits or learning answers.

Acronyms can exclude newer readers if they are not explained. This section keeps the main terms available at the end of the page so the article stays readable while still supporting learners and audit users.

AcronymMeaningPlain-English use
COMAHControl of Major Accident HazardsMajor-accident regime with separate GB and Northern Ireland regulations; check site threshold.
PSMProcess Safety ManagementManagement of major accident hazard controls.
MOCManagement of ChangeControlled review before changes are made.
SCESafety Critical ElementA system, structure or component whose failure could contribute to a major accident.
KPIKey Performance IndicatorA measure used to track performance.

Which Crownway Fuels documents support this topic?

Open an editable document, read the preview, or find its place in the Crownway hierarchy. 8 resources relate to this page.

Fictional Crownway Fuels examples for English forecourts, with a separate illustrative bulk terminal. Check site applicability, permissions and actual controls before adapting any document for use.

Proactive inspections and process safety monitoring policy (8)
  • Proactive inspections and process safety monitoring policy (CWF-POL-MON · Completed fictional example)

    Set company expectations, responsibilities and resources for proactive inspections and process safety monitoring.
    Read preview · Download DOCX · Show in hierarchy

  • Proactive inspections and process safety monitoring procedure (CWF-PRO-MON · Completed fictional example)

    Explain who does what, in what sequence, the control rationale, evidence, escalation and safe restart conditions.
    Read preview · Download DOCX · Show in hierarchy

  • Risk based inspection and assurance schedule (CWF-PLN-MON-01 · Completed fictional example)

    Provide the site/task-specific risk based inspection and assurance schedule and retain its controlled output.
    Read preview · Download DOCX · Show in hierarchy

  • Daily forecourt critical control and opening check (CWF-CHK-MON-01 · Blank editable master)

    Provide the site/task-specific daily forecourt critical control and opening check and retain its controlled output.
    Read preview · Download DOCX · Download PDF · Show in hierarchy

  • Bulk site shift safety critical control check (CWF-CHK-MON-02 · Blank editable master)

    Provide the site/task-specific bulk site shift safety critical control check and retain its controlled output.
    Read preview · Download DOCX · Download PDF · Show in hierarchy

  • Leading and lagging process safety indicators (CWF-REG-MON-01 · Blank register with separate fictional worked entries)

    Provide the site/task-specific leading and lagging process safety indicators and retain its controlled output.
    Read preview · Download XLSX · Show in hierarchy

  • Safety observation intervention and corrective action (CWF-FRM-MON-01 · Blank editable master)

    Provide the site/task-specific safety observation intervention and corrective action and retain its controlled output.
    Read preview · Download DOCX · Show in hierarchy

  • Cross site critical control verification audit (CWF-AUD-MON-01 · Blank editable master)

    Provide the site/task-specific cross site critical control verification audit and retain its controlled output.
    Read preview · Download DOCX · Show in hierarchy

Open the full Crownway library