The daily department heads' meeting: a fifteen-minute agenda that gets things done
A daily department heads' meeting should take fifteen minutes and produce clear decisions. This guide explains the fixed agenda, the single number sheet, and the simple action log that keeps the meeting short and effective.
Contents
Key takeaways
- The daily meeting exists to synchronise one business day, so its only durable output is a one-line action log with an owner and a date for every item.
- A fixed order, yesterday, today, tomorrow, problems, stops the meeting from turning into a general discussion.
- Numbers are read before the meeting on a single sheet; anything inside its normal band is not spoken aloud.
- Anything that needs comparison across days or weeks belongs in the weekly meeting, not in the daily one.
- An item with no owner, or no date, is not an action; it is a wish that will be repeated tomorrow.
A daily department heads' meeting is a short stand-up where each department states the day's exceptions and the group assigns owners and dates. The agenda is fixed: yesterday, today, tomorrow, problems. Numbers arrive on one sheet beforehand, so the fifteen minutes go on decisions, not on reading reports.
It is 09:05. Eleven people are in the back office, the front office manager is reading yesterday's occupancy aloud, and the housekeeping manager is still waiting to say that two rooms have no hot water. By 09:40 the meeting has covered everything and decided nothing. This article gives you a hotel daily department meeting agenda that fits in fifteen minutes: who attends, what runs in which order, which numbers belong on the one sheet, and how to keep an action log that survives contact with a real morning.
Why hold a daily department heads' meeting at all?
Because a hotel sells a perishable product: a room that is empty tonight cannot be sold tomorrow, so the decisions that protect tonight expire within hours. The daily meeting exists to take those decisions once, in one room, before the day starts.
The meeting is a synchronisation tool, not a management tool. It aligns departments on one business day; it does not plan the season, review performance or solve structural problems. Its output is decisions and owners, not discussion. If the meeting ends and nobody can name what changed, it was a report reading with chairs.
Short is a design constraint, not a virtue. Fifteen minutes forces the agenda onto exceptions, because there is no time to recite what everyone already knows. The trade-off is real: a short meeting only works if the numbers arrive before it starts. If the sheet is prepared in the room, the meeting becomes the place where the numbers are discovered, and it will run long every day.
Keep three rhythms separate: daily for the day's exceptions, weekly for planning and trends, monthly for review. Mixing them is the most common reason a daily meeting grows to forty minutes. The meeting also has a social function that is easy to dismiss: department heads hear each other's constraints out loud, which reduces the corridor negotiations that otherwise happen at 15:00 when it is already late.
Who should attend the daily briefing, and who should send notes?
Attend if you hold a number on the sheet or an action on the log. Everyone else sends a written note to the chair before the meeting and reads the log afterwards.
Standing attendees are the general manager or duty manager as chair, front office, housekeeping, food and beverage, and technical or maintenance. Reservations or revenue joins when the day's pace or a group block is on the agenda. Guest relations, spa, security and the outsourced laundry or cleaning contractor are invited when their item is on the sheet, not by default. A standing invitation for people who never speak trains everyone that attendance is symbolic. If you are unsure who owns what, a clear hotel organisation chart: departments, roles and who decides what settles it before the first meeting.
The chair's job is timekeeping and closure, not content. The chair does not answer questions that another department head owns; the chair asks for an owner and a date. One fixed scribe keeps the log, and the same person for months rather than a rotation. A stable format is worth more than fairness in the rota.
The night team does not attend; its observations reach the meeting through the handover notes that feed the yesterday block. Say this explicitly, or someone will start waking the night manager. No vendors, no consultants, no agency representatives. Commercial conversations happen elsewhere, with the department head who owns the contract.
What is the fixed order of the agenda?
Four blocks in the same order every day: yesterday, today, tomorrow, problems. The order never changes, so nobody has to think about what comes next and the meeting cannot be reordered by whoever speaks loudest.
Yesterday covers what the numbers do not show: incidents, complaints, no-shows, walk-ins, overbookings handled, maintenance failures, VIP treatment that went wrong, and anything the handover notes flagged. Today covers the operating day: arrivals and departures with their peak times, rooms out of order, groups in house and arriving, events, expected staffing gaps, and the one or two moments where the house will be under pressure. Tomorrow covers what needs a decision today: early breakfast requests, group departures with luggage, contractors on site, VIP amenities, and rooms that must be released or held.
Problems is the shortest block and the most abused. Only items that need a decision from someone in the room today enter it. Everything else goes to the log or to the weekly meeting. Give each block a time budget and keep it visible, for example four minutes for yesterday, four for today, three for tomorrow and four for problems. The numbers are illustrative; the discipline of a budget is not. The chair closes each block with a single question: what did we decide, and who owns it.
ChecklistThe chair's checklist for the four blocks
- Yesterday: what happened that the numbers do not show, and is anything still open from it?
- Today: where will the house be under pressure, and at what hour?
- Tomorrow: what must be decided today so that tomorrow runs?
- Problems: which of these needs a decision from someone in this room today, and which can be logged?
The yesterday block draws directly on the front desk shift handover checklist: cash, arrivals and promises, so the two documents should agree on what counts as an open item.
Which numbers belong on the one sheet?
One page, same layout every day, distributed before the meeting: the day's room and guest counts, the exceptions in housekeeping and maintenance, and the commercial items that change today's decisions.
Room side: rooms available, arrivals, departures, stayovers, rooms out of order and out of service, and tonight's occupancy. Keep out of order and out of service as separate lines; they mean different things and only one of them is a sellable-room decision. Group side: rooms picked up against each block, remaining block, and the cut-off date. This is the line that most often changes a decision on the day, and reading it well is the skill behind the hotel pickup report: how to read booking pace day by day.
Housekeeping side: rooms cleaned, rooms remaining, and the departures still in house. Link this to the room report so the front desk and housekeeping are reading the same status; the mechanics are covered in housekeeping reports explained: room report, discrepancy and attendant sheets. Maintenance side: open jobs with age in days, and anything that removes a room from sale. Commercial side: food and beverage covers and reservations, VIP arrivals, and complaints logged yesterday.
Every line carries a normal band. Only a number outside its band is spoken aloud; a number inside it is read and passed over. Without bands, the sheet becomes a script and the meeting becomes a reading.
| Number | Who brings it | What makes it worth mentioning |
|---|---|---|
| Arrivals, departures, stayovers | Front office | A peak hour or a count that strains the desk |
| Rooms out of order and out of service | Technical and housekeeping | Any change that removes or returns a sellable room |
| Group rooms picked up against block | Reservations | A cut-off date or a pickup that changes availability |
| Rooms remaining to clean | Housekeeping | A gap against the departure pattern |
| Open maintenance jobs | Technical | Any job older than its agreed age |
| Food and beverage covers | F&B | A function or a full outlet |
| VIP arrivals and complaints | Guest relations or front office | Any VIP or any repeat complaint |
Agree the definitions before you agree the layout
Room status codes and the boundary between out of order and out of service are common practice rather than a universal standard, and hotel systems differ. Agree the definitions once and write them at the foot of the sheet, so the sheet says what this hotel means.
What makes an action log work?
Three fields and nothing else: the item, the owner, the date. A log with more columns is a project plan, and a project plan written in fifteen minutes is abandoned within a month.
The item is one sentence in plain words, written as an outcome rather than an activity: not "look at the hot water" but "rooms 214 and 216 back in service or blocked". The owner is one named person, not a department. "Housekeeping" cannot be asked on Thursday whether it was done. The date is a day, not "this week". If the item genuinely has no deadline, the date is the day it will be reviewed again.
The scribe writes during the meeting and the chair reads the new lines back at the end. Reading back takes under a minute and catches the misheard owner before it becomes a missed task. The next meeting opens with the open items, oldest first, before the four blocks. An item that has slipped twice is not a scheduling problem; it is a decision the meeting is avoiding.
Only cross-department items and items with a deadline enter the log. A task that lives inside one department stays in that department's own list, or the log fills with noise and stops being read.
Key pointThe log line format
Date opened · item written as an outcome · one named owner · review date · status. Closing rule: an item with no owner or no date is not an action and does not enter the log.
What belongs in the weekly meeting instead?
Anything that needs comparison across days or weeks, or more than two departments to design. The daily meeting handles today; the weekly meeting handles the pattern behind today.
Move to weekly: booking pace and pickup trends, staffing and rota planning, training, supplier and contract issues, menu and pricing changes, deep cleaning and preventive maintenance schedules, and complaint themes rather than single complaints. The test is time and shape, not importance. If an item cannot be decided in two minutes by the people in the room, it is not a daily item, however urgent it feels at 09:10.
Give the daily meeting one escalation phrase: "this needs a weekly slot". The chair names who will bring it and on which day, and the item leaves the room. Watch for repetition. The same topic appearing three mornings running means either the weekly meeting is not doing its job or the daily meeting is being used to avoid a decision. Keep the weekly agenda separate and short as well. A weekly meeting that inherits everything the daily meeting refused becomes the new problem.
Night audit and month-end closing are weekly or monthly rhythms by nature; the daily meeting only needs to know whether the business day closed cleanly, which is the outcome of the night audit checklist: closing the hotel business day in order.
Which rules keep the meeting to fifteen minutes?
Start on time, stand up, read the numbers beforehand, and end every item with an owner and a date or with the words "log it". The rules matter more than the agenda, because the agenda is only as good as the chair's willingness to cut.
Start on time even when someone is missing, and never recap for latecomers. One recap teaches the whole team that the start time is negotiable. Stand, and keep chairs, coffee and screens out of the room. One printed sheet or one screen showing the sheet, nothing else. Numbers are read before the meeting. Anyone who has not read the sheet does not speak on it.
When discussion drifts into problem solving, the chair says "log it" and names two people to meet afterwards. The room is for decisions, not for repair work. End on time even if the agenda is unfinished. Unfinished items go to the log with an owner and a date, which is a better outcome than a nineteen-minute meeting that decided one thing. Review the format after a month, not after a week. Change one thing at a time: the block order, the sheet layout or the log fields, never all three.
The chair's three phrases
Watch outThree failure modes to watch for
Status reporting, where each head reads out what the sheet already says; problem solving in the room, where two people settle a maintenance question while nine people wait; and a log nobody reads back, where actions are recorded and never reviewed. Each has one fix: read the sheet beforehand, say "log it", and open the next meeting with open items.
What to do next
Tomorrow morning, put the day's numbers on one sheet, run the four blocks in the fixed order with a visible clock, and write every decision as one line with a named owner and a date. Do that for two weeks before changing anything, then delete from the sheet every line nobody ever spoke about and move to the weekly meeting every topic that appeared three days running. The meeting gets short not because you cut it, but because you stopped giving it work that belongs elsewhere.
Frequently asked questions
Should the daily hotel meeting be in the morning or at the shift handover?
Morning, before the arrival peak, because the decisions it takes are about today's selling and servicing. The shift handover is a separate, narrower exchange between the outgoing and incoming teams; it feeds the yesterday block but does not replace the meeting. If the hotel runs a large night operation, the handover notes are written, not presented.
What happens if the general manager cannot attend?
A named duty manager chairs with the same authority to assign owners and dates, and the log goes to the general manager the same morning. Cancelling the meeting because the chair is away teaches the team that it is the general manager's meeting rather than the hotel's. The one thing that does not transfer is the authority to approve spending, and items needing it are logged with the general manager as owner.
How long should the action log be kept?
Keep open items until they close, and keep closed items long enough to answer "when was this decided and by whom", for example to the end of the month. The log is a working record, not an archive; if a decision needs a permanent record, it belongs in the department's own documentation. Do not turn the log into a second reporting system.
Should each department head read out a report?
No. Reports are read before the meeting, and only exceptions are spoken. Reading a report aloud converts a decision meeting into a briefing and guarantees that it overruns. The one exception is a department that has something the sheet cannot show, such as an incident or a guest promise made overnight.
How is the daily meeting different from the front desk handover?
The handover moves operational detail between shifts inside one department; the daily meeting moves decisions between departments for one business day. The handover notes are an input to the yesterday block, not a substitute for it. Keeping the two separate stops the daily meeting from becoming a long recital of room moves and cash counts.
