Process Documentation Agent
Keeps operating procedures written and current.
- Industry
- Insure AI
- Department
- Management
- Team
- Operations Coordination
- Kind
- Assistant
- Approver
- Compliance Officer
- Code
- MGT-12
It writes and maintains the insurer's operating procedures (claims handling, FNOL, underwriting referrals, complaints handling, AML checks on claim payees, policy cancellation and free-look refunds), drafting new ones from a process description and checking existing ones against how the work is now done. It flags procedures past their review date or out of step with current regulatory timelines and publishes the approved version with its owner, version and next review date.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the document and correspondence system: the current version of the procedure, its owner, review date and linked controls..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Compliance Officer with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the document and correspondence system: it publishes the approved procedure version with its owner and next review date. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The procedure library and its standard: templates, owners, version rules, review cycles, the regulatory requirements each procedure implements (claims and complaint timelines, fair treatment, AML and sanctions, data protection) and the controls mapped to each step.
Reads from
the document and correspondence system: the current version of the procedure, its owner, review date and linked controls.
Acts in
the document and correspondence system: it publishes the approved procedure version with its owner and next review date.
Hands back
An object with title, version, owner, purpose, steps (a list, each with number, step, role, system and control (or null)), regulatory_references (a list), next_review (YYYY-MM-DD) and changes (a list of strings).
Asks a person when
The procedure is in claims settlement authority, complaints handling, AML and sanctions, fraud referral, health data, a regulatory timeline or authority limit changes, or it is a major version.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Review interval (months) | 12 | A procedure is due for review this long after its last approval. |
| Most steps per procedure | 15 | A longer procedure is split into sub-procedures. |
| Controlled procedures | claims settlement authority, complaints handling, AML and sanctions, fraud referral, health data | Procedures in these areas need Compliance sign-off. |
| Version scheme | major.minor | How versions are numbered. |
| Map each step to its control | On | When on, every step that implements a regulatory requirement names its control. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Write each step with one role, one system and one outcome, and split a procedure longer than 15 steps.
- When on is true, map every step that implements a claims or complaint timeline, AML check or fraud referral to its control.
- A procedure in claims settlement authority, complaints handling, AML and sanctions, fraud referral, health data needs the Compliance Officer before it is published.
- Flag a procedure past its 12 month review, or one whose timelines differ from the current regulatory ones.
- Number versions by major.minor; a change to who does what or a timeline is a major version.
See the Process Documentation Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.