A complaint log is a product backlog.

Most agencies treat complaints as a threat to be minimised, which produces a predictable outcome: complaints are handled verbally by whoever received them, resolved informally, and never written down. The log stays short. Everyone is relieved. And the agency learns nothing, repeats the same failure across four intakes, and eventually meets it as a formal escalation with no record of the three earlier warnings.

An empty complaint log is not evidence of a good service. It is usually evidence of a log nobody uses.

Define a complaint widely.

If you define a complaint as a formal written grievance, you will record two a year. Define it as any expression of dissatisfaction about your service, however it arrived, and you will record something useful. A parent saying "we still have not heard anything" in a messaging app is a complaint about communication. Log it.

This is uncomfortable at first because the number goes up. Say out loud, to the whole team, that the number going up is the goal for the first quarter. Otherwise staff will read a rising count as their own failure and quietly stop logging.

What each entry needs.

• Who complained, and whether they are the student, a parent or a third party.
• The date it was received and the channel it arrived through.
• What they said, in their words rather than a summary that already contains your defence.
• Which student and which stage of the journey it concerns.
• The source of the student, so patterns by sub-agent or by counsellor are visible.
• What was done, by whom, on what date.
• The outcome, and whether the complainant accepted it.
• What changed as a result — the field that turns a log into an improvement record, and the one most often left empty.

Handling one well.

1. 01Acknowledge quickly, in the channel it came in. Most escalation is caused by silence rather than by the original problem.
2. 02Separate the facts from the feeling, and check the facts against the file before responding. This is why dated counselling notes exist.
3. 03Say what you got wrong, plainly, where you got something wrong. Partial admissions read as evasion and provoke exactly the escalation you were trying to avoid.
4. 04Say what you will do and by when. A date is worth more than an apology.
5. 05Close the loop in writing, even when the resolution was verbal.
6. 06Record what you changed, or record explicitly that nothing needed to change and why.

Reading the log as research.

Once a quarter, read every entry in one sitting. Not the summary — the entries. Group them by stage: counselling, applications, visa, pre-departure, post-arrival. The distribution tells you where your service actually breaks, and it is almost never where the team believes it breaks.

Recurring themes in agency logs tend to be mundane: nobody told us this would take this long, we did not know about this fee, we could not reach anyone in August, the person who knew our case left. Every one of those has a structural fix — a status the family can see, a fee schedule given earlier, coverage planned for the crunch, files that are legible to the next person.

Make it easy to complain.

Publish how to complain where a student will actually see it: in the agreement, on your site, and in the pre-departure pack. Say who receives it, how long acknowledgement takes, and what happens if the student is not satisfied with your answer. Say it in the language they are counselled in. A complaints route that only a confident, fluent student can find selects for exactly the complaints you least need to hear, and hides the ones you do.

What a reviewer looks for.

Not a short log. They look for whether entries have outcomes, whether outcomes have dates, whether anything changed as a result, and whether a student would have known how to complain in the first place. A log with twenty entries, all closed, several with a linked change to a process, describes an agency that listens. A log with two entries and no outcomes describes one that does not.