Te Au Reka goes live Monday: lessons from a staged court rollout

By DataForge team21 November 20265 min read

The Ministry of Justice starts its delayed Te Au Reka court system in Canterbury on 23 November. Here's what NZ firms replacing core systems can copy.

What goes live on Monday

On Monday 23 November, the Ministry of Justice switches on the first part of Te Au Reka, its new court case management system. The first users are in the Family Court at Christchurch and Ashburton. A Law News preview published on 20 November calls the launch a limited soft launch, for judicial and registry use only. The Lawyer Magazine reports that registry staff will file all new Family Court cases in Te Au Reka and judges will decide those cases in the new system. Existing cases stay in the old case management system. The Ministry's Te Au Reka page sets out the next steps. The courts portal for lawyers reaches the South Island from March 2027, the Lower North Island and Central regions in April 2027, and the Northern region in May 2027.

Te Au Reka replaces a court administration process that still runs largely on paper. DXC Technology signed the contract in August 2023 and is building the system on Microsoft products, according to Law News. Justice Secretary Andrew Kibblewhite told a select committee that when he arrived, the most significant courts technology he'd seen in 40 years was the post-it note.

How the programme got here

The Family Court launch was originally due in mid-2026. Law News's September reporting on Official Information Act documents shows the Ministry judged that date unachievable in June 2025 and moved the project to red status. In February 2025 the Ministry had already considered scrapping Te Au Reka. Officials kept going to hold the confidence of the judiciary and the legal profession. When the contract was signed, Kibblewhite told Parliament the budget was roughly $139 million of capital plus $30 million of operating spend. A select committee review this year showed costs up by about 15%. The Ministry redacted every overall budget figure in its OIA response, including figures it had published before. The total cost to taxpayers hasn't been published.

The documents list causes that anyone who has run a large system replacement will recognise. DXC found the solution more complex than it expected, and vendor costs rose as a result. DXC also underestimated how hard staff training would be, so the Ministry brought training in-house and needed a larger internal team. The Ministry added a commercial risk that time-and-materials estimates could prove inaccurate. A March 2026 independent quality assurance review raised concerns about an insufficient integrated plan and an unclear critical path, though the same review noted genuine progress. Kibblewhite wanted a September 2026 launch, partly because of the election period, and the QA reviewers warned that going early could produce poor outcomes. The Ministry chose November.

Why the launch design deserves attention

Leave the cost overrun aside and the structure of Monday's launch reflects sound practice. Christchurch and Ashburton give the Ministry real caseloads without exposing every Family Court registry to early defects. Victoria McLaughlin, the Ministry's Deputy Secretary for Te Au Reka, said the controlled internal launch would let the team refine both the system and its supporting processes before the wider release (Law News). Her reference to supporting processes matters. In business system rollouts, most go-live trouble traces back to forms, handoffs and exception handling that nobody redesigned.

Sequencing users is the second sound choice. Registry staff and judges work in Te Au Reka for about four months before lawyers and self-represented litigants arrive through the portal. Defects that internal staff find do far less reputational damage than defects that the public finds. Filing only new cases in the new system also avoids a large data migration on day one. The cost of that choice is a stretch of dual running, where staff work across two systems and reports have to draw on both until the old cases close.

The contingency also has a written trigger. In April the Ministry said that if a large critical issue couldn't be resolved by November, registry, judicial and portal functions would all move to March 2027 (Law News, April 2026). Four months of float with a stated condition for using the float gives everyone a shared basis for deciding whether to slip. Programmes without one tend to move the date only after missing it.

What NZ businesses should take from Te Au Reka

Most NZ organisations replacing an ERP, practice management platform or line-of-business system will spend a fraction of $170 million. The pressures on Te Au Reka still apply to smaller projects. A vendor's complexity estimate changes once the vendor sees how your processes actually run. Training effort gets underestimated, and whoever owns training ends up needing more people. Executives want a go-live that fits an outside calendar such as financial year end, a board cycle or peak season. The independent reviewer is the person paid to push back on that date, and the Ministry's papers show what happens when the reviewer's warning and the preferred date collide.

The benefits case deserves the same scrutiny. Kibblewhite has linked Te Au Reka to efficiencies that could shrink the Ministry, and in June he said: "The ministry will be smaller in the future, I'm sure of that." When a business case depends on headcount reductions, the staff asked to test and adopt the system know about the plan. Adoption planning has to account for that openly. Whether Monday's launch goes smoothly won't be known for some weeks, and the Ministry hasn't said which measures it'll use to judge readiness for the March portal release.

For organisations planning their own replacement, our digital transformation and ERP pages cover how we approach staged rollouts.

Practical next steps

  • Pick a pilot team or site with genuine volume and limited exposure, and give the pilot users months in the new system before customers or partners touch it.
  • Set the data cutover rule early. Either move open work across or run new work in the new system while old work finishes in the old one. If you choose dual running, budget for it and plan how reporting will combine both systems.
  • Write down the contingency trigger before go-live. Record the severity of issue that moves the date, who makes the call and what the fallback date is.
  • Treat training as your own workstream with your own owner and budget, and check the vendor's training estimate against your actual staff numbers and shift patterns.
  • Commission independent QA at major gates and agree in advance that its findings go to the steering group unedited.
  • On time-and-materials contracts, ask the vendor to re-estimate after discovery and report variance monthly against that re-baselined figure.

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
Get new articles by RSS