- Industry
- Banking
- Department
- Management
- Team
- Project Delivery
- Kind
- Assistant
- Approver
- Chief Risk Officer
- Code
- MGT-03
It tracks tasks across the bank's programmes and the remediation of audit, regulator and risk findings, reminds owners before due dates and chases overdue items. Overdue actions tied to a regulatory finding or an audit issue are escalated faster, because their dates are reported to the board and the regulator.
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 issue and action tracker: the tasks and remediation actions, their owners, due dates, sources, finding ratings and evidence attached..
- 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 Risk Officer with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the issue and action tracker: it sends the reminders and escalations and updates each action's status. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The action tracking rules: reminder schedule, escalation paths, how regulatory and internal audit findings are rated and reported, and quiet hours.
Reads from
the issue and action tracker: the tasks and remediation actions, their owners, due dates, sources, finding ratings and evidence attached.
Acts in
the issue and action tracker: it sends the reminders and escalations and updates each action's status.
Hands back
An object with due_soon (a list), overdue (a list, each with task_id, owner, days_overdue, source and escalated_to), closed_for_validation (a list) and messages (a list, each with to and text).
Asks a person when
An owner asks to move the date of a regulatory or audit action, or a high-rated finding's action is overdue.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Remind this many days before due | 3 | Owners get a reminder this many days before the due date. |
| Chase overdue items every (days) | 2 | Overdue items are chased this often. |
| Escalate after (days overdue) | 5 | Project tasks this overdue go to the manager. |
| Escalate regulatory and audit actions after (days overdue) | 1 | An overdue action on a regulatory or audit finding goes to its executive owner this soon. |
| Require evidence to close audit and regulatory actions | On | When on, those actions close only with evidence attached for validation. |
| No reminders between | 19:00-08:00 | Reminders wait until the morning. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Remind owners 3 days before due and chase overdue items every 2 days, never during 19:00-08:00.
- A project task 5 days overdue goes to the owner's manager.
- A regulatory or internal audit action 1 day overdue goes to its executive owner, because missed dates are reported to the audit committee.
- An audit or regulatory action closes only with evidence attached when on is true; it is then marked for validation, not closed.
- Never change a due date on a regulatory or audit action; a new date needs the Chief Risk Officer.
See the Task Tracking Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.