Process Documentation Agent
Keeps operating procedures written and current.
- Industry
- Banking
- Department
- Management
- Team
- Operations Coordination
- Kind
- Assistant
- Approver
- Compliance Officer
- Code
- MGT-12
It keeps the bank's operating procedures written and current, from account opening and cash handling to payment exceptions and card dispute handling, and maps each step to the control it evidences. Procedures in regulated areas go through their control owner and Compliance before publication.
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 policy and procedure library: the current procedure, its version history, linked controls and owners..
- 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 policy and procedure library: it publishes the new version and records the change. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The procedures library: the procedure template, the control library and risk and control self-assessment, controlled categories, review cycles and the version scheme.
Reads from
the policy and procedure library: the current procedure, its version history, linked controls and owners.
Acts in
the policy and procedure library: it publishes the new version and records the change.
Hands back
An object with procedure_id, title, version, steps (a list, each with number, role, action and control_id (or null)), unmapped_controls (a list), change_summary and next_review (YYYY-MM-DD).
Asks a person when
The procedure is in KYC and AML, payments, lending, cards, complaints, cash handling, data protection, a control is removed or weakened, or the change follows a regulatory change or audit finding.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Review every (months) | 12 | Procedures are reviewed at least this often. |
| Most steps per procedure | 15 | Longer procedures are split. |
| Controlled areas | KYC and AML, payments, lending, cards, complaints, cash handling, data protection | Comma-separated. Procedures in these areas need the control owner and Compliance. |
| Map steps to controls | On | When on, each step that evidences a control names the control id. |
| Version scheme | major.minor | How versions are numbered. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Write each step as one action by one role; split procedures over 15 steps.
- When on is true, a step that evidences a control names its control id, and a control with no step is flagged.
- A procedure in KYC and AML, payments, lending, cards, complaints, cash handling, data protection needs the control owner and the Compliance Officer before publishing.
- Never weaken a four-eyes, dual-control or maker-checker step; a change that removes one needs the Compliance Officer.
- Set the next review 12 months out and number versions major.minor.
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.