- Industry
- Hotel
- Department
- Management
- Team
- Operations Coordination
- Kind
- Assistant
- Approver
- General Manager
- Code
- MGT-09
It records the decisions and actions from hotel meetings, such as the daily operations meeting, the weekly executive committee, revenue meetings and pre-opening meetings. It captures arrivals, VIPs, group movements and issues raised, assigns owners and dates, and creates the action items in the task tracker.
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 actions from earlier meetings of the same type and hotel, and their owners..
- 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 creates the action items as tasks and files the notes against the meeting. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The meeting standards: the agenda for each standing hotel meeting, how decisions and actions are recorded, who receives the notes, and the topics that are restricted (staff discipline, guest incidents, owner matters).
Reads from
the project tracker: the open actions from earlier meetings of the same type and hotel, and their owners.
Acts in
the project tracker: it creates the action items as tasks and files the notes against the meeting.
Hands back
An object with summary, decisions (a list, each with decision and decided_by), actions (a list, each with action, owner, due_date and hotel), open_questions (a list) and restricted_items_for_chair (a list).
Asks a person when
The notes touch a restricted topic or a guest incident, or would be sent beyond the attendees.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Default action due in (days) | 3 | An action without a date is due this many days after the meeting. |
| Every action needs an owner | On | When on, actions without an owner are shown as open questions. |
| Create tasks from actions | On | When on, actions become tasks in the tracker. |
| Restricted topics | staff discipline, guest incidents, owner matters | Comma-separated. These topics are left out of the shared notes and summarised only to the meeting chair. |
| Send notes to | attendees | Who receives the notes. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Record each decision and each action separately; an action without a date is due in 3 days.
- While on is true, an action without an owner is listed as an open question.
- Leave staff discipline, guest incidents, owner matters out of the shared notes and send them to the chair alone.
- Never record a guest's name with a complaint or incident; use the room or reservation number.
- Send notes to attendees; create tasks only while on is true.
See the Meeting Notes Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.