Council amalgamation is coming. The government has given territorial authorities until 9 August 2026 to submit voluntary reorganisation proposals, with new structures in place before the 2028 local elections. The governance debate is loud. The operational detail is quieter — and that's exactly where the risk lives.
Venue hire and facility management sits squarely in that operational blind spot. It's not glamorous. It rarely makes the agenda on an executive strategy day. But when it breaks during a merger, the community feels it immediately and they don't forgive it easily.
This article is for facilities and venue hire leads, COOs, CIOs and CEOs who want to get ahead of the problem rather than clean it up afterwards.
SpacetoCo is a cloud-based venue and asset booking platform used by councils across Aotearoa and Australia to manage, publish, and reconcile community facility bookings in one system. It's trusted by more than 70 councils and processes over 540,000 bookings annually.
Let's be honest about where most councils actually are in 2026. Many have moved past paper forms, and they're running enterprise systems. They show availability. They display pricing. Progress, right?
Sort of. The problem is these platforms are siloed by design. Each council instance runs independently. You can't surface facilities from a neighbouring council. Community groups that operate across boundaries — and there are a lot of them — have to navigate completely separate booking portals, separate login credentials, separate payment systems. Many still require hirers to be vetted before a booking is confirmed. "Allow 3–5 working days for your booking to be processed." In 2026, nobody should need a PDF tutorial to book a community hall, but here we are.
Now merge two councils running different instances of different platforms. You don't just inherit two systems, you inherit two sets of pricing logic, two finance reconciliation workflows, two approaches to community leases, two databases of regular hirers, and two sets of staff who've built their entire process around the way their system works. That's not a technical problem you solve on merger day. It's a slow-burn operational headache that compounds for years if you don't address it early.
The community, meanwhile, doesn't care. They just want to book the hall.
The government has been clear about what reorganisation proposals need to demonstrate. They should be realistic, simple, efficient, fairly represent communities, and support the new planning system. That's not just a checklist for governance structures — it's a useful lens for every operational decision that flows from amalgamation, including how you manage your community facilities.
Run those criteria against your current booking setup:
Realistic — Can your current system actually scale across a merged council without a 12-month IT project? Most venue booking integrations take that long, minimum. If you're already in the middle of a restructure, that timeline isn't realistic.
Simple — Is your booking experience genuinely simple for the community? Or does it require a login, a vetting process, a wait, and a follow-up call? Simple means a resident books and pays in minutes, from their phone, at 10pm.
Efficient — How much admin time goes into manual data entry, bond processing, invoice chasing, and credit note reconciliation? If the answer is "a lot," that's not efficient — and a merger will make it worse before it gets better.
Fairly represents communities — Are all your facilities actually discoverable? Community-leased halls, rural venues, and facilities managed by third parties under peppercorn arrangements are often invisible to the public because they sit outside the council's main booking system. Fair representation means every community asset is findable.
Supports the new planning system — Decision-making under the new RMA framework will require better data. Utilisation rates, revenue trends, demand patterns across a region — this is the kind of insight that informs infrastructure investment and planning. You can't generate it from two siloed systems.
The strategic opportunity in amalgamation — if you approach it deliberately — is to build something genuinely better than what either council had before. Not just a merged version of two old systems, but a single, joined-up bookable ecosystem that serves the whole region.
What does that actually look like? A resident anywhere in the new combined territory can search for available facilities across all council-owned and community-operated venues in one place. One booking experience. One payment process. No login required to check availability. No "allow 3–5 days" message. Just: here's what's available, here's the price, here it is confirmed.
That's not just operationally tidy. For a merged council trying to demonstrate its value to a community that was sceptical about amalgamation in the first place, it's a tangible, visible win. Facilities that were previously invisible get discovered. Utilisation goes up. Revenue follows. And the community's first experience of the new council is a positive one.
Helpful Resource: Building a bookable ecosystem for your community
Speed matters here because amalgamation timelines are fixed. The answer isn't the most sophisticated solution — it's the one that deploys fast, doesn't require a lengthy IT project, works across council boundaries from day one, and keeps finance records clean throughout.
A few things to look for:
Cross-boundary architecture. The platform needs to support a multi-council structure natively — not through a workaround or a custom integration. Booking teams managing different facility types (libraries, recreation centres, parks, arts venues) should be able to operate independently while the community sees one joined-up experience.
Community lease support. This is the one that catches most councils out. Peppercorn-lease and community-operated venues need to sit alongside council-owned assets in the same discoverable ecosystem. The community operator manages their own space; the data flows back to council; the resident sees one seamless service. Most platforms can't do this. It's worth asking specifically.
Finance compatibility without a project. Reconciliation with OneCouncil and other council finance platforms should happen through live reporting and scheduled exports — not a six-month integration build. Your finance team is already stretched. Don't give them a new manual process.
Weeks, not months, to go live. A structured three-phase rollout — setup, migrating existing regular hirers, and a hypercare period post-launch — should get a council live in 8–12 weeks. That's achievable within amalgamation timelines.
Real reporting, accessible to everyone. Utilisation data, revenue trends, booking patterns by facility type and geography — this should be available in real time, not buried in a custom report request. Decision-makers in a newly merged council need this to make good infrastructure choices quickly.
Councils using SpacetoCo have reclaimed up to 80% of the time previously spent on manual booking administration. Hastings District Council runs libraries, community halls, sports and recreation spaces, open spaces and campgrounds through a single bookable ecosystem. Taupō District Council moved 10 community facilities off manual processes and saw reduced administration, simplified cashflow, and increased bookings. Two neighbouring councils in Hawkes Bay have now selected SpacetoCo — laying the groundwork for a joined-up regional booking experience across their district ahead of any structural change.
Helpful Resource: How councils are using SpacetoCo creatively across all their asset types
Amalgamation creates a narrow window to get operational infrastructure right before the structural chaos peaks. The councils that use that window well — that arrive at their new merged entity with clean, tested systems, a single booking experience for the community, and real data to make decisions with — will have a genuine head start.
The ones that wait will be reconciling two booking backlogs, managing two finance workflows, and explaining to a new combined council why the hall still can't be booked online without calling someone first.
That's a solvable problem. But it's a lot easier to solve before the merger than during it.
Helpful Resource: Local Government New Zealand — Resources on council reform
What happens to existing venue bookings when two councils merge?
Without a unified platform, existing bookings typically sit in two separate systems with different data structures, pricing logic, and finance workflows. Regular hirers may not know which system their bookings are in, and staff spend significant time manually reconciling records. The cleanest approach is to migrate both councils onto a single platform before or during the transition, with proper data migration and hirer communication support built into the rollout.
Can councils run a single booking system across merged regions without a long IT project?
Yes — if the platform is designed for multi-council architecture from the ground up. Purpose-built local government booking platforms can typically deploy in 8–12 weeks without complex IT integration. The key questions to ask are: does it support multiple booking teams managing different facility types independently? Does it connect to your existing finance system through reporting exports rather than a custom build? And does it handle community-leased venues natively?
How do community-leased venues fit into a merged council's booking ecosystem?
This is one of the most overlooked challenges in amalgamation. Community-operated venues on peppercorn leases — sports clubs, arts centres, rural halls — are often managed on entirely separate systems or spreadsheets. In a merger, you can inherit a patchwork of these arrangements across two councils. A platform that allows community operators to manage their own spaces while sharing data back to council, and that presents all venues — council-owned and community-operated — in a single discoverable ecosystem, eliminates this complexity.
What reporting should a merged council expect from its booking platform?
At minimum: real-time utilisation data by facility and geography, revenue trends, booking patterns by hirer type (casual, regular, commercial, community group), and automated reconciliation exports compatible with council finance systems. This data is essential for making smart infrastructure investment decisions under the new planning framework — and it shouldn't require a custom report request every time.
How does a unified booking platform improve the community experience after amalgamation?
Residents in a merged region gain a single place to find and book any facility across the combined territory — without needing to know which council owns what, or navigate multiple portals. Facilities that were previously hard to find become discoverable through search engines and AI tools. Booking is self-service, available 24/7, with instant confirmation and no waiting period. For a community that may have been sceptical about amalgamation, that's a visible, tangible service improvement delivered fast.
Talk to the SpacetoCo team — we've worked with councils through exactly this kind of transition and can give you a straight answer on what's realistic.