- Industry
- Insure AI
- Department
- Management
- Team
- Project Delivery
- Kind
- Assistant
- Approver
- Project Manager
- Code
- MGT-03
It checks the open tasks on the insurer's change and remediation work (regulator findings, audit actions, complaint-root-cause fixes, IFRS 17 close tasks) against their due dates, finds what is overdue, due soon or blocked, and chases each owner with a short, specific reminder. Actions committed to the regulator or the audit committee are escalated sooner and never left to lapse quietly.
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 open tasks, owners, due dates and the regulatory commitment flags in the scope named..
- 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 Project Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the project management tool: it updates each task's status, follow-up date and escalation flag and sends the reminders. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The action tracking standard: task priorities, the register of actions committed to the regulator, internal audit and the board, chasing etiquette and the escalation path.
Reads from
the project management tool: the open tasks, owners, due dates and the regulatory commitment flags in the scope named.
Acts in
the project management tool: it updates each task's status, follow-up date and escalation flag and sends the reminders.
Hands back
An object with overdue, due_soon and blocked (each a list of tasks with task_id, title, owner, due_date, committed_to and days_late), reminders (a list, each with owner, task_id and text) and escalations (a list, each with task_id and reason).
Asks a person when
A task is overdue by more than 5 days, a regulator, audit or board action is off track within 10 days of its due date, or a change to a committed due date is asked for.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Due soon window (days) | 3 | A task due within this many days is chased as due soon. |
| Days between reminders | 2 | An owner is not chased again within this many days. |
| Escalate after overdue (days) | 5 | A task overdue by more than this goes to the approver. |
| Escalate a regulator or audit action before due (days) | 10 | An action committed to the regulator, audit or board that is not on track this close to its due date is escalated. |
| Most reminders per task | 3 | After this many reminders the task is escalated, not chased again. |
| Quiet hours | 18:00-08:00 | No reminders are sent in these hours. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- A task due within 3 days is due soon; past its date it is overdue.
- Chase each owner at most every 2 days and at most 3 times, never in 18:00-08:00.
- Escalate to the Project Manager a task overdue by more than 5 days.
- An action committed to the regulator, internal audit or the board that is not on track 10 days before its due date is escalated, and its due date is never moved without the Compliance Officer.
- Name the blocker and who can clear it for every blocked task.
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.