Knowledge base
What goes in a daily briefing.
At Inge de Bruijn Zwembad, a daily briefing lands in management's inbox every morning at 07:00. This article covers what's in it, in what order, and above all what doesn't belong there. No theory, just the structure of a briefing that runs every day.
The day starts with deciding, not with gathering.
Without a briefing, the morning starts with logging in. Open the register system for yesterday's revenue, pull up the schedule, scan the inbox, maybe check one more portal for energy or visitors. By the time you've seen it all, the first hour is gone and you haven't decided anything yet.
A daily briefing flips that around. One message, every morning at a set time, with everything you need to steer the day. At Inge de Bruijn Zwembad that's 07:00, well before the first visitor walks in. The format hardly matters, an email works fine. The content and the order make the difference, and that's where most briefings go wrong.
Five parts, in this order.
The order is half the value. Whatever calls for a decision goes at the top, whatever only reassures goes at the bottom. That way, on a quiet day the recipient reads only the first line, and on a busy day exactly what's going on.
- 1. ExceptionsEverything that went differently than expected, with one line of explanation per item. Revenue well below expectations, an outage, a payment that didn't go through. This goes at the top, because this is where today's work is.
- 2. Yesterday in numbersRevenue, visitors or occupancy, always next to what you expected. A number on its own says nothing. €4,100 is only good or bad news next to the €3,800 you expected for that day. Without a comparison, a number is decoration.
- 3. Open actionsWhat's still pending from earlier days and who it's waiting on. This isn't about blame. An action that never comes back up quietly slides off the pile.
- 4. Customer signalsReviews waiting for approval, questions the AI assistant had to pass on, a complaint that came in. A small problem you see today doesn't turn into a big problem next week.
- 5. Checked overnightWhat the monitoring checked overnight and whether everything was green. Usually this is one line. If anything was red, it isn't here. It's at the top, with the exceptions.
A briefing isn't a report, it's a decision list.
The biggest trap is completeness. A briefing that mentions everything there is to mention turns into a report, and reports get skipped. The core rule is that anything that isn't an action or an exception belongs at the bottom or not in the briefing at all. Whoever writes the briefing, or the system that puts it together, has to be able to answer one question for every line. Does the recipient need to do something with this today?
- Every line is a decision or an exception, the rest is an attachment
- Numbers always sit next to an expectation or a benchmark, never on their own
- An exception gets an explanation, a normal day gets no words
- The briefing arrives at the same time every day, even when everything is green
- On a quiet day the briefing is short, and that's a feature
- Anything that sits for three days without action deserves a conversation instead of a line
The reading test is simple. If the briefing takes more than three minutes, there's too much in it. After reading, the recipient should know what needs to happen today, not everything that happened yesterday.
How it runs in practice.
The structure above comes straight from the daily briefing I built for Inge de Bruijn Zwembad. It puts itself together every morning from the connected systems (register, schedule, energy, reviews and the overnight checks). You can see what that looks like in the case study on reporting and monitoring.
The line about last night comes from The Night Shift, automated checks that keep running overnight so the briefing can report in the morning whether everything is intact. A briefing without that monitoring layer only tells you about yesterday, not whether your systems are still up and running today.
What would be in your briefing tomorrow at 07:00?
In the free process review I look at which systems you have now and which briefing could come out of them as soon as tomorrow. Half an hour, an honest answer, and three concrete opportunities on paper to take with you.