From the Local Government edition of October 31, 2026
Newcastle and Muswellbrook councils launch the DAISY AI planning assistant; vendor reports 16,533 conversations in nine months while Wingecarribee removes it after a pilot
City of Newcastle and Muswellbrook Shire Council (New South Wales); vendor Enterprise AI · Municipal planning and development applications · Hunter region, New South Wales, Australia
- Publisher
- Information & Data Manager (IDM)
- Original publication
- 30 October 2026 (Information & Data Manager)
- Source retrieved
- 2026-11-01
What happened
Two more New South Wales councils, Newcastle and Muswellbrook, put the DAISY AI planning assistant on their websites to explain which planning rules apply to a property and which documents an application needs. Across all live councils the vendor reports 16,533 conversations from January to September 2026, a third of them outside counter hours, and models 4,133 staff hours returned at 15 minutes per enquiry. It also claims a 20% cut in assessment timeframes and a 49% rise in service capacity for early adopters, without a stated method. The same article notes Wingecarribee Shire Council is removing the tool after a 15-month pilot.
Why it matters
Why now: published 30 October with new council launches and nine-month usage totals. It is a rare case where adoption and withdrawal of the same municipal AI tool appear side by side, which is useful for U.S. cities weighing permit-guidance assistants. Transferability is limited by NSW planning law and vendor-only metrics.
Evidence and measured results
Vendor-reported conversation counts and modelled staff hours; unattributed assessment-time and capacity claims; one sentence on a council removing the tool. No independent evaluation.
Limitations and uncertainty
Vendor metrics; hours modelled; 20% and 49% claims unattributed; withdrawal reason not reported.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-31; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Planning teams spend time on avoidable enquiries and incomplete development applications.
- Stakeholders
- Planning director
- Customer service manager
- Council IT lead
- Elected councillors
- Discovery questions
- How many pre-lodgement enquiries arrive by phone and counter each month?
- What share of applications are returned as incomplete?
- What would make the council end a pilot early?
- Who maintains planning-rule content today?
- Value hypothesis
- Bounded: after-hours guidance could reduce some routine enquiries if answers prove accurate.
- Potential engagement
- A pilot design with baseline enquiry counts, accuracy sampling and exit criteria for an AI planning-guidance assistant.
- Unsupported claims
- Assessment times fell 20% at any named council
- Staff hours were actually saved
- Answers are accurate
Pre-sales engineering
Role takeaway
- Fit
- Councils with codified planning controls and public property data.
- Architecture and integration
- Website assistant grounded in planning controls, with a planned link to the case-management platform for planner-side checks.
- Prerequisites
- Machine-readable planning controls
- Property data access
- Content update process
- Constraints
- NSW-specific planning law
- Vendor-reported metrics only
- Integration tied to one platform vendor
- Security
- Define what conversation data is stored and for how long before launch.
- Proof of value
- Score answers on a sample of real enquiries against planner judgement
- Compare incomplete-application rates before and after launch
Delivery
Role takeaway
- Work
- Load planning content, launch applicant guidance, monitor usage and decide on planner-side extension.
- Dependencies
- Vendor content updates
- Planner time for answer review
- Platform integration if extended
- Ownership
- Council planning department, with customer service for resident-facing performance.
- Skills and adoption
- Planners learn to review and correct the assistant's rule content.
- Governance checkpoints
- Pilot review against agreed measures
- Decision gate before planner-side use
- Annual contract and exit review
- Acceptance criteria
- Proposed: sampled answer accuracy above an agreed threshold
- Proposed: measured drop in phone and counter enquiries
- Proposed: documented exit plan
- Risks
- Outdated rule content gives wrong guidance
- Metrics remain vendor-only
- Tool removed after sunk effort
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Resident-facing guidance is the first stage; the vendor is integrating with Civica Altitude and Muswellbrook is exploring planner-side assessment support, which would move the tool from public information into the case-management system.
Governance
Who approves, reviews and stays accountable for outcomes?
The vendor states planners remain responsible for all assessments and determinations. Councils moving to assessment support would need rules on how AI-prepared compliance checks and report drafts are reviewed.
Security and privacy
What data, permissions and controls need testing?
The article does not describe what resident data conversations capture or how it is retained.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
A third of conversations happened outside counter hours, pointing to after-hours demand; staff time effects are modelled, not observed.
Procurement
What should contracts, pricing and exit terms secure?
One council ended the tool after a pilot, so contracts should include exit terms and agreed success measures before rollout.
Operating model
Which teams own the service once it runs?
Councils are staging from applicant guidance to planner assistance, which changes who owns the tool from communications to planning.
Publication history
- 2026-10-31Local Government · Issue 564 resources
Stable resource ID: nsw-hunter-councils-daisy-ai-planning-assistant-16533-conversations-wingecarribee-removal-20261030