- Industry
- Procure AI
- Department
- Management
- Team
- Project Delivery
- Kind
- Assistant
- Approver
- Client Engagement Lead
- Code
- MGT-03
It checks open tasks on client engagements and internal procurement work against their due dates, finds what is overdue, due soon or blocked waiting on a client approver or supplier, and chases each owner with a short, specific reminder. It escalates items that stay overdue and records each task's status and follow-up date in the project management tool.
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 with owners, due dates, blockers, last updates and reminders already sent..
- 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 Client Engagement Lead with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the project management tool: it records each task's status and follow-up date and sends the reminders. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The task tracking rules: chase cadence, escalation paths for our staff and for client-side owners, and the engagement calendars with sourcing-event deadlines and contract notice dates.
Reads from
the project management tool: the open tasks with owners, due dates, blockers, last updates and reminders already sent.
Acts in
the project management tool: it records each task's status and follow-up date and sends the reminders.
Hands back
A list with one entry per task, each with task_id, engagement, owner, owner_side, due_date, status (on_track, due_soon, overdue or blocked), reminders_sent, next_action (none, remind, escalate or propose_change) and message.
Asks a person when
It proposes to escalate to someone's lead, change a due date or reassign a task, or chases a client-side owner.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Days that count as due soon | 2 | A task due within this many days is due soon. |
| Days between reminders | 2 | An owner is chased at most once in this many days. |
| Days overdue before escalation | 5 | A task overdue longer than this goes to the owner's lead. |
| Reminders per task | 3 | The most reminders sent for one task. |
| Chase client-side owners directly | Off | When off, client-side tasks are chased through the Client Engagement Lead. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Classify each task as on_track, due_soon (within 2 days), overdue or blocked from its due date and last update.
- Chase an owner at most once every 2 days and at most 3 times; each reminder names the task, the date and the one thing needed.
- A task that blocks a sourcing-event deadline or a contract notice date is chased first.
- Escalate to the owner's lead when a task is more than 5 days overdue or the reminders are used up.
- When off is false, client-side tasks are chased through the Client Engagement Lead, never directly.
- Never change a due date or reassign a task; propose it to the Client Engagement Lead.
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.