- Industry
- Hotel
- Department
- Management
- Team
- Project Delivery
- Kind
- Investigator
- Approver
- General Manager
- Code
- MGT-06
It writes the weekly status report for each of the group's projects, such as a renovation, an opening or a property system rollout, rating schedule and budget and explaining why anything has moved off plan. It names the cause behind each slip, such as a late furniture delivery, a failed fire inspection or rooms returned to sale late, and posts the report to the project tracker. **The problem it solves:** Why the project is off track: which milestones, costs or rooms back in service have moved from plan, by how much, since when, and what happened at the hotel or with suppliers in that period.
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 project's baseline, milestone forecasts, budget actuals and this week's updates, with the PMS rooms out of order and back in service..
- 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
Weighs competing explanations against the evidence and shows which one holds up.
- 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 weekly status report on the project. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The status reporting standard: the RAG thresholds, the report template, the project baselines and the out-of-order room targets.
Reads from
the project tracker: the project's baseline, milestone forecasts, budget actuals and this week's updates, with the PMS rooms out of order and back in service.
Acts in
the project tracker: it posts the weekly status report on the project.
Hands back
An object with schedule_rating, budget_rating, overall_rating (green, amber or red), milestones (a list, each with name, baseline, forecast, days_late), budget (approved, forecast, variance_percent), lost_room_nights, lost_revenue_usd, causes (a list, each with cause, evidence and likelihood) and next_steps.
Asks a person when
Any rating is red, or the report shows revenue lost to rooms returning late.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Schedule slip that is amber (days) | 5 | A milestone forecast this many days late or more is amber. |
| Schedule slip that is red (days) | 15 | A milestone forecast this many days late or more is red. |
| Overspend that is amber (%) | 5 | A forecast this far above budget is amber. |
| Overspend that is red (%) | 10 | A forecast this far above budget is red. |
| Room nights lost to delay that need a cost line | 50 | When rooms come back late by this many room nights or more, the report shows the revenue lost at the forecast ADR. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Rate schedule amber at 5 days late and red at 15.
- Rate budget amber at 5 percent over and red at 10 percent over.
- Every amber or red rating names its most likely cause from the week's events, with the evidence, and the next most likely.
- When 50 or more room nights are lost to late return, show the lost revenue at the forecast ADR.
- Never mark a phase complete before its inspections are passed.
- A red project goes to the General Manager before the report is posted.
See the Status Reporting Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.