What RNZ reported
On 12 November, RNZ reported that options for replacing New Zealand's 111 emergency call system had slipped. They were due to Police Minister Mark Mitchell by July 2026 and are now expected in February. The same story quotes a police report from earlier this year: "The fragility and governance around the 111 platform presents a fundamental risk to emergency response."
Two days later, RNZ interviewed Inspector Natasha Rodley, police's acting director for communications and dispatch. She described the system as both effective and fragile. She called the April 2026 target of a new system in 2027/28 aspirational. She also confirmed police hadn't yet looked overseas for cost estimates. RNZ notes that police have been working on a replacement for more than four years without a delivery date.
The weaknesses are well documented. A briefing to the minister about a year ago, covered in the 12 November story, listed these problems:
- the system takes voice calls only, with no text or video
- the legal framework is fragmented and outdated
- no single agency oversees the whole service
- the first point of contact is a telco, which the briefing called very uncommon internationally
Spark runs that front end. Its call centre triages each call and transfers it to police, fire or ambulance. Spark has said it supports a review that could move call answering to a public-service model.
A white paper from the National Emergency Communications Working Group of Australia and New Zealand, reported by RNZ in January, found the service still runs on a model set up in 1958. It handles about 2.8 million calls a year, and 2.5 million of those come from mobiles.
Why a stalled public project matters to private system owners
We think the 111 story is an extreme case of a problem that shows up in plenty of organisations. Several groups depend on one system, nobody owns it end to end, and a supplier runs the part customers touch. Police, fire and ambulance all rely on 111, yet none of them is responsible for all of it. Police set up a cross-agency group with MBIE and the telcos last year to restart the search for a replacement. According to RNZ, that group has so far agreed an initial problem definition and scope.
A group with shared interests but no single budget holder tends to stall at that stage. Agreeing what the problem is costs nobody anything. Deciding what to fund, what to drop and who carries the transition risk needs one person with authority over all three.
The missing cost estimate makes the problem worse. A minister can't rank a replacement against other spending without at least a rough price, and a board can't either. The January white paper coverage noted that an overhaul hasn't been funded and the government hasn't committed to one this term. A replacement with no estimate rarely makes it into a budget round, so the old platform keeps running.
The 111 story also shows how a system can become fragile when the people using it haven't changed but the traffic has. Calls from apps, alarms, smartwatches and cars now compete with people dialling for help. Police analysis found that 75 to 89 percent of Apple Crash Detection calls weren't emergencies. The white paper found that 111 queues calls in arrival order and can't prioritise during major disasters, which means a surge of automated alerts can block human callers.
Business systems face a smaller version of the same pressure. Service desks, order queues and customer inboxes were designed for requests typed by people. They now take a growing share of traffic from integrations, sensors and AI agents.
The last lesson concerns adjacent programmes. Next Generation Critical Communications has nearly $2 billion for emergency communications, including a $1.84 billion Public Safety Network. In April 2025 its director told RNZ that the 111 improvements investigators had asked for were neither in NGCC's scope nor funded. A large programme running beside a weak system can look like cover for it. Unless someone checks the scope documents, nobody finds the gap until it causes trouble.
What it means for NZ businesses directly
Some of this affects day-to-day operations. Employers with lone workers, remote sites, rural staff or monitored alarms are relying on a service that the minister's briefing described as fragile in big storms, harder to use for rural and disabled callers, and voice-only. Police describe even a 2027/28 replacement as aspirational. Health and safety plans should therefore be built around how 111 works now. They shouldn't count on text, video or better location handling arriving within the next few years.
Firms that make or sell devices that call 111 automatically, such as alarms, telematics or wearables, should expect the rules to change once a replacement is funded. The white paper recommended a new agency to take charge of 111 and work on legislative and regulatory change. Nothing has been decided yet, and no timetable has been published.
For most organisations the bigger value lies in checking their own legacy platforms against the same tests. A replacement that has sat at "problem definition" for years usually has an ownership problem more than a technology problem. Our digital transformation work starts from that point: who decides, what the replacement roughly costs, and what keeps the old system safe in the meantime.
Practical next steps
- Name one accountable owner for each shared system. Give that person authority over budget and scope, even if several teams use the platform. A steering group that advises the owner is fine. A steering group in place of an owner is how replacements stall.
- Price every replacement on your risk register. Write down a rough cost range now, even if it's wide. Anchoring a board decision on a range is far easier than on nothing, and the range can narrow as discovery work goes on.
- Measure machine-generated traffic. Work out what share of tickets, orders or messages in your core systems comes from integrations, monitoring tools and AI agents. Then decide how that traffic gets filtered or ranked so it can't crowd out people. Service management practices such as ITIL 4 give you a structure for setting priority rules and handling demand.
- Read the scope of the big programmes next to your weak systems. If a major ERP, network or cloud project sits beside a fragile platform, check in writing whether the fragile platform is in scope and funded. Don't assume it is.
- Treat a supplier-run front end as a governance decision. Where a vendor handles your first customer contact, review the transition and exit clauses, the performance data you receive, and who can change the triage rules.
- Check emergency procedures for lone and remote workers. Test them against what 111 can do today. Add backup ways to raise an alarm at sites with poor coverage, and record the decision in your health and safety plan.
Sources
- RNZ: Fragile 111 system poses fundamental risk - but replacement delayed again (12 November 2026)
- SafetyNews NZ: Fragile 111 system poses fundamental risk - but replacement delayed again (republished RNZ story)
- RNZ: 111 'solid', 'fragile', 'effective' and a safety risk - all at the same time (14 November 2026)
- B2B News: 111 system 'fragile' says police report, still no fix date (15 November 2026)
- RNZ: Pressure grows to fix 111 emergency call system with 1958 model still in use (28 January 2026)
- RNZ: Agency charged with emergency communications upgrade not funded for 111 changes (9 April 2025)
- IT Brief: Digital transformation tag page
Want to know what this means for your organisation? Our team in Auckland can show you your top three opportunities in a free 30 minute assessment.
Get my free assessment How we help