Image
Workflow
Compliance

Incident documentation and reporting

The incident gets written up weeks later, from three people’s memories of it. This is how an agent opens the record the moment somebody raises one, assembles from what your authorized records already hold, and leaves reportability, notification and closure to the accountable owner.

The incident was written up weeks later, from memory

Today

Required fields filled in by whoever was asked last

  • The incident got written up weeks later, from three people's memories.
  • The template had required fields, filled in by whoever was asked last.
  • Somebody wanted to know whether it had to be reported, and the answer came from whoever answered first.
  • By the time anyone asked for the file, it had to be rebuilt rather than read.
With agents

The file opens when a person raises the incident and collects as it runs

  • The file is assembled as the incident runs rather than rebuilt later.
  • A missing required field stops being filled by guesswork.
  • The decision that commits the business reaches the person who makes it.

How an agent runs it

An incident is an event, and its record is one you would rather start as it happens than rebuild afterwards. This workflow opens the record at that moment and assembles from what your authorized records already hold.

01

Opens

Starts the incident record the moment a person raises one, against the template your own policy defines, with the accountable owner named on it.
02

Assembles

Collects what the records you authorize already say about it, with the source of every item shown.
03

Names

Says what the template requires and the record cannot supply, and asks the named owner for it rather than filling it in.
04

Drafts

Prepares the write-up and the internal report from what the record holds, with each statement traced to the record behind it.
05

Human gate

The reportability question, every notification that leaves the business, and the closure all go to the named accountable owner, because each one commits the business and a person is the one who decides. Nothing is determined, characterised, notified or closed here, and the file can be assembled by hand at any point without the agent, because the template and the records are yours.
06

Tracks

Shows which incidents are open, which are waiting on an answer, and for how long.
07

Records

Keeps the closure the owner decides with the record, so the finished file can be read later rather than rebuilt.

Results

What changes when the file is assembled as the incident runs

Assembled while the incident runs

The record opens when a person raises the incident and collects as it goes.

Missing fields go to the owner

What the template requires and the record cannot supply is asked of the owner rather than inferred.

Reportability held for the named owner

Reportability, notification and closure are held for the named accountable owner, with the drafted record in front of them.

Where this fits

Workflow / Automate a Workflow

Tier 1 through the Automate a Workflow door: one process end to end, from the moment a person raises an incident to a record and an internal report a person decides on. Whether an incident is reportable and what it should be called are your judgement and your advisers', nothing leaves the business without the accountable owner, and nothing here is legal advice. It extends toward a compliance coordinator role as a possible next step rather than a promised state, and How It Works shows how the gates are built.

Tier 1 / Prove
How It Works

Questions, answered

No. The reportability question, every notification that leaves the business, and the closure are gated by default and go to the named accountable owner. The workflow makes no reportability determination, no notification outside and no legal characterisation, and gives no advice. The template and the records stay in your systems, so the file can be assembled by hand at any point without the agent, and How It Works shows how that authority is set.
AI Opportunity Audit

Find the incident fields left blank until the write-up

Bring the last incident you wrote up and the template your policy says it should have followed, and see which required fields your records could have filled at the time.