7 Challenges of Multi-Site IT Rollouts (and How to Fix Them)

Every multi-site IT rollout hits the same seven walls. After 25 years of deployments across Australia and New Zealand, we can name them before the kickoff meeting ends. Here they are, with the fixes.

1. No two sites match

The "standard store" doesn't exist. Different cabling eras, different power, different landlords, different back rooms. Plans built on head-office assumptions die at site 40.

Fix: audit every site first and turn findings into per-site work packages. Boring, unfashionable, decisive.

2. Freight and labour miss each other

The engineer arrives; the kit is at a depot 40 km away. Or the kit sits in a stockroom for three weeks growing coffee rings. Every mismatch is money spent installing nothing.

Fix: one schedule that books freight and crew as a pair, with delivery confirmed before travel starts.

3. Devices arrive unready

Site crews configuring devices from scratch turn a 90-minute install into a four-hour one, with variance to match.

Fix: central staging. Image, configure, kit and label per site before dispatch. Integration centres exist for this.

4. The business keeps trading

Stores, branches and clinics won't close for your project. Install windows are nights, pre-opens and negotiated gaps.

Fix: playbooks timed to fit the window, plus a rehearsed rollback so morning trade never depends on last night going perfectly.

5. Scope drifts sideways

"While you're there, can you also..." Fifty sites in, the crews are doing undocumented favours and the schedule quietly dies.

Fix: a change process with a price. Extras are welcome, scoped and billed, not absorbed until the program collapses.

6. Exceptions multiply

Site 47's problem becomes site 52's and 61's because nobody closed the loop. Weeks later there's a backlog of half-done sites nobody owns.

Fix: daily exception reporting with named owners and response clocks, and a cleanup wave planned from day one.

7. The last 5 per cent never finishes

Rollouts decay at the edge: deferred sites, access failures, franchisee no-shows. Programs stall at 95 per cent and stay there for a year.

Fix: treat 100 per cent as the definition of done. Escalation paths for stubborn sites, and a formal close-out gate that forces the tail.

The pattern behind all seven

Each challenge is a coordination failure, not a technical one. That is why the fix is always process: audits, staging, playbooks, governance. Our complete deployment guide walks the full method end to end.

Facing a rollout with a few of these already showing? Speak to an expert.