What Belongs in a Hotel Morning Brief (And What Doesn't)

The morning brief has one job: get the team oriented fast. What's the occupancy picture, where's the pickup heading, is the rate position where it should be, and what needs attention today. That's it. Most of the morning briefs I see are trying to do more than that — and the extra weight makes the whole thing slower to read, slower to build, and harder to act on.

Start with what the brief is for

Before deciding what to include, it's worth being clear about who reads the brief and what decision they're making with it. A revenue manager uses it to decide whether any rate adjustments are needed and which dates need closer attention. An ops director uses it to understand where the portfolio stands relative to expectations. An owner uses it to know whether anything is off enough to warrant a conversation.

None of those use cases require a 40-column spreadsheet. They require a clear view of a small number of things. The brief is at its best when someone can read it in under three minutes and know exactly what, if anything, needs their attention today.

What belongs — and what doesn't

A representative brief layout

Here's what a clean, functional hotel morning brief looks like for a single property. Each row is a date. The columns answer: where are we, how are we moving, are we priced right, are we on target, and what needs attention.

Seven columns. Everything someone needs to start the morning. Monday the 28th gets flagged because it's below comp on rate and well below occupancy target — that's a decision date. The rest either look fine or are worth a closer look. The team can read this in 90 seconds.

The exceptions column is the most important one

If there's one thing that separates a useful brief from one that just reports numbers, it's a well-designed exceptions layer. The team doesn't need to read every row carefully if the brief tells them which rows actually require attention.

Exception flags can be as simple as a conditional formula: if occupancy is below X% for a date within Y days and pickup over the last 7 days is under Z rooms, flag it. If the rate gap vs. comp median is wider than $20, flag it. The thresholds are configurable and should be set based on how the property normally operates — not generic defaults.

The goal is that on any given morning, a revenue manager looks at the exceptions column first. If everything is green, the review takes two minutes. If there are flags, those dates get attention. That's the workflow the brief is designed to support.

Format follows audience, not preference

There's no universal right format for a morning brief. The right format is the one the team actually opens and uses. For some teams, that's a Google Sheet shared via a link every morning. For others, it's a PDF in a group email. For others, it's a tab in an internal dashboard that's always open on the ops manager's second monitor.

What I'd push back on is the assumption that a fancier format is a better format. A clean, well-structured Google Sheet that shows up reliably at 7:30am beats a beautifully designed dashboard that requires three clicks and a login. The content matters more than the container.

One more thing: the notes column is load-bearing

Every brief should have a notes or context column, and it should be easy to update. Rate strategy decisions, group blocks coming off market, a local event driving demand on a specific date — this context doesn't fit in a number, but it completely changes how the team interprets the numbers next to it.

When the brief is automated, the notes column is the one place where a human still adds something every morning. That's fine. The goal was never to remove all human judgment from the morning. It was to remove all the mechanical assembly so the human judgment can focus on what matters.