REGISTER REGISTER TO LEARN

Read -> Check Steps -> Flag Gaps -> Review -> Verify

Change and Relief-Verification Agent

The agent reads your management-of-change register and flags records that skipped a required step or closed without a pre-startup review, plus changes that left a relief or interlock scenario unverified. It also lists overdue actions from process-hazard studies. It reads the change register, the hazard-study action tracker, the relief-device register, and pre-startup review records, then returns a set of lists the safety team can work through.

The Problem

The change was closed. The relief case was never re-run. The line ran for a year on an assumption.

A small piping change went through eighteen months ago to add a bypass. The management-of-change record was opened, the drawing was updated, and the change was marked closed. What no one did was re-run the relief case for the vessel now that the bypass could block a relief path. The gap sat quietly in a closed record until an audit asked to see the relief verification and found nothing attached.

What Changes

Every closed change checked for the step that was skipped

The agent reads the change register and the linked trackers and looks for records that were closed without a pre-startup review, changes that touched a relief or interlock scenario without a re-check, and hazard-study actions that are past due. It returns an incomplete-change list, a closed-without-review list, a relief-scenarios-to-recheck list, and an overdue-action list. The safety engineer works from four short lists instead of reading every record.

Humans stay in control: the agent flags the gaps, and your process safety engineer decides which changes are reopened, re-reviewed, or re-verified.

HOW THE AGENT WORKS

TRIGGERLLMAPIDECISIONACTIONWAIT
TRIGGERWeekly review schedule firesRuns on a schedule and on demand before an audit or management review.
APIRead change and action trackersPulls the management-of-change register and the hazard-study action tracker.
APIRead relief and review recordsPulls the relief-device register and pre-startup review records to match against changes.
LLMCheck each change for gapsTests each change for missing steps, missing reviews, and unverified relief or interlock scenarios.
DECISIONAny gap or overdue action?
LLMDraft the four listsWrites the incomplete-change, closed-without-review, relief-to-recheck, and overdue-action lists.
ACTIONSend lists to safety engineerDelivers the four lists to the process safety engineer for review.
The agent does not approve changes, close records, or sign a relief verification. Your process safety engineer does. The agent removes the manual audit of every change record to find the ones missing a step.

HOW TO BUILD IT

Three levels of depth. Pick the one that matches where you are.

For the ops person who needs to understand what's involved and brief their team.

Your Change RecordsChange register, action tracker, relief register, review records
The AgentWorkflow engine + LLM
Your Safety TeamProcess safety engineer reviews the lists

WHAT YOUR TEAM PROVIDES ONCE

  • Change register - your management-of-change records with steps, status, and what each change touched
  • Hazard-study action tracker - the actions from process-hazard studies with due dates and status
  • Relief-device register - the relief and interlock scenarios tied to equipment
  • Pre-startup review records - the reviews that should exist before a change is closed
  • A notification channel - email, Teams, or Slack where the lists land
What happens day-to-day: on a set schedule the agent reads the change register and its linked trackers, checks each record for a skipped step or an unverified relief case, and sends the safety engineer four short lists. Before an audit or a management review, the same run can be triggered on demand. The engineer works the lists rather than re-reading every change.

For the IT person or technical lead who needs to scope the integration.

INQUIRY SOURCES

Management-of-change register export
Hazard-study action tracker export
Relief-device register and pre-startup review records

WORKFLOW ENGINE (N8N)

Schedule or on-demand run
Fetch change and action records
Fetch relief and review records
Test changes for missing steps
Gaps found?
Build the four lists JSON
Post lists to safety channel

CONNECTS TO

Change tracker (SAP MoC / Enablon / spreadsheet)Read: change records, steps, status. Write: none
Action tracker (Enablon / Intelex / spreadsheet)Read: hazard-study actions, due dates. Write: none
Relief register (spreadsheet / asset register)Read: relief and interlock scenarios by tag. Write: none
Notification (Email / Microsoft Teams / Slack)Read: none. Write: the four gap lists
WITHOUT PMS API

Without API access, the trackers are exported to spreadsheets on a schedule and the agent reads those. The four lists are the same, they just reflect the last export rather than live status.

WITH PMS API

With API access to the change and action trackers, the agent re-checks as records change and can flag a change that closes without its review the same day it happens. Best experience.

For the person who wants to build this agent step by step. Each node below maps to an n8n workflow node.

