For risk managers and incident coordinators

See which incident actions are overdue

Certant reads your incident exports alongside your follow-up policy and lists actions past their due date, and records with no owner or date.

Each alert shows the record and the policy rule behind it.

INC-0412 · Replace damaged handrail, loading dockExample

Due 20 Oct 2026. Still recorded as open.

Overdue by 14 days Incident export, 3 Nov 2026 · row 31
The follow-up, its due date and the row it was read from.
The problem

Follow-ups slip after the report

The incident gets reported and investigated. The corrective action is assigned in a meeting and typed into a register, and nobody opens the register again until the next audit.

Some actions have no owner, and others have no due date, so there is nothing to be late against.

The documents

What Certant reads

The export can come from your incident system or from a spreadsheet register.

DocumentWhat it supplies
Incident exportsEach incident, its follow-up actions, owners, due dates and recorded state.
Follow-up policyThe timeframes and requirements your organisation has set, such as when a due date must be assigned.
Action updatesNotes or closures recorded since the last export.
The result

See each action and its rule

Incident follow-ups, checked 3 Nov 2026Example
IncidentActionOwnerDueRecorded stateStatus
INC-0412Replace damaged handrail, loading dockJ. Okafor20 Oct 2026Open
Overdue by 14 days
INC-0418Retrain forklift operatorsNone recorded14 Nov 2026Open
No owner
INC-0421Review chemical storage signageP. LindqvistNone recordedOpen
No due date
INC-0399Repair floor drain, wash bayS. Marwick30 Sep 2026Closed 28 Sep 2026
Closed on time

Detail for INC-0421

Record source
Incident export, 3 Nov 2026 · row 40
Rule
a due date is assigned within five business days of the action being raised.
Rule source
Incident management policy · section 6.2 · page 9
An action with no due date can't go overdue, so it's listed against the policy rule that says it needs one.
The approval

A person reviews each reminder

Certant drafts a reminder to the action's owner, or an escalation to their manager, with the record and the rule attached. The incident coordinator approves it before it's sent.

Proposed reminderExample
To
J. Okafor
Draft
"The handrail replacement on the loading dock, raised under INC-0412, was due on 20 October and is still recorded as open. Can you update the record or let us know what's holding it up?"
Attached
export row 31
Waiting for approval · Incident coordinator
Scope

What setup involves

We map the columns in your incident export and pick the rules from your follow-up policy that you want checked. Then we run it on a current export and you compare the list with your own.

AreaWhat to expect
ChecksCertant checks the records you export against the rules you configure.
ResponseIt isn't an emergency response tool. It doesn't decide whether an incident must be notified to a regulator, and it submits nothing to one.
Your systemIt works beside your incident-management system and doesn't replace it.
Related

Related use cases

Overdue asset inspections

Inspections that are overdue or have no report on file.

See the use case

Regulatory return gaps

Sites and periods missing from the returns you hold.

See the use case

Roster reporting gaps

Sites that haven't sent a roster return.

See the use case
See all use cases

Bring your current incident export

Send us an export of open incidents and your follow-up policy. We'll show you what's overdue and which records are missing an owner or a date.

Strata is a paid add-on for the Business plan and above. Certant Cloud, your cloud, or fully air-gapped.