Government
Public-service modernisation - the next generation of automation and experience.
Government departments, agencies, and service partners have the challenge of delivering customer (citizen) services that meet modern expectation, with the added need to architect for scale.
Every corner of the government tech stack has undergone rapid evolution over the past 5 years. Bigger, faster, smarter, and more reliable. Adopting these advancements is often a complex program of change, but the real opportunity lies in measurable interventions that ship value in months, build evidence, and earn the right to do more. This is the work we do in Australian government.
Our proof in government is multiple production engagements, including a state regulator and a state government department, both anonymised at the client's request. The discipline underneath them, making the rules that govern public services visible, auditable, and owned by the people responsible for them, transfers to any department where rules matter and audit trails are not negotiable. Alongside the decisioning work, citizen service and accessibility, including sign-language self-service, are already in production in European public service, and we are bringing them to ANZ. We mark clearly what is proven and what is still ahead.
The landscape
The problems departments, agencies, and regulators often recognise
We have worked with a number of government departments and their extended network of supporting partners over the years. Here are some of the key challenges we often observe.
The rules are invisible to the people responsible for them
The logic deciding who gets which service, who pays what, who qualifies, lives in legislation, policy documents, and the heads of long-serving staff. It is also buried in systems built fifteen years ago and modified hundreds of times. When policy changes, finding where the rule actually lives is detective work.
Policy changes. The system doesn't.
When the policy team needs a rule changed, the answer is a release cycle measured in quarters, queued behind every other IT priority. Policy intent and system behaviour drift apart. And because the rules are opaque, as much as you may test, some gaps emerge late in the program, or even after go-live.
You can't always show your work
When a decision is challenged, on review, appeal, FOI, or audit, you have to reproduce exactly which rule applied, in which version, against which data, at that moment. Most systems can tell you what they decided today. Far fewer can tell you what they would have decided two years ago, and that is the question that matters.
The real work is in the exceptions, and no one can see it
Most systems are built for the happy path. The edge cases and ambiguous submissions fall into a catch-all queue with a generic error and a reviewer eyeballing everything. The exception path turns into increased, often manual, workload, invisible to everyone judging whether the system works.
The routine swallows the people who should be on the hard cases
Citizens call, email, and queue with the same questions: opening hours, which form, where their request is up to, how to book the collection. Front-line staff spend the day on first-level queries while the cases that actually need judgement wait behind them. The service is busy and slow at the same time.
Not every citizen can use the service the way it was built
A public service assumes a citizen who can read the form, navigate the portal, wait on hold, and hear the phone. Deaf and hard-of-hearing citizens, and people who do not read the language the form is written in, are left needing an intermediary to reach a service that is theirs by right. Universal is not the same as accessible.
What good looks like
A department that has solved these
Shifts that follow when the problems above are addressed structurally. None of them require a five-year program. Each one is achievable in increments, with evidence built at each step.
The rules are visible, and they belong to the business
The logic governing a service is written where the policy team can see it, test it, and change it. No archaeology. No dependency on the one person who remembers why.
Policy moves at the speed of policy
A rule change is modelled, tested against the live ruleset, and shipped in days. The team sees the impact before it commits, not after.
Every decision can be reproduced
Versioned rules and immutable logs mean any decision can be replayed exactly, against the rules in force when it was made. Audit becomes verification, not recovery.
The exception path is designed, not endured
Routine cases clear automatically. The hard ones route to the right person with the context already gathered. The exception queue stops being the workload.
The routine clears itself, around the clock
Citizens get answers, book appointments, submit readings, and find forms at any hour, often in a handful of messages rather than a place in a queue. Staff spend their time on the cases that need a person. The service is available when the citizen is, not only when the office is open.
Every citizen can self-serve, on their own terms
The service responds in the citizen's own language and in sign language, so deaf and hard-of-hearing citizens complete the task themselves, with no interpreter in the loop. Accessibility is built into the service, not bolted on as a separate channel.
Several engagements anchor our work in government.
Two kinds of public-service work. Decisioning, proven in our home market: both Australian engagements anonymised at the client's request. Citizen service, proven in European public service: production deployments of the conversational AI platform Digital Experience Labs brings to ANZ.
State government department
Contract management - making policy rules visible and shippable
An Australian state government department running a high-volume contract program. We made the business logic governing public funding visible, auditable, and manageable by the policy team. Rule changes moved from quarters to weeks. The policy team gained the ability to model changes before recommending them.
State regulator
Lodgement validation at scale, with full audit
An Australian state regulator running high-volume lodgement validation. The platform validates filings in batch processing with complete audit trails, protecting millions of citizens behind the scheme. Decision logic externalised, owned by the regulator, ready for the regulatory and product change cycle the regulator operates against.
Conversational citizen service, end to end
An environmental-services utility serving Tuscany, running conversational citizen service and end-to-end booking across phone and web - more than 100,000 appointments booked end to end. Answers routine questions in the citizen's own language and hands judgement to a person. Working today in Europe; ready for ANZ government service.
Citizen service that speaks sign language
An Italian water utility serving 107 municipalities, running 24/7 self-service and a signing avatar in Italian Sign Language, so deaf and hard-of-hearing citizens self-serve directly, no interpreter in the loop. The architecture extends toward Auslan, which is the build step for ANZ. Proven capability; Auslan is the next step.
AI plus immersive kiosks
Service and information points for physical locations, regional offices and service centres, combining conversational AI with an interactive interface. In production in European public and cultural settings. The ANZ government application is the next step.
How we engage
Pilot first. Then more.
The government buyer is risk-averse for good reason. Five-year programs with fixed scope and immovable end dates are how regrets are born. We do not work that way. We deliver in increments that ship, get used, and get measured.
Pilot
A pilot is bounded - small scope, defined success criteria, evidence-based outcome. Three to six months. Targeted at one high-value pattern in your context. Cost low enough to fund from operational budget if needed.
Evidence
The pilot produces measured outcomes - not promises. Time saved, errors reduced, citizens served, decisions consistent. The evidence sits with the department, not the vendor.
Extension
If the evidence justifies it, the pilot extends. New pattern, adjacent context, deeper integration. Each extension a new commitment with its own scope, its own success criteria, its own evidence. Not a march toward a megaproject.
This is not the only way to engage with us. For departments that prefer a different model, we will work the way that suits the procurement and risk posture. The pilot-first pattern is what we recommend by default because it is what we have seen work in government contexts.
Capabilities that apply
Where to start
Our decisioning and AI capabilities cover the work on this page. Process and Decision Automation anchors the decisioning work, where both our state-level engagements sit. Artificial Intelligence covers citizen service and accessibility, including sign language, proven in European public service. Programs typically start with one and grow into the other.
Process and Decision Automation
Public-service decisioning, rule externalisation, program integrity, lodgement validation. State-level proof anchors here.
Artificial Intelligence
Citizen-facing services and self-service for routine matters, with accessibility, including sign language, designed in from the start so more people can self-serve without an intermediary.
Related reading
Go deeper
Pieces on public-service decisioning, the boundary between automation and judgement, and where AI helps in regulated contexts.
Questions we get asked
What government work do you do?
High-volume business rule automation, decisioning and validation services, process automation, and citizen service. The citizen-service work, including 24/7 self-service and sign language, is proven in European public service and coming to ANZ. All of it is performant, scalable, adaptable, and auditable.
What is lodgement validation?
Checking high volumes of lodgements against a regulatory ruleset, with every exception explained and every decision replayable against the rules in force at the time. An Australian state regulator runs this in production, validating filings at scale with complete audit trails.
Do you replace legacy government systems?
Only if needed. Otherwise, we modernise in increments that ship, integrating with what is already in place.
Can citizens access government services in sign language?
Yes. The conversational platform we bring to ANZ runs a signing avatar in production at acquevenete, an Italian water utility, so deaf and hard-of-hearing citizens self-serve with no interpreter in the loop. The architecture extends toward Auslan for ANZ deployment.
Can AI handle routine citizen queries around the clock?
Yes. In European public service the platform answers routine questions, books appointments, and tracks requests 24/7 in the citizen's own language - more than 100,000 appointments booked end to end at one utility - and hands anything needing judgement to a person.
Is conversational AI proven in public service?
Yes, in European public service. Sei Toscana runs conversational citizen service and end-to-end booking across phone and web; acquevenete, serving 107 municipalities, runs 24/7 self-service including Italian Sign Language. Both are in production today.