Complaint Report Template
A complaint report template for when somebody is unhappy with the service rather than hurt by it. Each point they raised answered separately as upheld or not, an acknowledgement clock that starts the day the complaint arrives and runs separately from the response clock, and the escalation route written into the reply rather than held back until it is asked for.
- Every point answered separately, not one overall verdict
- Two clocks: acknowledgement, then full response
- The outcome the complainant actually asked for, recorded
- Root cause before closing, or the same complaint returns
Complaint Report
Answered point by point
| # | INVESTIGATION | DONE | BY WHOM | FINDING |
|---|---|---|---|---|
| 1 | Complainant contacted to confirm we have understood it | |||
| 2 | Records reviewed, work orders, helpdesk, CCTV, access logs | |||
| 3 | Service records and SLA performance checked for the period |
The document you will get. Download for the full, editable file.
Who this complaint report is for
One complaint, and three people who each need a different part of it to be right.
Whoever takes the complaint
Sections 1 and 2, in the complainant's own words before anybody interprets them. The field worth slowing down for is what outcome they are asking for, because it is usually smaller and cheaper than the one you would have offered.
Whoever investigates it
The nine investigation steps and the point-by-point findings. Each point gets its own row, its own finding and its own outcome, which is what stops a partly justified complaint being answered as though it were wholly wrong.
Whoever owns the timescales
Two clocks, not one. Days to acknowledge against the acknowledgement target, days to a full response against the response target, tracked separately because they fail separately.
Whoever looks across the year
The Complaint Log, where category and root cause across twelve months is the only view that shows a pattern. A single complaint rarely tells you anything on its own.
Where complaints concentrate
The structure suits any occupied building. What changes is who is entitled to complain and what happens if you get it wrong. If you run one of these, the sector page goes further than the template does.
- Commercial real estate
Multi tenant buildings, where a complaint about the common parts is really a service charge conversation waiting to happen.
Portfolio maintenance software - Corporate facilities
Occupied offices, where comfort and cleanliness dominate and the volume is what makes patterns readable.
Corporate facilities software - Retail and malls
Trading environments, where a complaint from a tenant and one from a member of the public need different handling and different timescales.
Retail maintenance software - FM service providers
Contracted delivery, where complaint handling is usually a contractual obligation with its own reported timescales.
FM service provider software - Education
Campuses, where the complainant may be a student, a parent or a member of staff, and the escalation route differs for each.
Campus maintenance software - Healthcare
Clinical settings, where a facilities complaint can carry a statutory escalation route that a service complaint ordinarily would not.
Healthcare maintenance software
What a complaint report should contain
A complaint report is the record of somebody being dissatisfied with a service, and of what was done about it. It captures the complaint in their own words, the outcome they are asking for, an acknowledgement and a full response against separate targets, a finding against each point raised, the remedy offered and the root cause behind it.
A. The sections that carry the weight
| Field | What goes in it | Why it earns its place |
|---|---|---|
| Complaint details | Reference, when it arrived, who took it and how it reached you | How it reached you matters more than it looks. A complaint arriving by survey or social media has usually already been through a stage you never saw. |
| Who is complaining | Tenant, occupant, visitor, client, staff or contractor, and how they prefer to be contacted | The complainant type sets the escalation route. Anonymous is a valid answer here, recorded with the note that no response is possible. |
| What the complaint is about | Category, their own words, when it happened and where | Their own words, before interpretation. The paraphrase written at intake is what gets disputed later when the response does not match what they think they said. |
| What outcome they are asking for | Asked explicitly, not inferred | The single most useful field in the document. Most complaints are resolved by the thing the person actually wanted, and it is usually smaller than the remedy you would have offered unprompted. |
| Acknowledgement | The target, the date, who by, and whether it was met | A policy target rather than a per complaint decision. Most complaints escalate because of silence, so this section exists to make silence visible. |
| Investigation | Nine steps from confirming the complaint to reviewing similar past ones | The last step is the one people skip. A complaint that matches three others from the same floor is a different problem from a one-off. |
| Findings, point by point | Each point raised, what was found, the outcome and the evidence | The reason this document exists. Outcome is Upheld, Partly upheld, Not upheld or Inconclusive, spelled exactly that way so the counts underneath mean something. |
| Outcome and remedy | The apology, what is being put right, work orders raised and what was authorized | The line worth keeping is what you cannot do and why. An unmet expectation left unexplained comes back, usually to somebody more senior. |
| Response and escalation | When the response went, whether they accepted it, and the route onward | Including the external body and its deadline. Tell them how to escalate in the response rather than on request. |
| Timeliness | Days to acknowledge and days to respond, each against its own target | Two measures because they fail independently. A team can acknowledge everything inside a day and still take six weeks to answer. |
| Learning | Root cause, whether it is a pattern, and what changed | The only part of the document with any value after the file is shut. A complaint closed without a root cause is one you will receive again from somebody else. |
| Sign-off | Investigated by, approved by, and how long it is retained | Retention matters where a complaint can be reopened by an ombudsman or a regulator long after you considered it closed. |
The point-by-point findings table is the decision that separates a complaint process that settles things from one that generates escalations. A complaint is rarely about one thing. Somebody writes in about the washrooms, and inside that are three separate assertions: they were not cleaned on particular mornings, nobody answered when it was first raised, and the contractor was rude when challenged. Answering all of that with a single overall verdict fails whichever way it lands. Uphold it and you have conceded points that were not true; reject it and you have dismissed one that was. Either way the complainant reads the response, sees that the part they most cared about was not addressed, and escalates, which is the outcome the process existed to avoid. Answering each point on its own line, with its own evidence and its own outcome, costs a few extra minutes and removes most of that. The second decision is keeping the two clocks apart. Acknowledgement and response are different promises: one says we have your complaint and here is when you will hear, the other answers it. Running them as a single target hides the failure that actually causes escalation, which is silence in the first week.
B. What it looks like filled in
One complaint through the process. The acknowledgement went out the next day, which is the reason this one never escalated.
| Line | Value |
|---|---|
| Reference | CMP-2027-0074 |
| Complaint | Washrooms not cleaned, Northgate House |
| Working days to acknowledge | 1, against a 2 day target |
| Working days to full response | 6 |
| Root cause | Cover not arranged for absence |
| Escalated | No |
The complaint was upheld, and it still did not escalate. That combination is worth noticing, because the instinct is to treat an upheld complaint as a failure of the service and a rejected one as a success of the process. It is the other way round more often than not. This one was acknowledged the next working day against a two day target, which meant the complainant knew within twenty-four hours that a person had it and when they would hear back. Six working days later they got a response that addressed what they raised and named the root cause, which was that cover had not been arranged for an absence rather than that a cleaner had been careless. The root cause is what makes the last line of the record worth anything. A complaint closed as washrooms not cleaned teaches nobody anything and will arrive again from a different floor. A complaint closed as cover not arranged for absence points at a rota, and that is a thing somebody can actually change.
Word for a version you want to hand to whoever is investigating, Excel for the one that counts the outcomes and holds a Complaint Log for reading patterns across the year, and PDF for the copy that goes in the file. Free, and yours to rebrand.
How do you handle a facilities complaint?
The handling matters more than the form. Acknowledge early, answer each point separately and find the root cause before you close it. Six steps.
Record it in their words, and ask what they want
Capture the complaint before anybody paraphrases it, then ask explicitly what outcome they are looking for. It is usually smaller than you expect and it is frequently the entire resolution.
Acknowledge inside your published target
Set the target as a policy rather than per complaint, and acknowledge even when you have no answer yet. Tell them when they will get a full response and record that you told them.
Separate the complaint into its points
Most complaints contain several assertions. Break them out before investigating, because a point that was never identified cannot be answered and is the one that gets escalated.
Investigate each point against evidence
Work orders, helpdesk records, attendance, CCTV, access logs and the service performance for the period. Review similar past complaints, because a pattern changes both the finding and the remedy.
Answer every point, then set the remedy
Mark each outcome as Upheld, Partly upheld, Not upheld or Inconclusive. Say plainly what you cannot do and why, and give the escalation route in the response itself.
Find the root cause before closing
Not the event, the reason the event was possible. A complaint closed without one is a complaint you will receive again from somebody else on a different floor.
A complaint versus an incident
Two records that get confused constantly, and the difference is not how serious it is. It is whether somebody was harmed or something was damaged.
| Aspect | A complaint | An incident |
|---|---|---|
| What happened | Somebody is dissatisfied | Somebody was hurt or something was damaged |
| The first question | What outcome do you want | Is anybody still at risk |
| What drives the timescale | A published acknowledgement target | Immediate action, then a reporting deadline |
| Who may have to be told | An ombudsman or the client | A regulator, an insurer, sometimes both |
| How it is answered | Point by point, upheld or not | Root cause and corrective action |
| What it must never become | A file with no root cause | A complaint record |
If somebody was hurt, or something was damaged, use an incident report rather than this one. The distinction is not severity and it is not tone. A furious complaint about a contractor blocking a fire door is still a complaint; a quiet note about a visitor who tripped on the same obstruction is an incident, and it carries reporting duties that a complaint does not. Logging an injury as a complaint is the version of this mistake that causes real harm, because the clock that matters is a statutory reporting deadline and nobody started it. The reverse happens too, less dangerously but more often: a service complaint entered as an incident goes to a safety team who have no way to resolve it, and the complainant hears nothing for a fortnight. Keep the two routes separate, say on each which one to use, and accept that some records will need to be both.
When the template starts to feel limiting
The file is built for one site handling a manageable number of complaints. Four things start to hurt as soon as that is not the shape of the problem.
Nothing watches the two clocks
Both targets are recorded and neither is monitored. A complaint drifting past its response date is discovered when the complainant chases it, which is the moment the process was meant to prevent.
The complainant cannot see progress
Once acknowledged, the file is invisible to the person who raised it. Every status question becomes a phone call, and silence is what turns a complaint into an escalation.
Patterns only appear if somebody looks
The Complaint Log holds the categories and the root causes, but nothing surfaces the third complaint about the same floor unless a person happens to sort the sheet.
The complaint and the work that fixed it stay separate
A remedy raises work orders, and those live somewhere else. Whether the thing you promised was actually done is a second lookup nobody makes.
What running this in Facilio looks like
The handling does not change. What changes is that the clocks run on their own and the pattern surfaces without anybody sorting a spreadsheet.
Ops Performance Intelligence
Both clocks run without supervision
Acknowledgement and response carry their own targets, so a complaint drifting past either one surfaces before the complainant chases rather than after.
Work Order Intelligence
The remedy stays attached to the complaint
Work raised to put something right stays connected to the complaint that prompted it, so whether the promise was actually delivered is visible on the record.
Audit Report Intelligence
Patterns read themselves
Because every complaint carries a category, a site and a root cause, the third one about the same floor is recognizable as a pattern rather than as three unrelated files.
Asset Intelligence
Complaints attach to the building
A run of comfort complaints against one area reads against the plant serving it, which is usually where the answer is.
Hallucination-free by design. Atom AI answers from the records in your tenant rather than generating plausible text, so an empty field reads as empty rather than filled in for you.
Frequently asked questions
What is a complaint report?
It is the record of somebody being dissatisfied with a service and of what was done about it. This one captures the complaint in the complainant's own words, the outcome they are asking for, an acknowledgement and a full response against separate targets, and a finding against each point raised.
It closes with a root cause and whatever changed as a result, which is the only part of the record that has any value once the file is shut.
What is the difference between a complaint and an incident?
A complaint is dissatisfaction with a service. An incident is somebody being hurt or something being damaged. The difference is not how angry the person is or how serious it sounds, and a calm note about a trip hazard is an incident while a furious letter about cleaning is a complaint.
Incidents carry reporting duties and deadlines that complaints do not, so use an incident report for those. Some events genuinely need both records.
Why answer each point separately?
Because a single overall verdict on a complaint that raised four things satisfies nobody. Uphold it and you concede points that were not true; reject it and you dismiss one that was.
Either way the complainant sees that the part they most cared about was not addressed, and escalates. Answering each point with its own evidence and its own outcome removes most of that.
What outcomes should a complaint point be given?
Upheld, Partly upheld, Not upheld or Inconclusive, spelled exactly that way so the counts underneath the table mean something. Inconclusive is a legitimate answer and is better than forcing a finding the evidence does not support.
An overall outcome is recorded separately, but it is a summary of the points rather than a replacement for them.
How quickly should a complaint be acknowledged?
Set it as a policy rather than deciding per complaint, and acknowledge inside it even when you cannot answer yet. Two working days is a common target and the template treats it as a separate promise from the full response.
Most complaints escalate because of silence rather than because of the original problem, which is what the separate acknowledgement clock is there to make visible.
Should you tell somebody how to escalate?
Yes, in the response itself rather than when they ask. Withholding the route does not reduce escalations, it just means the first the ombudsman or the client hears about it comes from the complainant.
Giving it also tends to slow escalation down, because a complainant who knows the route exists is more willing to let you finish first.
What should go in the root cause?
Not the event, the reason the event was possible. Washrooms not cleaned is the event; cover not arranged for absence is the root cause, and only one of those points at something anybody can change.
A complaint closed without one will arrive again from a different person about a different floor, and nobody will connect the two.
Can this be used for staff grievances?
No. This is built for complaints about a facilities service, with categories like cleanliness, temperature, noise, access and contractor conduct, and every example in it is a building example.
Staff grievances run through an HR process with different rights, different confidentiality and different escalation, and putting them through a facilities complaint file is a mistake in both directions.
In one paragraph
A complaint report works when each point raised is answered on its own line rather than under a single overall verdict, because one verdict on a complaint that raised four things satisfies nobody. Acknowledge inside a published target and treat it as a separate promise from the full response, since most escalations come from silence rather than from the original problem. Ask what outcome the complainant actually wants, and find a root cause before you close it.
The last section is the only one worth anything later
Answer each point, keep the two clocks apart, and write a root cause rather than a description of the event. Once nothing is watching the response date, or the same complaint keeps arriving without anybody connecting them, the file has done what it can.
