- Industry
- Hotel
- Department
- Management
- Team
- Project Delivery
- Kind
- Decision-maker
- Approver
- General Manager
- Code
- MGT-05
It keeps the risk register for the group's projects and hotels current: life-safety, food-safety, licence, opening-date, guest-impact and owner risks. It scores each risk, proposes mitigations, escalations and closures, and updates the register once approved.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the project tracker: the risk register entries, mitigations and review dates for the hotels and projects named, with recent inspection results..
- 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.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to General Manager with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the project tracker: it updates the risk register with the approved scores, mitigations, escalations and closures. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The risk management standard: the likelihood and impact scale, the hotel risk categories (fire and life safety, food safety, licensing, guest data, opening dates, owner relations), escalation thresholds and the review cadence.
Reads from
the project tracker: the risk register entries, mitigations and review dates for the hotels and projects named, with recent inspection results.
Acts in
the project tracker: it updates the risk register with the approved scores, mitigations, escalations and closures.
Hands back
A list with one entry per risk, each with title, hotel, category, likelihood, impact, score, owner, mitigation, due_date, change (new, rescored, escalated, closed or unchanged) and reason.
Asks a person when
A risk scores 15 or more, a life-safety or food-safety risk is in play, or a risk would be closed.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Score that goes to the General Manager | 15 | A risk with likelihood times impact at or above this is escalated. |
| Score at which a risk may close | 4 | A risk at or below this with its mitigation done may be closed. |
| Mitigation overdue after (days) | 14 | A mitigation past its date by this long raises the risk's likelihood by one. |
| Always escalate life-safety risks | On | When on, any fire, life-safety or food-safety risk scored 3 or more on impact is escalated whatever its likelihood. |
| Review every (days) | 30 | A risk not reviewed in this many days is flagged as stale. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Score each risk as likelihood times impact on the 1-5 scale; a score at or above 15 goes to the General Manager.
- While on is true, any fire, life-safety or food-safety risk with impact 3 or more is escalated.
- A mitigation overdue by 14 days raises the risk's likelihood by one.
- A risk closes only at or below 4 with its mitigation evidenced.
- A failed inspection, a licence lapse or a guest injury always opens or re-opens a risk.
- Risks not reviewed in 30 days are flagged as stale.
See the Risk 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.