How to Run a Resident Complaints and Communications Workflow in Strata
Strata resident complaints don't have to spiral into disputes. Here's a practical, step-by-step workflow for logging issues, assigning responses, tracking follow-up, and keeping escalations to a minimum in busy buildings.
Managing strata resident complaints is one of the most time-consuming and emotionally charged parts of running a strata scheme or owners corporation. A noise dispute that sits unanswered for a week, a maintenance request that falls between the cracks, or a by-law breach that never gets formally acknowledged — each one chips away at resident trust and increases the risk of formal tribunal proceedings.
The good news is that most escalations are preventable. The difference between a complaint that gets resolved quietly and one that ends up before NCAT (or your state's equivalent tribunal) is almost always process, not personality. This article walks through a practical, end-to-end complaints and communications workflow that strata managers, building managers, and self-managing owners corporation committees can adapt to their own buildings.
---
Why a Formal Workflow Matters for Strata Resident Complaints
A structured workflow does three things that ad-hoc email chains simply cannot:
- Creates a clear paper trail — essential if a matter escalates to mediation or a tribunal.
- Sets and communicates expectations — residents who know their complaint has been received and is being acted on are far less likely to escalate.
- Distributes accountability — it's clear who owns each action and when it is due.
Without a workflow, complaints get managed reactively. The same issues resurface, the same residents feel ignored, and committee members burn out fielding calls on their personal phones.
---
Step 1: Establish a Single Point of Entry for All Complaints
All complaints should arrive through one channel, not five. Whether that channel is an email address, an online form, or a dedicated building management platform, the goal is to eliminate the risk of requests being missed because they were sent to the wrong person or buried in a personal inbox.
What to communicate to residents
- The preferred method of lodging a complaint or request (e.g., a dedicated email address such as
complaints@[buildingname].com.au, or a resident portal). - What information residents should include: their lot number, a description of the issue, when it occurred, and any supporting photos or documents.
- The expected response timeframe — even a simple acknowledgement within 24–48 business hours goes a long way.
Post this information in the common property noticeboard, include it in your welcome pack for new residents, and reference it in your building's by-laws or house rules where appropriate.
---
Step 2: Log Every Complaint in a Central Register
Every complaint, regardless of how minor it seems, should be logged in a central register the moment it is received. This is not about bureaucracy — it is about accountability and pattern recognition.
What your complaints register should capture
- Date and time received
- Lot number and resident name (or "anonymous" if the complainant requests it)
- Category — noise, by-law breach, maintenance, common property damage, neighbour dispute, building management concern, etc.
- Description of the issue
- Priority level — urgent (safety risk), high, medium or low
- Person assigned to respond
- Target response date
- Status — open, in progress, resolved, escalated
- Resolution notes and date closed
A shared spreadsheet works for small buildings. For buildings with higher complaint volumes, a purpose-built facilities or strata management platform gives you searchable history and automated reminders — tools like Orveya are built specifically for this kind of structured workflow.
---
Step 3: Acknowledge Receipt Within a Defined Timeframe
Send an acknowledgement to the complainant as soon as the complaint is logged — ideally within one business day. The acknowledgement does not need to contain a solution. It needs to confirm:
- The complaint has been received and recorded.
- Who is handling it.
- When the resident can expect a substantive update.
This single step eliminates a huge proportion of follow-up calls and frustrated "I never heard back from anyone" emails. Use a templated response to keep this consistent and efficient, but personalise it with the resident's name and a brief reference to their specific issue so it does not feel automated.
---
Step 4: Assign, Categorise and Prioritise
Not all complaints carry the same urgency, and your response process should reflect that. A water leak affecting multiple lots is categorically different from a noise complaint about a neighbour's television.
A practical priority framework
| Priority | Examples | Target first action | |---|---|---| | Urgent | Structural safety risk, fire safety concern, flooding | Same day | | High | By-law breach causing ongoing nuisance, lift outage, security issue | Within 48 hours | | Medium | Noise complaint, parking breach, general maintenance request | Within 5 business days | | Low | Suggestion, general enquiry, minor cosmetic issue | Within 10 business days |
Assign each complaint to a named person — the strata manager, building manager, committee member, or contractor — and make that assignment visible in the register. Unassigned complaints fall through the gap.
---
Step 5: Investigate Before Responding on Substance
Before sending a substantive response to either party in a dispute, gather the facts. This means reviewing relevant by-laws, inspecting the area if the complaint involves common property, and — where the complaint concerns a specific lot owner — giving that person an opportunity to respond before any formal notice is issued.
This step protects the owners corporation from allegations of procedural unfairness and, in most Australian jurisdictions, is a prerequisite before issuing formal breach notices or escalating to a tribunal.
Keep brief investigation notes in the register. If site photos are taken, attach them to the record.
---
Step 6: Communicate the Outcome Clearly
Once a resolution or next step is determined, communicate it to the complainant in plain language. Avoid strata jargon. Tell them:
- What action has been taken or will be taken.
- Any timeframe for that action.
- What the outcome means for them practically.
- What they can do if they remain unsatisfied (internal review, formal mediation, tribunal).
If the complaint cannot be resolved in the resident's favour — for example, the alleged breach did not occur, or the matter falls outside the owners corporation's jurisdiction — explain why clearly and respectfully. Residents who understand the reasoning are far less likely to escalate than those who receive a generic "we've looked into it" response.
---
Step 7: Track Follow-Up and Close the Loop
An unresolved complaint sitting in an open status is a future escalation waiting to happen. Build follow-up checkpoints into your workflow:
- Set a reminder to check in with the complainant within a week of issuing your response.
- If a contractor has been engaged, confirm completion before marking the complaint as resolved.
- If the matter involves a by-law breach and a notice has been issued, diarise a follow-up inspection.
When a complaint is genuinely resolved, close it in the register with a brief note summarising the outcome and notify the complainant. Closed-loop communication signals professionalism and builds trust over time.
---
Step 8: Review Complaint Trends Regularly
Your complaints register is a management intelligence tool, not just a filing system. Review it at committee meetings — quarterly at minimum — and look for patterns:
- Are complaints clustering around a particular area of common property (suggesting a maintenance backlog)?
- Is the same lot number appearing repeatedly as either complainant or subject?
- Are noise complaints spiking after short-term rental activity?
Trend data lets you address root causes proactively, rather than managing the same issues reactively over and over. It also provides objective evidence for committee decisions on capital works, by-law amendments, or contractor performance reviews.
---
How to Reduce Escalations Before They Happen
Most escalations in strata stem from poor communication, not irresolvable disputes. The following practices consistently reduce the rate at which complaints reach mediation or tribunal:
- Acknowledge fast, resolve at the right pace — speed of acknowledgement matters more to residents than speed of resolution.
- Be consistent — treat like complaints the same way. Inconsistency breeds perceptions of favouritism.
- Keep residents updated — a quick "we're still waiting on the contractor" message prevents residents from assuming nothing is happening.
- Document everything — if a matter does escalate, a well-maintained register demonstrates good faith and procedural fairness.
- Know when to refer — some complaints (particularly inter-lot disputes) are best referred to professional mediation early, before positions harden.
---
Frequently Asked Questions
How quickly should a strata manager respond to a resident complaint?
Best practice is to acknowledge receipt within one business day and provide a substantive response or update within five business days for standard complaints. Urgent matters — particularly those involving safety — should receive a same-day response. Publishing your response timeframes in your building communications sets clear expectations and reduces follow-up pressure.
Does an owners corporation have to investigate every complaint it receives?
Generally, yes — particularly where a complaint relates to a potential by-law breach or common property issue. Failing to investigate and act on legitimate complaints can expose the owners corporation to liability. The depth of investigation should be proportionate to the severity of the issue. Always document the steps taken.
Can a resident remain anonymous when making a complaint?
An owners corporation can accept an anonymous complaint and investigate on that basis, but anonymous complaints can be more difficult to act on formally — particularly if the matter needs to proceed to a breach notice or tribunal. It is good practice to explain this to residents while still assuring them you will look into the matter where possible.
What is the difference between a complaint and a by-law breach notice?
A resident complaint is an informal notification that something may be wrong. A by-law breach notice (or notice to comply) is a formal legal document issued under strata legislation, requiring a lot owner to remedy a specific breach. A complaint often triggers an investigation that may or may not result in a formal breach notice — they are not the same thing and should not be conflated in your communications.
When should a strata complaint be escalated to a tribunal?
Escalation to a tribunal (such as NCAT in NSW, VCAT in Victoria, or the equivalent in other states) is generally appropriate when internal resolution processes have been exhausted, the matter involves a serious or ongoing by-law breach, or there is a dispute about the owners corporation's obligations that cannot be resolved through mediation. Most jurisdictions require evidence of prior attempts to resolve the matter before accepting an application.