AI training for Copilot, Claude and OpenAI. Book your slot now 09 974 2379Client PortalRemote Support
Belton IT Nexus
Belton · Run / Protect / Improve / BuildView all services ›
Belton · Knowledge, not gatekeepingResource library ›
Belton IT Nexus · Est. 2004 · Newmarket, AucklandAbout us ›
Home/ Industries/ Government & Local Government

Technology for New Zealand agencies and councils, built around the obligations you carry.

Public sector IT is judged on evidence, not effort. We run the environment, and our flagship product, Duly, takes on the weeks that official information requests eat.

OIA& LGOIMA, one system NZISMaligned controls M365your own tenancy AIoff by default
Public sector IT
§01

The obligations are the architecture

The brief

Agencies and councils are not judged on whether the work was done. They are judged on whether it can be shown. A request answered well but reconstructed badly six months later still becomes a complaint, and the reconstruction costs more than the answer did.

That changes what good IT looks like here. Access control, retention, logging and the audit trail stop being hygiene and become the deliverable. We build public sector environments so the record is a by-product of doing the work, not a project that starts when someone asks a question.

The rules NZ agencies and councils work under

Official Information Act 1982 and the Local Government Official Information and Meetings Act 1987. Twenty working days to decide, withholding grounds that have to be reasoned rather than asserted, and an Ombudsman who can ask exactly how you reached the answer. The two Acts ask for the same discipline and then wire it differently.

Privacy Act 2020. Notifiable privacy breaches go to the Office of the Privacy Commissioner, and public sector holdings are almost entirely in scope. The controls have to be both strong and demonstrable.

Public Records Act 2005. Full and accurate records, created and maintained, with disposal only under an authorised schedule. Archives New Zealand audits against it. Cloud migrations and mailbox cleanups are where this quietly goes wrong.

NZISM and the Protective Security Requirements. The New Zealand Information Security Manual sets the technical baseline your security team assesses against. We design to it rather than retrofitting to it after a review.

Dulyby Belton IT Nexus

Case management & assurance · OIA & LGOIMA · Agencies & councils

Get the weeks back.

Duly takes on the parts of an official information request that eat the calendar: finding who holds what, running the search, drafting the letter and the schedule, chasing the approvals. Your people spend their time on the decisions that actually need them.

And because every step runs through one system, the record builds itself.

What it is

An operating system for official information, not another AI assistant.

Duly doesn't replace your Microsoft environment. It sequences it into a request-handling workflow and wraps every step in an audit trail.

Runs in your own environment
Installs into your Microsoft 365 tenancy and reads your data in place.
Built for New Zealand law
Response clocks, transfer windows, extensions and both working-day calendars. Tested rules, not a model's judgement.
The record is a by-product
Every action is time-stamped as it happens, so nobody writes the audit trail afterwards. It's the spine of the system, not a report bolted on.
No new platform in the path
Works with the Microsoft 365 licences you already hold. Nothing new to buy, and nothing new for your security team to assess.

Won't Copilot and Purview do this eventually?

They do parts of it well. Neither holds a case, runs a statutory clock, routes approval by delegation, or produces an evidence pack. Duly makes their output defensible.

Is it the same product for agencies and councils?

One product, one codebase. The rules engine is configured to the Act you're under, and your templates, delegations and approval chains are your own.

What makes it different

The hard part isn't answering.
It's proving how you answered.

Speed is only worth having if the answer holds up. Two commitments most tools can't make.

Reproducible search

We can show you what was searched, not just what was found.

Duly searches with explicit, recorded queries. Every search is stored in full: terms, people, locations, date range, results. Re-run it in two years and you get the same answer.

If a complaint turns on whether a search was thorough, you have to describe the search itself. A tool that hands back "these documents seemed relevant" can't. Ours is written down.

The AI line

AI assists. The human decides. Always.

Every withholding decision is a legal decision, and Duly is built so it stays one. This isn't a setting. Every AI suggestion is recorded separately from the decision it informed.

AI is used for
  • Summarising for review
  • Suggesting who may hold material
  • Grouping & de-duplicating
  • Drafting from your templates
  • Surfacing past decisions
AI is never used to
  • Choose a withholding ground
  • Weigh the public interest
  • Declare a search complete
  • Release anything unsigned

