Why the night shift is always last to know
It is not carelessness. It is arithmetic. Decisions are made in office hours, the communication is drafted in office hours, and it goes out when it is ready, which is usually mid-afternoon. From then on, each shift gets it as it clocks on.
- Days get it fresh, with the supervisor standing there to be asked.
- Afters get it second hand, relayed by whoever is going home.
- Nights get it third hand, with the offices shut and nobody to ask.
- Anybody off that day does not get it for two or three days, if somebody remembers.
The result is predictable: the part of the workforce that works nights and weekends becomes certain that nobody tells them anything. And that certainty is what turns up in engagement surveys as 'poor communication', when what is actually missing is timing.
Handover is a channel, and should be treated as one
In most plants, the real internal communication channel is the shift changeover: fifteen minutes in which the people going home tell the people coming in what has happened. It works very well for operational things and very badly for everything else.
It works for operational things because the outgoing shift knows what the incoming shift needs. It fails for institutional things for three reasons: it is told from memory, it is told with the teller's opinion attached, and by the third handover nothing of the original message is left.
Writing for somebody who will read it eight hours later
An announcement in a shift business is an asynchronous text, like a letter. The person reading it has nobody to ask and cannot wait until tomorrow to act. That forces you to write differently.
01
Absolute dates, never relative ones
'Tomorrow' and 'this week' do not mean the same thing at seven in the morning as they do at eleven at night. Write 'from 6am on Thursday the 12th'.
02
Who it affects, in the first line
Anybody unaffected stops reading and costs you no attention for the next notice. 'Line 2 and maintenance only' saves more than any clever headline.
03
What to do, in the imperative
If the notice does not end in a specific action, it is not a notice, it is a bulletin. And if there is no action, say that too: 'nothing to do, this is for information'.
04
Who to ask at three in the morning
A name and an extension, or the shift manager on call. Without this, doubts get resolved by asking a mate, which is how a procedure gets bent out of shape.
Four publishing rules that fix half the problem
- Publish before the day's first handover, not when the text is perfect. A correct notice at 5.30am is worth more than a flawless one at 4pm.
- Always publish in the same place. If it is the noticeboard one month, the group chat the next and the payslip the month after, nobody builds the habit of looking.
- Segment properly. If the notice is about line 2, do not send it to the other three: people learn very quickly to ignore a channel that sends them things that are not theirs.
- Check by shift, not overall. Night shift coverage is a separate number, and it is the one that tells you whether the problem is solved.
The fourth is the hard one and the one that changes the most. While coverage is only looked at overall, a site with a small night shift can sit outside the loop for months without setting off any alarm.
Weekends, bank holidays and time off
The easier it becomes for a notice to reach somebody's phone, the more important it is to write down when it is expected to be read. The UK has no statutory right to disconnect, so nothing here is settled for you: if you do not write it down, every manager interprets it their own way and the conversation ends up with the reps.
Set out daily and weekly rest: an uninterrupted rest period of not less than eleven hours in each 24-hour period, and an uninterrupted rest period of not less than 24 hours in each seven-day period, or 48 hours in each fourteen-day period.
Requires the written statement of employment particulars to set out the terms relating to hours of work, including the days of the week the worker is required to work and whether those hours or days may vary.
- Whether people are expected to read announcements on shift or off it. This is the sentence you have to write, and it is not a sentence about the tool: it is your policy.
- What happens for somebody who has a long weekend off and comes back to eighteen unread posts. Usually the important things get pinned to the top and the rest is treated as read.
- What genuinely counts as urgent, and which route is used when it is. Almost always the shift manager's phone, and it is fine for that to stay the case.
- Who can publish at the weekend. If it is the duty managers, give it to them in writing and with a rule attached.
As with the rest of these guides: this is not legal advice. Your company's policy on out-of-hours contact is for your employment solicitor and your representatives to settle between them, and what is here is the list of the things that usually get left unwritten.
Three concrete cases and how they get handled
01
Unplanned line stoppage
Publish as soon as you know, segmented to the affected plant only, saying from when and until when and what the people on that line do in the meantime. Update the same post rather than putting out three separate notices: somebody clocking on at ten at night needs to find the current state, not the history.
02
Rota change
A fixed publishing date every month, the 20th say, always in the same place. What turns this into the most-read content in the company is the regularity: if people know it is there on the 20th, they go in on the 20th.
03
A change to a safety procedure
Publishing is not enough here: you need a record that it reached every person in the affected role. This is the case where a named read receipt is justified, and it is worth explaining why before you switch it on.