TRIGGERNode 1
Trigger - scheduled review
n8n Schedule node weekly, plus a manual trigger for pre-audit runs.
Output: The set of change records and linked actions to check.
APINode 2
HTTP Request - read records
GET change records, hazard-study actions, relief scenarios, and review records.
Output: A joined dataset keyed by change id and equipment tag.
LLMNode 3
LLM - check each change for gaps
Send each change with its linked review and relief data, ask which required steps are missing.
You are a process-safety change reviewer. For each change record, decide whether it is missing any required step: a pre-startup review before closure, a relief or interlock re-check when a relief scenario was affected, or an open hazard-study action past its due date.

Changes: {change_records}
Relief scenarios: {relief_scenarios}
Reviews: {review_records}
Today: {today}

Respond ONLY with valid JSON. No explanation.
INPUT
change MOC-231 closed, touched relief scenario RV-14, no review record; action A-88 due last month still open
OUTPUT
{"incomplete_changes": [], "closed_without_review": ["MOC-231"], "relief_to_recheck": [{"change": "MOC-231", "scenario": "RV-14"}], "overdue_actions": ["A-88"]}
DECISIONNode 4
IF - any gap found
n8n IF node on any list not empty.
Output: Routes findings to the list builder.
LLMNode 5
LLM - draft the four lists
Turn the gap data into four readable lists with the reason for each entry.
Turn this gap data into four lists for a process safety engineer: incomplete changes, closed without review, relief scenarios to re-check, and overdue actions. Give one line of reason per entry.

Gaps: {gaps_json}

Respond ONLY with valid JSON. No explanation.
INPUT
closed_without_review MOC-231, relief_to_recheck MOC-231 RV-14, overdue_actions A-88
OUTPUT
{"closed_without_review": [{"id": "MOC-231", "reason": "closed with no pre-startup review attached"}], "relief_to_recheck": [{"id": "MOC-231", "reason": "affected relief scenario RV-14, no re-check"}], "overdue_actions": [{"id": "A-88", "reason": "past due, still open"}]}
ACTIONNode 6
Send - notify safety engineer
n8n Email node sending the four lists to the process safety team.
Output: A message with the four gap lists.
MVP vs Advanced — Where To Start
MVP — START HERE
  • Start with the last two years of changes on one unit so the register is a manageable size.
  • Export the change register and relief scenarios to a spreadsheet with a shared tag column.
  • Check for the two gaps that matter most first: closed without review, and relief scenario not re-checked.
  • Have the safety engineer confirm each flag against the real record for a month.
  • Add the overdue-action list once the change flags are trusted.
  • Only then extend across all units and the full change history.
ADVANCED — ADD LATER
  • =+ Connect the change tracker API so a change closing without a review is flagged the same day.
  • =+ Add interlock-bypass records so temporary bypasses left open are flagged too.
  • =+ Link relief scenarios to equipment tags so any change on that tag prompts a re-check question.
  • =+ Draft a pre-audit pack that lists every gap with the evidence needed to close it.
  • =+ Trend gap types by area to find where the change process breaks down.
  • =+ Keep a dated snapshot of each run so an auditor can see the state at any past review.

Full Video Walkthrough Coming Soon

Watch the agent find a closed change that skipped its relief re-check.

Register to be notified

Everything on this page is free to learn.

When you're ready to build — do it yourself or bring us in.

Register FOR WALKTHROUGHS
Book a call to scope this

OTHER AGENTS IN LEASING & MARKETING

Permit-to-Work Conflict and Simultaneous-Work Checker

Flags clashing permits and open-but-expired work before the shift starts

Statutory Safety Test and Certificate Agent

Keeps one live list of every statutory test and its due date

Incident Repeat-Cause and Action-Effectiveness Agent

Catches repeat root causes and corrective actions that did not work

Frequently asked questions

Change and Relief-Verification Agent is an AI agent that flags changes that skipped a step or left a relief scenario unverified.
The change was closed. The relief case was never re-run. The line ran for a year on an assumption. The Change and Relief-Verification Agent addresses this: flags changes that skipped a step or left a relief scenario unverified.
No. Your team stays in control. The agent does not approve changes, close records, or sign a relief verification. Your process safety engineer does. The agent removes the manual audit of every change record to find the ones missing a step.

This is 1 of 4 agents in Safety, Health & Environment. → · Explore all 15 departments →