How that call is handled sets the tone for years. On a road, rail, water or energy project, complaints are not a side task for the community team. They are an approval obligation, an early warning of delay, and often the only record of what the project knew and when.
This guide sets out a practical complaints process for engagement and project teams, with the documents worth reading alongside it. It is general information, not legal advice. Always work from your own approval conditions and management plans.
Start with what your approval actually requires
Before designing anything, pull the complaints clauses out of your conditions of approval, environmental authority and contract. They are usually more specific than teams remember.
The NSW Department of Planning, Housing and Infrastructure's template conditions for linear State Significant Infrastructure are a useful benchmark even outside NSW. They require a Complaints Management System in place before work starts and kept for at least 12 months after construction finishes. They also require a 24-hour phone number, a postal address, an email address and a mediation process for complaints that can't be resolved, all available a month before work starts and accessible regardless of age, ethnicity, disability or literacy.
The same template lists what the Complaints Register must record: the number of complaints, the date and time, how each was made, the complainant's details (or a note that none were given), the nature of the complaint, how it was addressed and whether it was resolved, and, if nothing was done, why. The register must be available to the Planning Secretary on request.
In Queensland, state agencies have a separate duty. The Public Sector Act 2022 requires public sector entities, including state government departments and public service offices, to run a customer complaint management system that complies with the current Australian Standard, which the Queensland Ombudsman confirms is AS 10002:2022. And where a complaint points to environmental harm, the Environmental Protection Act 1994 (Qld) duty to notify may start its own clock.
So one phone call can touch a planning condition, a public sector obligation and an environmental duty at once. Your process needs to see all three.
Use a three-level model
AS 10002:2022, Guidelines for complaint management in organizations, and the Queensland Public Service Customer Complaint Management Guideline both describe three levels:
- Frontline resolution. Most complaints about dust, noise, access or parking should be fixed by the first person who takes them, the same day if possible.
- Internal review. If the resident isn't satisfied, a more senior person who wasn't involved looks again.
- External review. Mediation, an ombudsman or the regulator.
On infrastructure projects, level 1 often sits with a contractor and level 2 with the client. Write down who owns each level, and make sure the handover doesn't reset the clock or lose the history.
Build the process around six steps
The NSW Ombudsman's complaint management guidelines set out six principles: respectful treatment, information and accessibility, communication, taking ownership, timeliness and transparency. Turned into a project process, that looks like this.
1. Receive it in any channel. Residents call the hotline, email the project inbox, stop a traffic controller, post on a community Facebook group or raise it at a drop-in session. All of these are complaints. If only the hotline counts, your register will undercount and your trends will mislead.
2. Record it the same day. Capture the fields your approval lists, plus location (address or chainage), the work package, the contractor responsible and any commitment already made to that household. A complaint without a location can't be mapped against the works program.
3. Acknowledge it. Tell the person you have it, who is handling it and when they'll hear back. Set acknowledgement and response timeframes in your procedure and publish them. The Queensland guideline requires agency complaint policies to state these timeframes.
4. Triage it. Ask three questions straight away:
- Does this suggest environmental harm or a safety risk? If so, escalate to the environment or safety lead now, because statutory clocks may already be running.
- Does it relate to an approval condition (noise limits, work hours, access)? If so, flag it for the compliance team.
- Is this person, street or issue already in the register? Repeat complaints are a different conversation from first ones.
5. Respond and act. Fix what can be fixed, explain what can't and say why. If you make a promise, such as rescheduling deliveries or installing a screen, record it as a commitment with an owner and a due date. Our guide to what a stakeholder commitments register should include covers the fields.
6. Close the loop. A complaint isn't closed when the contractor marks the job complete. It's closed when the resident has been told what happened. Record that communication, not just the action.
Watch the patterns, not just the tickets
The register is also your best early warning. The Queensland guideline includes trend reporting and analysis as part of the complaint lifecycle, and the same habit pays off on projects. Review it weekly with the construction team and look for:
- Clusters by place. Five complaints on one street in a week is a signal, even if each was "resolved."
- Clusters by contractor or activity. Night works, spoil haulage and traffic switches tend to drive spikes.
- Rising tone. A resident who was polite in March and angry in June is telling you something the complaint count won't.
- Silence. A street that complained often and then stopped may be satisfied, or may have given up and gone to their local member.
Share a short summary with the project director. Complaint trends are project risk, and they belong in the same conversation as program and cost.
Common gaps auditors find
When complaints handling is tested in an independent audit or a regulator request, the same weaknesses come up:
- Complaints recorded in several places (contractor spreadsheets, a client CRM, a shared inbox) that don't reconcile.
- No record of why no action was taken, even though the NSW template asks for it.
- Commitments made over the phone that never made it into the register.
- Response timeframes published but not measured.
- Personal information collected without telling the complainant how it may be shared.
Each one is easier to prevent at intake than to fix the week before an audit.
Where VivoAI fits
Most teams we talk to aren't short of complaints data. They are short of one place where it all lines up. VivoAI is built around a simple idea: One complaint. Three obligations. One record. Each complaint sits on one record that links the approval condition, the compliance clock and the evidence trail. VivoAI scores each interaction, shows whether sentiment is improving or worsening by place, and gives an indicative dollar risk. It is fully Australian hosted.
If you're reviewing your complaints process before construction starts, or ahead of an audit, I'm happy to compare notes. Get in touch.
Sources
- NSW DPHI, Template Conditions of Approval for State Significant Infrastructure (Linear Infrastructure), conditions B6 to B10
- Standards Australia, AS 10002:2022 Guidelines for complaint management in organizations
- NSW Ombudsman, Effective complaint management guidelines
- Queensland Ombudsman, Policy and procedure guide
- Queensland Government, Queensland Public Service Customer Complaint Management Guideline
- Environmental Protection Act 1994 (Qld)
This article is general information, not legal advice. Check your own approval conditions and obtain advice for your circumstances.
Next step
One complaint. Three obligations. One record.
If you're reviewing your complaints process before construction starts, or ahead of an audit, I'm happy to compare notes.