The turnaround schedule was locked a year ago. The scaffolding contractor, the crane plan, the catalyst delivery and the permit office are all booked. Then, ten days before mobilization, someone asks how 900 contractors are going to talk to each other, and whether the plant Wi-Fi can handle the permit tablets. Nobody has an answer, because nobody was asked.
This post is the backward timeline we use with refineries and chemical plants: what has to happen 16 weeks out, what has to happen 4 weeks out, and the checklist that tells you the network is ready before the first permit is pulled.
The short answer
Start about 16 weeks before the turnaround. That leaves time for a site assessment, network and radio design, device procurement (intrinsically safe devices can have long lead times), and staging and testing before mobilization, so the network is ready for peak headcount on day one.
Why Comms Planning Gets Left Late
Nobody decides to leave communications to the last minute. It happens because of how turnaround planning is organized.
- It has no line on the TAR plan. Scaffolding, cranes, firewatch, mechanical, electrical and permitting all have owners and milestones. Communications usually sits between site IT, operations and the contractors, so it belongs to no one until something breaks.
- The plant network seems fine. It is fine for 150 permanent staff. It was never sized for 600 extra people arriving at the same gate at 6am, each with a phone, and many with a tablet, a gas monitor or a body camera. Safety wearables and man-down alerts are only as good as the network under them, which is why connected worker safety belongs on a private network.
- Radios are treated as a box count. Ordering 300 handsets is easy. Planning talkgroups for 20 contractors across two shifts, without step-on during a hot-work window, is the hard part.
- The long-lead items are hidden. Intrinsically safe phones and tablets, licensed radio channels, IT security reviews and integrations with the permit system all take weeks. By the time anyone notices, the turnaround date cannot move.
The result is a scramble in week one: personal hotspots, borrowed radios, permit tablets that time out in the unit, and a safety supervisor calling the control room on a personal phone. We wrote about how that plays out in turnaround connectivity for oil & gas and chemical plants. This post is about preventing it.
The 16-Week Timeline
Work backward from the day contractors mobilize. The weeks below are counted before that date. On a large refinery turnaround with heavy integration work, add a few weeks at the front. On a small unit outage, you can compress the middle, but not the procurement step.
Weeks 16 to 14: Name the owner and set the requirements
Appoint one communications lead and put a comms line on the TAR plan with its own milestones. Pull the headcount curve, shift pattern, contractor list and work scope from the turnaround plan. Those four inputs size everything else: how many users at peak, how many talkgroups, which units and laydown areas need coverage, and which crews need intrinsically safe devices.
Weeks 14 to 12: Site assessment
Walk the site with the turnaround logistics plan in hand: process units, pipe racks, tank farms, laydown yards, the contractor village, the gate and badging area, and the control room. Measure what the existing Wi-Fi, carrier coverage and radio system actually deliver, and mark hazardous area classifications. A paid site survey and RF design at this stage gives you a documented baseline instead of a guess. We explain why that matters in paid site surveys vs. complimentary RF walkthroughs.
Weeks 12 to 10: Network and radio design
Design for peak headcount, not average. Decide coverage (where you need private 5G, industrial Wi-Fi or both), backhaul and failover, traffic segmentation, and the talkgroup plan. Decide how contractor radios and push-to-talk will bridge to the plant's existing radio system so operations and contractors can reach each other. Then submit the design to IT and OT security for review now, because approval is usually slower than the engineering. Keeping turnaround traffic isolated and segmented from the plant OT network makes that review much easier.
Weeks 10 to 8: Procurement
Order the long-lead items first: intrinsically safe phones and tablets, radios and accessories, SIMs, cameras and any mounting hardware for hazardous areas. Start spectrum or license paperwork where it applies. If you are renting instead of buying, reserve the fleet now. Rental fleets for turnaround season book up across the Gulf Coast at the same time yours does.
Weeks 8 to 6: Integrations and device setup
Connect the network to the systems the turnaround runs on: the digital permitting system, CMMS, badging and muster, and the plant radio bridge. Build the device management profiles: which apps each role gets, what is locked down, and how a lost device gets wiped. If no one owns that, read managing intrinsically safe devices before you receive the boxes.
Weeks 6 to 3: Staging and testing
Stage the equipment, enroll and label every device, and load the talkgroups. Then test where the critical calls happen: the bottom of a column, inside a vessel entry zone, under the pipe rack, at the far corner of the laydown yard. Run a dry-run of a permit sign-off and an emergency muster call over the new system. Fix the gaps while there is still time.
Weeks 3 to 1: Mobilization
Deploy the network and do a final coverage walk with the turnaround layout in place, because scaffolding and temporary structures change how signal travels. Set up device issue and return at badging, brief contractor leads on talkgroups and escalation, and confirm who answers the phone when something breaks on night shift.
Day one through demob
Run a daily network and device health check, watch capacity as headcount climbs to peak, and adjust coverage as work moves between units. At demob, collect and wipe every device, remove temporary equipment, and write down what to change for the next turnaround.
12-Point Readiness Checklist
Use this at the readiness review, typically three to four weeks before mobilization. If any item is still open, it has a named owner and a date.
- One named communications lead with a line and milestones on the TAR plan.
- Peak headcount and device count by shift, including contractors, cameras, gas monitors and wearables.
- Site assessment completed with coverage measured in every unit, laydown area and contractor village.
- Coverage design approved for peak load, with backhaul failover.
- IT and OT security sign-off on the design, segmentation and remote access.
- Talkgroup plan published by contractor, unit and shift, with an emergency channel everyone can reach.
- Radio bridge tested between contractor PTT and the plant radio system and control room.
- Intrinsically safe devices received, matched to the area classification where each crew works.
- Every device enrolled in device management, labeled and assigned to a role.
Integrations tested end to end
permits, CMMS, badging and muster.
- Field tests passed at critical locations, including a permit dry-run and an emergency call.
Support model confirmed
issue and return process, help desk hours, and on-site response for night shift.
Who Should Own the Plan
Ownership is the most common gap, and the easiest to fix. A working split looks like this:
Accountable: the turnaround manager
Communications readiness sits on the TAR plan and goes through the same readiness reviews as scaffolding and cranes. If it slips, it is a turnaround risk, not an IT ticket.
Responsible: one communications lead
A named person who runs the timeline above. This might be someone from site IT or OT, or the industrial wireless systems integrator operating the temporary network. What matters is that it is one person, not a committee.
Consulted: IT security, operations, safety and contractor leads
IT security approves the design, operations owns the plant radio system, safety sets the emergency comms requirements, and contractor leads confirm headcount and devices for their crews.
If the temporary network is outsourced, write the support model into the contract. There is a real difference between an operated deployment and dropped-off hardware when the radio bridge fails at 2am.
Common Mistakes
- Sizing for normal operations. The plant network handles today's load. Turnaround load is several times that, and it all arrives at shift change.
- Ordering intrinsically safe devices late. Certified devices and accessories can take weeks to months to arrive. A late order means crews work without them, or the wrong device ends up in the wrong zone.
- Testing in the parking lot. Coverage that works by the trailers can disappear inside a unit full of steel. Test where the work happens, after scaffolding is up if you can.
- Leaving the radio bridge to week one. If contractors cannot reach the control room on the same system, the emergency plan has a gap.
- Skipping the security review. A temporary network that IT has not approved gets shut down or isolated at the worst moment.
- No issue and return process. Devices without an owner go missing, and nobody can wipe what they cannot find.
- Forgetting demob. Equipment left on a pipe rack becomes next year's mystery device on the network.
How Clover IQ Supports Turnaround Communications
Clover IQ plans, deploys and operates temporary networks for turnarounds, from the first site assessment to demob.
Planning and design
A site survey, RF design and talkgroup plan built from your headcount curve, ready for your IT and OT security review.
Network on wheels
The Mobile Connectivity Unit brings its own power, backhaul, private 5G, Wi-Fi and on-prem push-to-talk, so the turnaround network does not depend on the plant network. Once it is positioned, it is typically live within about an hour.
Devices and support
Intrinsically safe devices enrolled and configured before they arrive, plus on-site support through peak. See turnaround infrastructure as a service, or the alerts we turn on in the first days in five alerts every turnaround site should be running by day two.
Questions from the Field
What is a turnaround (TAR)?
A turnaround is a planned shutdown of a process unit or a whole plant for inspection, maintenance, repairs, catalyst changes and project tie-ins that cannot be done while it is running. Refinery and chemical plant units typically go through one every few years. The work is compressed into a few weeks, because every day offline is lost production.
How much does headcount increase during a turnaround?
It often grows several times over. A plant that runs on 150 permanent staff can host 400 to 600 or more contractors during a turnaround, and large refinery turnarounds can bring in thousands. Most of them arrive at the same shift changes, which is why networks and radio systems sized for normal operations fail in the first week.
Turnaround vs shutdown vs outage: what is the difference?
The terms overlap, and the industry often groups them as STO (shutdowns, turnarounds and outages). Turnaround is common in refining and petrochemicals for planned maintenance events. Shutdown is a broader term and can be planned or unplanned. Outage is the usual term in power generation and utilities. The communications planning is the same for all three.
Straight Talk
Turnaround communications rarely fail because the technology is wrong. They fail because no one owned them until it was too late to order devices, get a design approved, or test in the unit. Sixteen weeks is not a lot of time. It is just enough, if someone starts the clock.
Book a 30-minute discovery call. Bring the turnaround date, the headcount curve and the unit list. We'll tell you where you are on the 16-week timeline and what to order first.



