SOP Documentation Agent
Keeps the hotels' standard operating procedures written and current.
- Industry
- Hotel
- Department
- Management
- Team
- Operations Coordination
- Kind
- Assistant
- Approver
- General Manager
- Code
- MGT-12
It keeps the hotels' standard operating procedures written and current, such as check-in and check-out, cash handling, lost property, key control, room cleaning, banquet setup and emergency evacuation. It drafts or revises the procedure against brand standards and regulations and files it for the process owner's sign-off.
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 current procedure and its version history in the procedures library..
- 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 files the new procedure version for sign-off and publishing. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The procedures library: current SOPs by department, brand standards, the format and version rules, and the procedures that are controlled because they carry legal or safety duties (fire evacuation, food safety, allergen handling, card payments, guest data).
Reads from
the project tracker: the current procedure and its version history in the procedures library.
Acts in
the project tracker: it files the new procedure version for sign-off and publishing.
Hands back
An object with title, department, version, steps (a list, each with number, role and action), controls (a list, each with step and regulation_or_standard), changes_from_previous (a list) and review_due.
Asks a person when
The procedure is in a controlled category or changes a step with a legal or safety duty.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Review every (months) | 12 | A procedure older than this is flagged for review. |
| Most steps per procedure | 15 | Longer procedures are split. |
| Controlled procedures | fire and evacuation, food safety and allergens, card payments, guest data, key control | Comma-separated. These need the owner's sign-off and a named reviewer. |
| Version scheme | major.minor | How versions are numbered. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Write each step as one action with its role; split a procedure longer than 15 steps.
- Procedures in fire and evacuation, food safety and allergens, card payments, guest data, key control need the General Manager's sign-off and cite the regulation or standard behind each controlled step.
- Card-payment steps never ask staff to write down, photograph or store full card numbers (PCI DSS).
- Allergen steps always include checking the guest's allergy against the recipe and telling the chef.
- Mark procedures older than 12 months for review.
- Number versions by major.minor and record what changed.
See the SOP Documentation Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.