The public sector layer for Dynamics 365
Case management for government.
NEC’s public sector case management product, on the Microsoft platform your agency already runs. Delivered in Australia by Exco Partners.
_The trap
Government casework is more than a support ticket.
Applications, complaints, licences, investigations, notifications, reviews. The work carries legislated deadlines, delegated authority, evidentiary standards and rights of appeal.
What arrives in the box with Dynamics 365 is a case record with a status field and an SLA timer. Everything that makes the work statutory has to be built, and it is where the money and the risk go.
- 01Statutory clock
- 02Workflow and routing
- 03Records and disposal
- 04Evidence and custody
- 05Decisions and authority
A missed statutory deadline is not a defect. It is a deemed decision, an appeal right, or a breach.
_Where you start
A working product, not a blank page.
Purpose-built for case management on Dynamics 365 and the Power Platform. Built once, shipped as a product, and configured to your agency.
The hard part is already done
The sections every program discovers late are decided, built and tested before yours starts. You inherit the decisions, not the discovery.
You only build what is unique to you
Product cost is visible and separate. What you fund is configuration to your services, not a statutory engine every other agency also needs.
Your business logic is configuration
Case types, forms, templates and rules are versioned and reusable. Legislative, organisational and delegation changes stay configuration.
Your first statutory service is where you find out what statutory casework actually requires, and you pay to learn it.
Your first service is where you configure what the product already knows, and every service after it costs less than the one before.
_Inside the product
Built for the work that gets challenged.
Managing complexity within your configuration.
Every case type is a versioned configuration record carrying the party roles a matter needs, the workflow it follows, the gates it must pass and the documents it produces. Publishing is a controlled act.
An agency adds a new complaint stream. A configurator clones the current version, adds two party roles and a conciliation track, and publishes. The four hundred matters already open continue under the version they started on.
- 01
A case type, and its versions
The case type is the durable identity of a service. A matter binds to the version active when it was raised and keeps it, whatever changes later.
- 02
Publishing is validated
Publish checks the whole model before anything moves: every track reachable, every transition legal, every gate pointing at something real.
- 03
A published version is frozen
Change is a new draft, cloned from the version in force. Nothing in flight moves underneath a case officer part-way through a matter.
Real casework runs multiple work-streams at once.
A single status field cannot describe a matter where assessment, consultation and a conciliation conference are all live together. Anycase 365 models a matter as parallel tracks, each separately governed.
A complaint runs assessment and respondent-notification tracks at once, with conciliation starting only if accepted. The officer sees all three in one control, and the matter cannot close while a mandatory track is unfinished.
- 01
Parallel tracks, not one status
A case type version declares its tracks and the matter carries one for each. A review track appears only on a matter actually under review.
- 02
Only the permitted moves
A move not declared as a permitted transition is refused in the platform transaction, not in a form script. That makes it a process control, not a label.
- 03
Gates define what must be true
A gate attaches to the stage, so one definition covers every route in. It can require information, a party in a named role, or evidence.
The record has to survive a tribunal.
Evidence is a record with provenance and a seal, never an attachment. Every item carries where it came from, who has touched it and what was done to it, in a chain nobody can rewrite.
A respondent disputes a document produced four years earlier. The officer walks its provenance back through two versions to the original and produces the unbroken custody trail, with the hash recorded at sealing.
- 01
Sealed evidence
An evidence item never exists without a chain of custody. The first event is written in the same transaction as the item, imports and integrations included.
- 02
The chain of custody
Custody events are refused on update and delete. There is no break-glass. A correction is a new row naming the one it corrects.
- 03
Provenance walks back
A new version names the one it supersedes, and provenance walks that chain to the original. Each version keeps its own trail.
A decision needs the power to make it.
Delegated authority is the question that gets challenged, and it is not the same as whether a user may edit a record. It is configuration, validated at the point of the decision.
A delegate declines an application under a threshold that changed six months later. The record shows the instrument in force, the position held, the evidence as it stood and the reasons given. None of it has to be reconstructed.
- 01
Delegation is to a position
A power is conferred by an instrument on a position, not a person, with dates and an optional threshold. Staff move; delegations do not follow them.
- 02
Validated at the point of decision
The check runs against the instrument version in force on the decision date. There is no override; escalation is the only path.
- 03
Immutable, and it cites its evidence
A decision cites the evidence relied on, resolved at that moment. Correction is a new decision naming the original, and both stay readable.
Document generation, to your standards.
The questions a service asks and the correspondence it sends are the two things no two agencies want the same way. Both are versioned configuration, authored by the agency, and both leave a reproducible record.
An agency revises its acknowledgement letter. New matters use the new wording from the moment it is published. A letter issued last year still renders exactly as it was sent.
- 01
Forms are configuration
A form is a versioned definition of questions, types, ordering and conditions, compiled at publish. A submitted response is immutable.
- 02
Templates authored in Word
Written by the people who own the wording. Merge paths are checked at publish, so a template that would render the wrong thing is refused, not discovered.
- 03
What was sent is what is kept
A document is bound to the template version active when it was issued. Years later, the record still shows exactly what went out.
_The lineage
Thirty-five years of statutory casework, now native on Dynamics 365.
Anycase 365 is not a new idea being tried out on your agency. It is NEC’s public sector case management product, in its Dynamics 365 form.
KMD WorkZone
The case and information management platform that runs Danish central government. More than 70% of government processes, across Police, Justice, Defence and Tax, serving over 5 million citizens.
The origin · 35 yearsNEC AnyCase
NEC brought WorkZone’s case management to the UK and Australia. AnyCase is in service for the Ministry of Defence, and across information rights, complaints and licensing.
The productisationAnycase 365
The same public sector case model, now native on Dynamics 365 and the Power Platform. Configured and delivered on the platform your agency already licenses.
Available now_The foundation
Enterprise scale, security and an AI future.
The platform decides what the agency is signing up to maintain. A bespoke case platform makes identity, integration, scale and AI a line item the agency owns for the life of the system.
Certified security and scale
IRAP assessed to PROTECTED and reassessed every two years. Capacity and resilience are Microsoft’s to run, not the agency’s to design.
Integrated where your people work
Outlook, Teams, Word, SharePoint and Power BI connect as first-party products. No interface for anyone to write or maintain.
Microsoft’s roadmap, inherited
AI arrives on the case data already there, under the permissions already set. The platform advances whether or not a project funds it.
No single supplier holds the keys.
Dynamics 365 and the Power Platform are a labour market. The agency can hire, second-source or bring configuration in-house, and put the services layer back out to tender without touching the system underneath.
_The reference architecture
Deployed in your environment.
A standard Microsoft Azure and Dynamics 365 environment. Anycase 365 is a managed solution inside it, not a second platform to run, secure and assure.
Case engine, queues, unified routing, knowledge, omnichannel, agent workspace.
Matter, parties, statutory clock, delegations, decisions, evidence and records.
Case types, instruments, rules, forms, correspondence, branding.
- Dataverse
- Power Automate
- Power BI
- Copilot
- Teams
- Exchange
- Azure Blob Storage · documents and evidence
- SharePoint · collaboration
Everything outside the blue card is standard Microsoft. That is the point.
Global scale, local delivery.
NEC has delivered critical technology and social infrastructure to governments for over a century. NEC Australia has served Australian government and business since 1969, and in 2026 added Exco Partners as its cloud, data and AI business unit, the delivery team behind Anycase 365.
_The demo
See one matter, end to end.
- Step 1 · Intake
Case types and intake
Configure a case type in minutes and see a matter logged by online form, email or front counter, then triaged and assigned.
- Step 2 · Workflow
Multi-track workflow and gates
Follow one case down parallel tracks, with gates that hold it until tasks, checks and statutory deadlines are met.
- Step 3 · Evidence
Documents and evidence
Generate notices from templates populated with case data, and capture, tag and version every piece of evidence.
- Step 4 · Decision
Decision and approval
Route a recommendation to the right delegate, record the decision and its reasons, with a full audit trail for review or appeal.
Book a product demo
Forty-five minutes with the team that delivers it. We’ll walk one of your case types through the product, in plain English.