Large councils often have their own reporting app, an online portal and a customer service centre. Small and rural councils usually do not. Many take reports from residents by phone and email, and staff type them into a system by hand. This post looks at what a small council needs from issue reporting software, and what to ask before you choose one.
How small councils take reports today
When we looked at the public websites of Queensland councils in October 2026, the picture was clear. The larger councils offered online forms, portals and, in one case, their own app. Several small and rural councils offered a phone number and an email address. One used a free third-party reporting app and its web form.
None of these is wrong. Phone and email work, and everyone can use them. But they have costs that a small team feels most:
- No exact location. A resident describes the spot, and a staff member works out where it is.
- No photo, or a photo in an email. Staff must save it and attach it to the request.
- Retyping. Every report is typed into the request system by hand.
- No status for the resident. Residents phone again to ask what happened.
- Reports for the wrong council. On a long rural road near a boundary, the resident may not know which council owns it.
In a council with one or two customer service officers, each of these steals time from other work.
Why small councils are different
Small and rural councils have needs that large councils do not share.
A small team. The same officer may answer the phone, take rates payments and log requests. There is no one to build or maintain a custom app.
Large areas. A rural council can cover thousands of square kilometres. An exact map pin saves a crew a long drive to the wrong spot.
Many roads, few people. Rural councils maintain long networks of roads with a small rate base. They need to know where the work is and what it costs.
A tight budget. A council cannot spend on a system that only a large council can afford.
Visitors and travellers. Many reports come from people passing through, who do not know the council's name, website or phone number.
What to look for
If you lead customer service, works or IT at a small council, check these points before you choose an app.
Free for residents, easy to start
Residents will not pay to report a pothole. The app must be free, and it must work on iOS, Android and the web, so residents without the app can still report.
Your categories and your boundary
The app should show your council's own list of problems, not a generic list. It should check that the pin is inside your council's area, so you do not receive reports for your neighbour's roads.
The five things a crew needs
Each report should carry the category, an exact location, photos, the time and the resident's contact details. Without them, staff phone the resident back.
Somewhere useful to land
Ask where the report goes. Into an email inbox, into a separate portal, or into your own request system ready to assign? The less retyping, the more time your team saves.
A way back to the resident
Status updates reduce follow-up calls. Ask how the resident hears that the job is scheduled or done.
Clear rules on privacy and data
Ask who can see the reports, and where the data is held. Ask whether your council's data is kept apart from other councils' data.
Nothing to maintain
A small council should not need to host servers or publish its own app in the app stores.
How Localtech Eye fits small councils
We built Localtech Eye with small and rural councils in mind. It is a free app for residents on iOS, Android and the web.
- Residents pick the problem from your council's own list and add up to five photos.
- They drop a pin, and the app checks that it is inside your council's area.
- The report carries the resident's name and contact details, so your staff can reply.
- The app removes location details from the photo files before upload. The time and place of capture go to the council as fields, with the map pin.
- Reports are not visible to other residents.
- Each council's data sits in its own database.
Where the report lands:
- Today: your council receives each report by email, with the photos, the map point, the address and the resident's contact details. Your staff contact the resident directly.
- With Localtech Core (in development): the Customer Requests module will receive each report as a customer request, ready to assign. A supervisor will be able to turn it into a work order, and residents will see the status in the app.
So a small council can start with email, with nothing to install, and connect the reports to work orders later. Read how that loop works in From resident report to work order: closing the loop.
Where it is available
Localtech Eye is live for Queensland councils. New Zealand, the United Kingdom, the United States and Canada are now taking councils. There is no resident service in those countries yet. See Australia or New Zealand.
The iOS and Android apps are in App Store and Google Play review. Residents in Queensland can report a problem on the web today.
See it with your council's data
For the wider view of request channels, triage and closing the loop, read Citizen service requests: how councils take reports. If you work at a small or rural council, book a demo. We will show you Localtech Eye with your council's categories and boundary, and talk through what suits a small team.