Local councils are under pressure from two directions at once. Residents expect digital services that work as well as the apps they use in their personal lives. At the same time, councils are operating on constrained budgets with legacy systems that weren't designed to talk to each other. The gap between what residents expect and what existing platforms deliver is where custom development starts to make sense.

The enterprise platforms used in local government -- TechOne, Civica, Salesforce Government Cloud -- are comprehensive systems that handle core council functions well. Most councils already run one of them, and they're generally the right choice for back-office operations. Custom development isn't a replacement for those systems. It's most valuable for specific resident-facing experiences the large platforms don't do well, or for field officer workflows that need a mobile-first approach the platforms weren't designed to deliver.

Councils in NSW, including smaller regional councils and the Southern Highlands, often have workflows specific to their service area and community that no platform vendor has bothered to build a module for. That's where a targeted custom build -- scoped tightly to the gap -- makes economic sense.

Here's what a local council app typically needs to handle well.

Resident request and complaint portal

The resident-facing experience for lodging a request or reporting an issue is one of the clearest gaps in most council platforms. A pothole on the main street, a broken footpath, a missed bin collection, an abandoned vehicle -- residents want to report these quickly and get confirmation that someone has seen it.

Maps and geolocation lets residents pin the issue on a map rather than trying to describe a location in text. This also means the report arrives at the council with precise coordinates, which is significantly more useful for dispatch than a street address description.

Push notifications and SMS notifications can update the resident when their request has been received, assigned, and resolved -- without staff needing to send individual emails. Closing the loop with residents is one of the most consistent drivers of satisfaction in council service delivery.

Real-time updates to a request tracking view give residents visibility of where their request sits in the workflow, which reduces repeat contacts to the council contact centre.

Permit and DA tracking

Development applications and permits are high-stakes for applicants and administratively complex for council staff. Applicants want to know where their DA is in the assessment process. Council planning staff need to track documents, conditions, referrals, and determinations.

A permit tracking module tied to document management gives applicants a portal view of their application status, any outstanding information requests, and the determination once it's made. For councils handling significant development activity -- particularly those experiencing residential growth -- this reduces the volume of status-check calls to the planning team.

Audit trail on DA documentation -- who lodged what, when referral responses came in, when conditions were modified -- is important for both internal process management and for decisions that may be reviewed by the Land and Environment Court.

Role-based permissions ensure applicants can only see their own applications, referral authorities see only relevant referrals, and planning staff have the access they need based on their role.

Asset and infrastructure management

Councils are responsible for significant physical assets: roads, footpaths, bridges, parks, drainage, public buildings, and fleet. Tracking the condition, maintenance history, and inspection schedule of these assets is a core function that specialist platforms (Infor, Confirm, Asset Edge) handle well. For councils already running one of those systems, integration is usually the right answer.

Where custom development adds value is in the mobile field experience: a council inspector or maintenance worker who needs to look up an asset record, log a defect, or record a completed maintenance task on their phone, in the field, without going back to the office to enter data.

Offline mode is important for outdoor inspections where coverage is unreliable -- particularly in rural council areas where field officers are working across large geographic areas.

GPS tracking can be used to confirm that inspection tasks have been physically completed at the correct location, which is useful for contract management and for audit purposes.

Inspection workflows

Council officers conduct a wide range of inspections: building, health, environmental, compliance, and licensing. Each inspection type has specific checklists, required documentation, and follow-up actions.

A mobile inspection app lets officers complete structured inspection forms on-site, attach photos, record GPS location, and generate a formal inspection report without returning to the office to write it up. PDF report generation from the completed form, sent automatically to the property owner or business operator, compresses the time between inspection and formal notification significantly.

Background and scheduled jobs can manage the inspection schedule: generating upcoming inspection lists, sending reminders to officers, and flagging overdue inspections to supervisors.

Document management and records

Councils are subject to the State Records Act and the Government Information (Public Access) Act. Document management needs to reflect these obligations: records need to be retained for defined periods, access needs to be logged, and documents may need to be produced in response to GIPA applications.

Audit trail on document access -- combined with role-based permissions -- provides the access control and logging that public sector records management requires.

For councils that need to move away from shared drives or email-based document management, a properly structured document repository with search, version history, and retention rules is a significant operational improvement.

File versioning and history ensures that earlier versions of planning documents, council reports, and policy documents are retained and accessible, not overwritten.

Integration with existing council systems

This is often the most technically complex part of a council build. TechOne, Civica, and other council platforms have varying levels of API access. Some support modern REST APIs; others require more complex integration approaches.

Public API and webhooks architecture on the custom side ensures the new system can push and pull data from existing platforms without manual data entry on both sides. The integration scope -- which systems, which data flows, how frequently data syncs -- is one of the biggest drivers of build cost and complexity.

Be specific about which integrations are genuinely non-negotiable and which would be nice to have. Integrating with a legacy system that has poor API support can cost as much as the rest of the build combined.

Staff rostering and availability

For councils with operational staff -- waste services, parks and gardens, infrastructure maintenance -- resource and staff scheduling and availability management help supervisors manage rosters, leave, and day-to-day task allocation. This is particularly relevant for councils that operate their own services rather than contracting them out.

Award obligations for local government workers under the Local Government (State) Award need to be factored into any rostering logic.

What does it cost?

Council builds vary enormously based on scope. A resident request portal or permit tracker integrated with an existing platform typically runs $60,000--$120,000 AUD. A broader platform covering resident services, field inspections, asset management, and system integrations would be $120,000--$250,000+ depending on integration complexity and the number of modules required.

The app cost calculator can give you a rough sense of where a specific scope might land.

Questions to ask before you build

Is TechOne, Civica, or your existing platform not doing this, or not doing it well enough? The enterprise platforms are expensive and slow to customise, but they do a lot. Make sure the gap you're trying to fill is genuinely not covered before committing to a custom build alongside them.

What is the resident-facing experience you're specifically trying to improve? Custom development is strongest when solving a specific, well-defined problem for a specific group of users. "Better digital services for residents" is too broad. "Let residents track their DA through the assessment process without calling us" is a build scope.

What are your integration requirements with existing systems? Get your IT team and the vendors of your existing platforms involved early to understand what API access is available and what data flows are feasible.

What are your obligations under the State Records Act and GIPA? Any document management functionality needs to comply with retention and access requirements. Legal and records management teams should be involved in scoping.

What devices do your field officers use, and what is mobile coverage like in your area? For regional councils with large service areas, offline capability for field apps is important. For urban councils with reliable coverage, it may not be.

---

See also: Maps and geolocation · Audit trail · Offline mode and PWA · Role-based permissions · App cost calculator · Book a free chat