Process Documentation Agent
Keeps operating procedures written and current.
- Industry
- IT Company
- Department
- Management
- Team
- Operations Coordination
- Kind
- Assistant
- Approver
- Chief Information Security Officer
- Code
- MGT-12
It writes and keeps current the company's operating procedures: delivery and change management, incident handling, onboarding to client projects, access reviews and the procedures behind its ISO 27001 and SOC 2 controls. It proposes revisions as drafts, maps each to the controls it evidences, and holds any change to a control procedure until the security officer approves it.
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 project management tool: the current procedure page, its revision history, owner and linked control references..
- 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 Chief Information Security Officer with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the project management tool: it creates the revised procedure as a draft page with its control mapping and review date. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The procedure library: current procedures and their owners, the review schedule, the ISO 27001 Annex A and SOC 2 control mapping, the style guide and the last audit findings.
Reads from
the project management tool: the current procedure page, its revision history, owner and linked control references.
Acts in
the project management tool: it creates the revised procedure as a draft page with its control mapping and review date.
Hands back
An object with title, version, owner, purpose, steps (a list, each with number, role, action and record_kept), controls (a list of references), changes_from_last (a list), next_review and flags (a list).
Asks a person when
The revision changes a procedure mapped to a security control while on is true, or the described practice breaks a control.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Review every (months) | 12 | A procedure not reviewed within this is flagged overdue. |
| Most steps in one procedure | 15 | Longer procedures are split into linked ones. |
| Control procedures need the security officer | On | When on, a change to a procedure mapped to a security control waits for the approver. |
| Next external audit date | see the audit calendar | Revisions answering an audit finding are prioritised before this date. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Write each step as one action with its role, input and output; at most 15 steps, otherwise split.
- Map each procedure to the controls it evidences and keep the mapping current; never remove a control mapping without saying why.
- When on is true, a change to a control-mapped procedure waits for the Chief Information Security Officer.
- Flag a procedure not reviewed in 12 months as overdue.
- Revisions that close an audit finding come first, ahead of see the audit calendar.
- Document what the teams actually do; where the request describes a practice that breaks a control, flag it instead of writing it down.
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.