If your organisation isn't ready for AI here at all, Duly runs without it. Every AI feature switches off tenancy-wide, and that's how the first release ships. AI is never in the redaction path.

In your tenancy

We work inside the environment you've already accredited.

Duly is built by Belton IT Nexus, Microsoft specialists. That isn't a line on a credentials slide. It's the reason Duly reads your information where it already lives, instead of asking you to move it somewhere new and justify that to your security team.

Nothing leaves your tenancyNo export, no copy, no new perimeter to assess. Your documents stay where your controls already apply.
Your permissions, honouredSearch runs under the access model you already have. Nobody sees material in a review set they couldn't open in SharePoint.
Your accreditation does double dutyMicrosoft 365 has already been through your security review. Duly builds on that work rather than restarting it.
One supplier who knows bothThe Act and your tenancy. When something needs fixing you're not triangulating between a software vendor and your IT partner.
The problem

The answer takes an afternoon.
The process takes three weeks.

Almost none of that time goes on the judgement calls only your people can make. It goes on locating information, chasing the people who hold it, assembling a schedule by hand, and waiting on approvals that nobody is tracking. Then the next request arrives and it starts again from nothing.

Where the time goes for both

  • Working out who holds what, then searching email, SharePoint, Teams and legacy stores by hand.
  • Rebuilding the schedule, the letter and the reasoning from scratch. Every time.
  • Answering the same requesters on the same subjects, starting from a blank page.
  • Reassembling months later what was searched and why, when someone asks.

And where it differs

  • Agencies: the clock running while Legal, Privacy and the Minister's office work through it.
  • Councils: one person on LGOIMA alongside three other jobs, with no cover for leave.
  • Agencies: consistency across business units that each answer their own requests.
  • Councils: requests that turn out to be a LIM or property file, and information held by a CCO or contractor.
0
complaints to the Ombudsman about delay in deciding, January to June 2025
+0%
rise in LGOIMA delay complaints in six months
0
complaints in total under both Acts
How it works

From request received to defensible release.

Following one case: OIR-2026-0863, a request from T. Rangi for the consultants engaged in 2025–26.

01
Capture and start the clock.
T. Rangi's request lands in a shared mailbox on 6 July. Duly logs it as OIR-2026-0863, acknowledges it from your template, and fixes the response date at 4 August, day 20, with the working shown. It also flags correspondence that is a request without saying so.
02
Triage and route.
Duly reads it as official information rather than a privacy request or a media enquiry, and assigns it to Sam Kaur. Had it turned out to be a LIM or a property file, it would go to a different team on a different clock.
03
Orchestrate the search.
Two custodians are scoped. Searches run across Exchange, SharePoint, OneDrive and Teams under your existing permissions, and every query is stored in full: terms, people, date range, results returned.
04
Draft with a head start.
The response letter and the schedule of documents generate from your templates. Last year's consultant-spend release surfaces as precedent, so nobody reargues settled reasoning or answers T. Rangi differently this time.
05
Decide, approve, dispatch.
Sam records each withholding decision against a ground from the library. Where the public interest has to be weighed, Duly requires her to write that reasoning before the case can move on. Approvals route by delegation instead of by email.
06
Keep the record that protects you.
If T. Rangi complains to the Ombudsman next March, the evidence pack exports as one record: searches run, documents considered, grounds applied, sign-offs given. Retrieval, not reconstruction.
Both Acts

One system, both Acts. And it knows the difference.

The OIA and LGOIMA ask for the same discipline, then wire it differently. The differences are small, undocumented in most tools, and exactly where deadlines get miscalculated.

OIA (agencies)LGOIMA (councils)
Time to decide20 working days20 working days
Year-end exclusion25 December to 15 January20 December to 10 January
Regional anniversary dayCounts as a working dayDoes not count
Withholding groundsSections 6 and 9Sections 6 and 7

Duly encodes both calendars and both sets of grounds as tested rules, not as a model's judgement. Councils also get LIM and property-file triage on its own clock.

Assurance

Your security team's questions, answered up front.

Designed to align with the New Zealand Information Security Manual, the Privacy Act 2020, and your recordkeeping obligations under the Public Records Act. Because Duly runs inside a tenancy your team has already accredited, and because the assurance documentation ships with the product, your review is shorter than it would be for a new platform.

