Shift Briefing
A short, structured start-of-shift message telling the incoming team what matters today, before the shift rather than after it.
A shift briefing is what the incoming team is told before they start: today's priorities, anything unusual, who is covering what. It is the forward-looking twin of a handover. A handover reports what happened; a briefing sets what is about to.
Why the two are not the same thing
Teams that run a good handover often assume it covers this, and it does not. A handover is written by somebody leaving, about the shift behind them, and it is naturally a list of problems. A briefing is written by somebody planning, about the shift ahead, and it carries intent: the delivery due at eleven, the two people short on Saturday, the promotion starting today. Reading yesterday's problems tells you almost nothing about either.
- What is different about today compared with a normal day
- Anything time-bound: deliveries, visits, deadlines
- Who is covering an unusual position or an extra site
- One thing to prioritise if the shift gets busy
Keeping it read rather than merely sent
The failure mode is a briefing nobody opens, and it is almost always caused by volume. A daily message that is mostly routine trains people to skim, and once skimming is the habit the one genuinely important briefing goes the same way. Send fewer, make each one specific, and put it where people already look at their shift rather than in a channel they have muted.
“A briefing sent to everybody, every day, about nothing in particular, is how a team learns to ignore the one that mattered.”
How Formclock handles this: team messaging.
Explore team messaging