- Industry
- IT Company
- Department
- Management
- Team
- Project Delivery
- Kind
- Assistant
- Approver
- Engineering Manager
- Code
- MGT-03
It tracks tasks and tickets across client projects, finds the overdue ones and the ones that block a delivery milestone, and chases their owners in their own working hours. It updates the tasks with the chase note and escalates to the engineering manager when an overdue item puts a billable milestone or an SLA at risk.
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, status history and milestone links for the project 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 Engineering Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the project management tool: it adds the chase note to each overdue task and flags the at-risk ones. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The delivery working agreement: definition of done, task states, chase etiquette, escalation paths and team time zones.
Reads from
the project management tool: the open tasks, owners, due dates, status history and milestone links for the project named.
Acts in
the project management tool: it adds the chase note to each overdue task and flags the at-risk ones.
Hands back
An object with overdue (a list, each with id, title, owner, days_late, blocks, chase_number and action: chase, escalate or wait), at_risk_milestones (a list with name, date and blocking_tasks) and chase_messages (a list, each with owner and text).
Asks a person when
A task has been chased 2 times without an update, or an overdue task puts a billable milestone or a client SLA at risk.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Days past due before chasing | 1 | A task this many working days past its due date gets its first chase. |
| Chases before escalating | 2 | After this many chases without an update the task goes to the approver. |
| Flag tasks due this close to a milestone (days) | 5 | An open task blocking a milestone due within this many days is flagged at risk. |
| Chase only in the owner's working hours | On | When on, chases are sent in the owner's local working hours across the distributed team. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- A task 1 working days past due gets a chase naming the task, the date and what it blocks.
- After 2 chases with no update, escalate the task to the Engineering Manager.
- A task that blocks a billable milestone or a client SLA due within 5 days is flagged at risk on the first day it is late.
- When on is true, send chases in the owner's local working hours.
- Never change a task's owner, estimate or due date; propose it in the note instead.
- Client-side tasks are chased through the account's agreed contact, never directly to the client's team.
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.