Where your data sitsIn your own Microsoft 365 tenancy. Duly reads it in place. No document set is copied to our infrastructure.
Where inference runsNever outside your tenancy boundary. Where AI is enabled, it runs on Azure OpenAI in your own subscription.
Which regionAzure Australia East or Australia Southeast, with no egress beyond the region you choose.
  • Privacy Impact Assessment template
  • Architecture and data-flow diagrams
  • Permission model, plus a simulator to verify against
  • Documented map of how AI is used and bounded
  • Incident and breach runbook
  • Full export in open formats, any time
  • Built and tested to WCAG 2.2 AA

Duly is in active development, built with a small number of agencies and councils. Built from public sources: the Official Information Act 1982, LGOIMA 1987, and published Ombudsman guidance. Figures from the Chief Ombudsman's data, January to June 2025. Duly is a working name. Not legal advice; no compliance claim is made.

Common questions
§03

Government and council IT FAQ

Before you talk to us

The New Zealand Information Security Manual is the baseline, alongside the Protective Security Requirements, and we use the Essential Eight as the practical maturity ladder because it is measurable and insurers understand it. We assess where you actually are, tell you plainly, and lift one maturity level at a time with evidence at each step rather than claiming alignment you cannot demonstrate.

Yes, and it is the part most migrations get wrong. Mailboxes and file shares move, disposal authorities do not follow, and an authorised schedule quietly stops being applied. We map retention and disposal into Microsoft Purview against your schedule, keep the disposal evidence, and make sure the migration itself is recorded rather than being a gap in the record.

Duly is in active development, built with a small number of agencies and councils. The early partner programme is open now: you get the product shaped around how your team actually works, and we get the reality check that only comes from live requests. Talk to us and we will show you a real case end to end before anyone signs anything.

An honest word on investment

The best version of this page is a choice.

Outcomes follow investment

Everything described here is real and achievable, for organisations that choose to align to the best standard and invest in it. With full investment, we can promise outcomes. With half the investment, we can promise half the outcomes. Neither is wrong. Invest at the level that fits your organisation, a little or a lot, and we will align the solution honestly to that level. Four things usually set the dial:

01
Uptime
How much downtime can the service actually carry? Minutes, hours or days changes the architecture, and the investment.
02
Recovery
When something fails, how fast must you be back, and how much data can you afford to lose? Faster and less both cost more.
03
Alignment
How closely do you align to NZISM, the PSR and the Essential Eight? Each maturity level is a step up in evidence, and effort.
04
Sovereignty
Where must your data live? Onshore, sovereign hosting is there when it is required, priced plainly.

We will tell you plainly what each level buys, and what it does not. That conversation is the first thing the session settles.

Get the weeks back on
official information.

Thirty minutes with one of our senior engineers is the fastest way to get a clear read on your current setup, where the exposure sits, and what would change first. We can walk a real Duly case end to end in the same session.

And relax

Getting started is the easy part.

Onboarding without drama

We do the switch: your current provider, the migration, the handover, all of it. Most teams barely notice the cutover happened.

Everything looked after

On the right plan, compliance, reporting and budgets are handled inside the partnership. You run the business; we run the IT underneath it.

Your QBR writes itself

Quarterly business reviews are generated automatically from your live environment: spend, posture, recommendations and roadmap, ready for the board, reviewed with your account manager.

The honest bit: the full looked-after experience comes with the right plan. We charge fairly for what we take on, and when costs step up it's because you are taking on more, always moving in the right direction.

Sovereign by design

New Zealand owned and operated.

Sovereign data centres across New Zealand and Australia, with your data kept onshore wherever it's required. Our team understands New Zealand, and our leaders have built, scaled and secured businesses right across the New Zealand landscape.

Sovereign data centres · New Zealand & Australia
  • Auckland
  • Christchurch
  • Sydney
  • Melbourne
  • Brisbane
  • Perth
International data-centre operations
  • Singapore
  • Germany
  • Netherlands
  • USA

Servers available in minutes, not days.

Explore data centres & hosting →
Partners & platforms
Microsoft Solutions Partner, Modern Work Microsoft Solutions Partner, Security
Fortinet Partner Veeam Partner Lenovo Partner HP Partner SentinelOne Partner Microsoft Azure Microsoft Copilot Claude
Book your free discovery & security session