How to Track Resident Complaints to Resolution

Every building runs on complaints. A light fails, a lift sticks, a bin is missed, a car is
parked across a gate. In most estates these arrive by message or in person, receive a "noted"
in reply, and from that moment depend entirely on somebody remembering.

The management is usually not careless. The problem is that a message is not a record. It has
no owner, no due date, no state, and no way to tell — a week later — whether anything happened.

To track resident complaints to resolution you need three things, and only three. None of them
requires software.

Give every complaint an identity

A complaint needs a reference, a date, and the name of the person who raised it.

The reference matters more than it looks. Without one, every subsequent conversation begins
with re-describing the problem, and two people discussing "the lift issue" in an estate with
two lifts and three recurring faults are often discussing different things entirely.

A running number with the year in it is enough. Give it to the resident when they report, so
they can refer to it instead of repeating themselves.

Give every complaint one owner

"The team will look at it" is not ownership. Neither is a group chat where four people can see
the message.

Every complaint needs exactly one name attached. That person does not have to do the work —
they may pass it to a contractor, a cleaner, an electrician — but they are the one who answers
the question "where has this got to?".

An unowned complaint is the single most common reason residents feel ignored. Not because
nobody cared, but because everybody assumed somebody else had it. Diffused responsibility feels
like teamwork from the inside and like silence from the outside.

Give every complaint an ending you can defend

Here is the distinction that removes most repeat complaints: a complaint is closed when the
person who raised it has been told it is closed. Not when the work was done.

Those are different moments, often days apart, and only the second one is visible to the
resident. Work completed without notification reads exactly like work not done, and generates a
second complaint about the first one.

Make notification the closing step rather than an optional courtesy afterwards. It costs a
sentence and it removes an entire category of friction.

The six-column log

A spreadsheet with six columns will run a small estate indefinitely:

| Ref | Date | Raised by | What and where | Owner | Closed |

One row per complaint. Add rows, fill the last column, sort by the empty ones.

The discipline that makes it work is filling it in at the moment of receiving the complaint,
not at the end of the day. A log updated retrospectively is a log with gaps, and the gaps are
always the busy days — which are the days that generate the complaints people remember.

Read the open rows, oldest first

Once a week, sort by date and look at the top. That list — the oldest unresolved items — is
your actual agenda, and it takes no analysis to produce.

It is also the honest answer when a committee asks how things are going. Reporting how many
complaints arrived measures how much people are telling you, which is not a measure of service.
Reporting how long the oldest open item has been waiting measures whether you are keeping up.

Watch for the ones that come back

Keep an eye on complaints about something already marked closed. A repeat is not a new
complaint — it means either the repair did not hold, or the underlying cause was never
diagnosed, or the resident was never told.

All three are worth knowing and all three are invisible if you file each report as a fresh
item.

When the spreadsheet starts to strain

The six columns do not stop being the right model. What changes is the cost of keeping them
current.

The strain shows up at recognisable points: when more than one person needs the log open at
once, when you want every complaint ever raised about one unit rather than one month, when
chasing owners becomes its own daily task, or when a committee starts asking for evidence
rather than assurances.

At that point the options are a shared document with proper access, or something that builds
the log from the messages residents and contractors already send — the approach Laksana takes,
which keeps the six columns while removing the person who has to type them in. Either way the
method is unchanged. Only the transcription cost is.