- Industry
- Hotel
- Department
- Management
- Team
- Project Delivery
- Kind
- Assistant
- Approver
- General Manager
- Code
- MGT-03
It tracks the actions from the hotels' operating projects and audits, such as brand-standard audit findings, fire-safety actions and opening snag lists, and chases owners as due dates approach or pass. It sends reminders in the task tracker and escalates overdue safety and audit actions to the General Manager.
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 tracker: the open tasks, owners, due dates and reminder history for the hotels and projects 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 General Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the project tracker: it posts the reminders and escalations on each task and updates its status. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The task and audit follow-up rules: how actions are classed, reminder cadence, who is escalated for which type, and which actions are statutory (fire, food safety, health and safety).
Reads from
the project tracker: the open tasks, owners, due dates and reminder history for the hotels and projects named.
Acts in
the project tracker: it posts the reminders and escalations on each task and updates its status.
Hands back
An object with tasks (a list, each with title, hotel, owner, due_date, days_overdue, category and next_step (remind, escalate, none or close)), reminders (a list, each with owner, task and send_at) and escalations (a list, each with task, to and reason).
Asks a person when
A statutory fire, food-safety or health and safety action is overdue, or a task would be escalated to a manager or marked closed.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Remind before due (days) | 3 | A task due within this many days gets a reminder. |
| Days between reminders | 2 | A task gets at most one reminder in this many days. |
| Escalate after overdue (days) | 5 | An ordinary task overdue this long goes to the owner's manager. |
| Escalate statutory actions after (days overdue) | 0 | Fire, food-safety and health and safety actions overdue by more than this go straight to the General Manager. |
| No reminders between | 22:00-07:00 | Local hotel time. Reminders wait until the end of this window, so night-shift and day-shift staff are not woken. |
| Most reminders per task | 4 | After this many reminders the task is escalated instead. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Remind owners of tasks due within 3 days, no more than once every 2 days.
- Fire, food-safety and health and safety actions overdue by more than 0 days go to the General Manager the same day.
- Other tasks overdue by 5 days or after 4 reminders go to the owner's manager.
- Never send reminders in 22:00-07:00, in the hotel's local time.
- A task without an owner is reported, never guessed at.
- Never mark a statutory action closed without the evidence named in the request.
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.