At ten to midnight, a food manufacturer's IT team finds ransomware on a file server and isolates the site network. Two production lines keep running on their own controllers. Email, Microsoft Teams, the works order system and the site phones go at once. Sixty people are on nights, with nine contract fitters in the warehouse.
Alerting shift workers during a plant IT outage depends on three things prepared in advance: contact details held somewhere the outage can't reach, a short set of instructions already approved, and a way to see who has confirmed them.
Alerting shift workers during a plant IT outage only works if it was set up beforehand. The numbers sit outside the systems the incident takes down, the first instructions are written and approved already, and the shift manager can see who has acknowledged before relying on anyone acting.
What Is Alerting Shift Workers During A Plant IT Outage?
Alerting shift workers during a plant IT outage means getting one instruction to every person on site when the plant's normal internal channels are unavailable. The cause may be a cyber containment, a failed switch or a power event. The job is the same either way: reach each person, and know the message landed.
Most plants talk to their shift teams through the public address system, two-way radios, supervisors walking the floor, the works order system and email to the office. Several of those run over the site network. When the network goes, the shift manager is left with a mobile phone and whatever numbers happen to be in it.
Why Does A Plant Keep Producing And Stop Communicating?
A plant keeps producing and stops communicating because the machines and the message travel on different systems. Programmable logic controllers (PLCs) run the line locally and carry on. The works order system, email, Microsoft Teams, internet phones and the digital muster board sit on the site network, and they go when it's isolated.
That split is what catches people out. The line is still making product. The operators are still at their stations. And the health, safety and environment (HSE) manager has no way of telling two hundred people anything at the same time. So alerting shift workers during a plant IT outage turns out to be a planning job rather than a technology one.
The National Cyber Security Centre (NCSC) guidance on effective communications in a cyber incident, published in October 2024, says that during a cyber incident an organisation's usual communications channels may not be available, and that organisations may need to establish alternative ways to keep in touch with staff, stakeholders and customers.
Who Has To Be Reached On A Plant Floor, And How?
Five groups have to be reached on a plant floor, and no single channel covers them: employees on shift, contract crews working on site, agency and temporary staff, off-site duty managers, and hauliers or visitors at the gate. Each group sits in a different system. Some sit in none.
The table maps those five groups against the channel that usually carries the message, so alerting shift workers during a plant IT outage can be planned group by group instead of as one broadcast.
| Group | Usually Reached By | During A Plant IT Outage | What Their First Message Must Contain |
|---|---|---|---|
| Employees on shift | Public address, supervisors, the shift briefing | The public address system may run over the site network, and a supervisor covers one area each | What to do with the line, and where to go |
| Contract crews on site | The supervisor who booked them in | Rarely on any company system or distribution list | Stop the job or carry on, and who to report to |
| Agency and temporary staff | The agency, a paper sign-in sheet | Numbers are often held by the agency rather than the plant | The same instruction as employees, in plain terms |
| Off-site duty managers and HSE | Email, Microsoft Teams, a call from the gatehouse | Email and Teams unavailable, mobile still works | What has happened, and that they are needed |
| Hauliers and visitors at the gate | The gatehouse phone, the barrier and its screens | Gatehouse systems may be down, and a queue builds at the gate | Whether to enter, wait or turn around |
Two rows are the ones most often missed. Contract crews and agency staff are on site, covered by the plant's emergency procedures, and usually absent from whatever distribution list the alert goes to.
Regulation 8 of the Management of Health and Safety at Work Regulations 1999 requires an employer to establish appropriate procedures for serious and imminent danger, and to nominate a sufficient number of competent persons to implement those procedures. Naming those people, and giving them a way to send a message that doesn't run on the site network, is the practical version of that duty. This is orientation rather than legal advice, and the position is as at October 2026.
The NCSC's advice on developing an incident response plan makes the same point about the list itself: hold at least two contact methods and two or more people for each key contact, because somebody will be unavailable on the night.
What Should The First Message To A Shift Say?
The first message to a shift should say what has happened in one sentence, what to do now, what not to do, how to confirm receipt and when the next update comes. It shouldn't guess at the cause or at a restoration time. Anything said early may have to be withdrawn.
Nobody writes that well at midnight with a radio in one hand. The NCSC recommends drafting pre-approved templates in advance, and the version a plant needs is short enough to read on a phone screen in a noisy building. This is the part of alerting shift workers during a plant IT outage that gets left to the night itself most often.
Three standing instructions cover almost everything a shift manager needs in the first ten minutes:
- Hold and make safe. Bring the line to a controlled stop, stay at your station, wait for your supervisor
- Continue with caution. Keep running, record jobs on paper, report anything unusual to the shift manager
- Evacuate to muster. Leave by your nearest route and report to your muster point for the roll call
The First Hour, Step By Step
Here's the opening scene again, with the preparation done.
- 23:50. IT isolates the site network and tells the duty shift manager.
- 23:55. The shift manager picks the agreed "continue with caution" message and sends it to everyone on site, the nine contract fitters included, by text and voice call.
- 00:04. Fifty-one of sixty-nine people have acknowledged. Eighteen haven't.
- 00:08. Supervisors get the list of eighteen names and walk their areas.
- 00:30. A second message gives the next update time and confirms that jobs are being recorded on paper.
- Next morning. The record shows who was told what, and when, ready for the handover and the incident review.
How Does Crises Control Help Plants Reach People On Shift?
Crises Control helps plants reach people on shift through Ping, its Emergency Communication Software, which runs in the cloud rather than on the plant's own network. One message goes to everyone selected by SMS, voice call, push notification, email, Microsoft Teams and web alert, and Ping records who received it and who acknowledged it.
Ping can deliver across every configured channel at once, or cascade through them until a recipient acknowledges, without an administrator chasing in between. It timestamps each delivery and acknowledgement, and it can target a group such as one site, a department or an on-call rota. For alerting shift workers during a plant IT outage, text and voice are the channels that still arrive once email and Teams have gone.
As Manufacturing Incident Management Software, the platform also carries the incident itself: a shared workspace the response works from, two-way acknowledgement that confirms who is safe and who needs help, and an automatically logged timeline for the investigation afterwards. Incident Task Management Software picks up the jobs that come out of the response, once the first instruction has landed.
Some things stay with the plant. The platform only reaches the numbers it holds, so somebody has to keep the shift, contractor and agency lists current, and on a site with rotating crews that's weekly work. Mobile signal inside a steel-framed building is a real constraint, so the public address system, radios and a supervisor walk-round stay in the plan. The people who send have to be able to sign in without the site network, which is worth testing this month rather than during an incident. And the shift manager still decides what the instruction says.
Plant Floor Alerting Checklist
This turns alerting shift workers during a plant IT outage into eight things an operations or HSE manager can check this week.
- Mobile numbers for every shift worker, contractor and agency worker on site are held outside the plant network and refreshed on a set day each week.
- Three standing instructions exist and are approved by the operations director: hold and make safe, continue with caution, evacuate to muster.
- The competent persons nominated under regulation 8 are named by role, with a deputy on every shift.
- At least two people on each shift can send an alert, and neither of them needs the site network to sign in.
- Every instruction asks for an acknowledgement, and one named person chases whoever doesn't reply.
- Areas with poor mobile signal are listed, with radio or a supervisor walk-round named as the fallback for each.
- The gatehouse has a way to hold or turn away hauliers when its own systems are down.
- The whole thing has been run once on a night shift, with email, Microsoft Teams and the works order system treated as unavailable.
The Line Doesn't Know The Network Has Gone
A containment decision at ten to midnight can leave a plant producing normally and unable to tell the people inside it anything at all. The controllers don't care that the network has gone. Sixty people on nights, nine contract fitters in the warehouse and a queue building at the gate all depend on a message that suddenly has nowhere to travel.
Closing that gap costs very little, and nearly all of the work happens in advance. It takes contact details the incident can't reach, three instructions written while nobody is under pressure, and a channel that shows who has confirmed them.
An operations or HSE manager can test it on a single night shift. Treat email, Microsoft Teams and the works order system as gone, then try to get one instruction to every person on site, contract crews included. If every acknowledgement comes back inside the time the plan allows, the plant has its answer on alerting shift workers during a plant IT outage. If it doesn't, the checklist above shows where it broke. For the next layer, read our ten questions a plant manager should ask before the next emergency, or see how Ping handles acknowledgement and escalation.
Frequently Asked Questions
What is out-of-band communication in a manufacturing plant?
Out-of-band communication in a manufacturing plant is any way of reaching people that doesn't travel over the plant's own network or the systems that depend on it. Text messages and voice calls to mobile phones, sent from a separately hosted service, are the common example, and two-way radio is another. It matters because it still works after the site network has been isolated.
How do you contact contractors and agency staff during an incident?
Contractors and agency staff are contacted during an incident by holding their mobile numbers on the plant's own alerting list, collected at induction, rather than going through the agency or the contractor's office. A worker who is on site is covered by the plant's emergency procedures whether or not they're on the payroll. Refresh the list on the same day each week, because the crews change.
Is a public address system enough to alert a plant?
A public address system isn't enough on its own. It reaches only the people inside its coverage who are able to hear it, which leaves out the yard, the gatehouse, remote plant rooms and anyone in hearing protection beside a running line. It also gives no record of who received the message, so the shift manager can't tell who is still unaware.
What should a plant do if mobile signal is poor inside the building?
A plant with poor mobile signal should list the affected areas and give each one a named fallback, usually two-way radio, a supervisor walk-round or a set check-in time. The fallback belongs in the plan by area, not left to judgement on the night. Site wi-fi can carry push notifications where it survives the incident, though it often runs on the same network that has gone.
How does Crises Control help a plant reach people on shift?
Crises Control helps with alerting shift workers during a plant IT outage through Ping, which runs in the cloud, separate from the plant's own network. Ping sends one message by text, voice call, push notification and the other configured channels, and records every delivery and acknowledgement with a timestamp. The manufacturing incident management page shows how the platform is used across sites and shifts.
This article was drafted with AI assistance and reviewed by the Crises Control team. Featured image: AI-generated.
