Briefing · Example Shire Council
Four channels, one list of what residents raised.
Prepared for Example Shire Council · 13 October 2026
Example data · fictional client
01 / The decision
Which resident issues reach the weekly operations meeting, and who decides.
Residents raise issues through a web form, the phone, a survey tool and the customer request system.
02 / Issues by channel Example data
Survey responses are 17.3% of issues and are not in the current list.
Web form
Phone log
Survey tool
Customer request system
Resident issues by channel · n=1,087 issues, 18 months to [date] · Source: web form, phone log, survey tool and customer request system, read [date] · Example data: Example Shire is fictional
03 / A four-week test Example data
104
of 111 repeat reports were caught by the records list in a four-week test.
The manual list caught 81.
n=111 repeat reports, four weeks to [date] · Source: the records list and the manual list, read [date] · Example data
04 / What we build
The use case determines the build.
For the weekly issues list, these are the parts. The scope names each deliverable and what it depends on.
Records
Decisions and workflow
Handover
05 / What the Council owns
When the logic is the Council’s, so is the record.
What the Council owns
- Decision logicThe rules or model behind each decision, tested and versioned, with each decision recorded.
- Data recordThe resident and service data each decision uses, with its sources and definitions written down.
- WorkflowThe steps that carry each decision into the tools officers already use.
- DocumentationRunbooks and training, so officers can run the system and change it as the Council’s needs change.
Runs inThe Council’s environment · The Council’s cloud · Hosted by NTWRK if needed
Rights and dependencies documented
Renting the part that decides
- Platforms that keep your decision logic
- AI seats that leave nothing behind
- Pilots that stop before production
- Consultants who leave decks
06 / The 30-day proof
One decision, tested in 30 days.
01
The decision
Defined with a baseline and a test, agreed before the proof starts.
02
The proof
A working proof on the Council’s data, with its results and known limits.
03
The record
The documented work behind the proof, from decision logic to workflow, handed over.
04
The recommendation
Build, buy, change the process or stop, with what it would take to run.
The proof tests one decision on agreed records. It does not establish production readiness or guarantee a return.
07 / The offer
A 30-day proof on one decision.
One decision, tested on the Council’s data against a baseline agreed first. At day 30: a working proof, its results and limits, the documented work and a recommendation to build, buy, change the process or stop.
Pricing is set in the proposal after scoping.
You can stop at day 30. Any production build is agreed separately.
08 / About
A Melbourne consultancy that builds intelligence into the systems your business runs.
With a defined handover for your team.
pending
Wes Fischer
Founder and CEO, NTWRK
+61 3 4427 7768
ABN 59 619 107 336
Start with the decision
Bring the decision worth testing.
Book a callFirst engagement: a 30-day proof on one decision.