Health · Safety · Environment

HSE that runs in the flow of work — not bolted on beside it.

Contego operationalizes HSE. Observations, risk, investigations, corrective actions, audits and learning live in one connected loop — each feeding the next — so safety happens where the work happens, not in a folder no one opens.

Built for offshore · fabrication · resourcesAligned to IOGP · ICAM · Life-Saving Rules
The HSE loop: observations, risk, incident, corrective action, audit and learning, each feeding the next.THEHSE loopone systemObservationscatch it earlyRisk · Bowtiescritical controlsInvestigationICAM · root causeActionsthat actually closeAuditsstandards → checksLearningprove the control
The bolt-on trap

Most HSE software is a bolt-on. So nothing compounds.

Point tools and compliance add-ons collect the same data twice and connect none of it. The signal you captured this morning never reaches the decision it should change.

Bolted on

  • Observations disappear into a form and a monthly count.
  • Audits live in spreadsheets; findings never become actions.
  • Incidents are investigated in isolation from the risks they prove.
  • Corrective actions are opened and quietly forgotten.
  • The LMS was bought from someone else and speaks a different language.

Operationalized

  • A near-miss trend becomes a leading indicator on the risk register.
  • A failed audit check opens a tracked action with an owner and a due date.
  • An investigation re-scores the very risk whose control failed.
  • Every action closes out through verification — or it isn't closed.
  • Training currency proves the control is actually effective.
The operating model

One loop. Every signal feeds the next decision.

This is what "operationalized" means in practice — the edges between modules are the product. A signal enters anywhere and drives everything downstream.

Forward path

  • Observation → Risk. Volume and type of everyday observations become a leading indicator on the register.
  • Risk → Investigation. When a critical control fails, it escalates straight to an investigation.
  • Investigation → Actions. Root causes auto-generate corrective actions and learnings.
  • Actions → Audits. Actions close out through audit verification.

Feedback path

  • Investigation → Risk. Every incident re-assesses the related risks.
  • Investigation → Learning. Learnings become short refreshers pushed to the crews who need them.
  • Learning → Actions. Training currency proves an action's control is effective.
  • Audits → Actions. Non-compliances feed the same register as incident actions.
The modules

Six modules. None of them stands alone.

Each is strong on its own — and each is worth more because of what it feeds.

Capture

Hazard Observations

Mobile-first: tap, photo, submit. Tagged by IOGP 577 activity and Life-Saving Rule at the point of capture.

Feeds → trends into the Risk Register
Anticipate

Risk & Bowties

Configurable 5×6 matrix, bowtie analysis and Critical Control Management — the controls that actually stop a fatality.

Feeds → a failed control to Investigation
Understand

Incident Investigation

Severity-tiered, ICAM-aligned, with 5-Whys, causal timelines and AI-assisted capture that gets to the real cause.

Feeds → corrective actions + learnings
Close

Corrective Actions

One company-wide register across incidents and audits. Owner, due date, verification — actions that actually close.

Feeds → audit verification
Verify

Audits & Inspections

A reusable question bank and IOGP 577 checklists, scored, with findings that don't die on the page.

Feeds → findings become tracked actions
SustainComing soon

Learning (LMS)

Focused HSE-compliance learning tied to the same records, so training currency and the audit trail just work.

Feeds → proof the control holds
Why this isn't a bolt-on

The proof is in the edges, not the feature list.

Four things a bolt-on structurally can't do — because its modules were never one system.

01

Controls fire at the point of work

Log a lift at ≥ 90% of rated capacity or work above1.8 m and the IOGP 577 control requirement appears as you capture — not months later in an audit finding.

02

A failed check becomes a tracked action

A non-compliant audit item lands in the same company-wide action register as incident actions — owner, due date, verification — so the loop closes instead of leaking.

03

One safety lens, everywhere

The same Life-Saving-Rule and fatality-risk classification runs through observations, incidents and audits, so your leading indicators and your investigations speak one language.

04

Leading indicators from normal work

Trends in everyday observations surface control degradation before the incident — Safety-II, learning from work as it's actually done, not just from what went wrong.

Where we stand

Built for operators — not bolted onto an ERP.

The incumbents are powerful and dated, or modern and shallow. Contego is one connected system, built mobile-first, for how Australian operations actually run.

Modern & mobileCapture in the field on a phone — not a legacy desktop UI.
LMS built inLearning is part of the loop, not a separate purchase and login.
AU frameworks nativeIOGP, ICAM, Life-Saving Rules and regulator reporting, out of the box.
One connected systemNot six point tools stitched together after the sale.
Credibility

Built by operators. Aligned to the standards that run hard industries.

Contego was built by people who ran the HSE function offshore and on the tools — and mapped to the frameworks majors and regulators already expect. You don't retrain your system to fit the software.

6
Connected modules
9
Life-Saving Rules, one lens
1
System, not a stack

Explore the HSE guides →

Stop bolting HSE on. Start operating it.

See the loop running on live data — observation to risk to action to audit — in a 30-minute walkthrough.