How to Handle a Complaint Against Your Licence

Why this matters

A complaint filed with your licensing authority is not a customer service problem that arrived in an official envelope. It is a proceeding with a deadline, a file that outlives the dispute, and an outcome that can attach to your licence for years. Shops lose these on process far more often than on facts: a missed response window, a defensive phone call to the complainant, or a job file that somebody tidied up after the notice arrived.

The first hour matters more than the next month. This is what to do in it, and in the four weeks after.

Step 1: Read the notice for exactly three things

Resist reading it as a person for now. Read it as a file, and extract three items before you form an opinion.

The deadline. The date and the exact count of days, and whether the count runs from the date of the letter, the date of service, or the date of receipt. Those produce different dates and the letter will say which.

The allegation as worded. Copy it out verbatim. Not your understanding of it, not the customer's story as you know it. The words in the notice define the scope of everything that follows, and your response is judged against them.

The file number and the assigned contact. Every subsequent communication references the number.

Everything else in the letter, including whatever it says about the underlying job, waits. Reading emotionally first is how shops end up drafting a response to the complainant's narrative rather than to the allegation, and those are frequently different documents.

Step 2: Calendar the deadline and confirm the channel

Put the deadline in a shared calendar with a buffer, not on the deadline itself. A working default is to set your internal due date at 70% of the window, so a 21-day window has an internal due date at day 15, leaving 6 days for a problem you have not thought of yet.

Then confirm how the response must arrive. A timely response delivered through the wrong channel is a late response. If the notice specifies a portal, use the portal, and keep the submission confirmation.

Step 3: Preserve everything before you touch anything

Say this to the whole shop the same day: nothing related to this job gets edited, deleted, tidied or reorganised.

That covers the job file, dispatch and scheduling records, time entries, photos, texts and voicemails on personal phones, invoices and estimates, and any note fields in your system. It includes well-intentioned cleanup. A tech who rewrites a sloppy note to be clearer has done more damage than the sloppy note ever would, because software keeps change history and the change is discoverable.

What you may do is add. New notes, dated as new, clearly recording what you know now. Adding is documentation. Editing is alteration, and the two are read entirely differently.

Then capture the material out of any system where it could roll off: text threads, call logs, telematics or GPS records with retention windows shorter than this will take. Do that in the first week, because a 90-day retention window and a 6-month proceeding do not overlap.

Step 4: Notify your insurer and, if a bond is involved, your surety

Do this early, and do not wait until you have decided whether the complaint has merit.

Most liability policies require notice of a claim or a potential claim as soon as practicable, and a claims-made policy requires the notice inside the policy period, so a delay while you assess the merits can cost you the defence coverage you would otherwise have had. Read your own policy's notice clause rather than assuming, and send the notice in writing.

If the complaint could produce a claim on your licence bond, the surety gets notice too. The bond claim runs on a separate track with its own consequences, including your obligation to repay the surety anything it pays out. See related: The Bonds and Insurance That Usually Ride With a Licence.

Step 5: Decide whether to bring counsel

Bring counsel, before drafting anything, if any of these are true:

• The allegation as worded could support suspension or revocation rather than a citation or corrective order
• It alleges fraud, misrepresentation, or unlicensed activity, which are the categories authorities treat most severely
• The same facts are also in a lawsuit, or you expect them to be
• The complaint involves an injury, or a condition that could have caused one
• The authority has asked for an interview rather than a written response

A well-documented self-response is usually proportionate for a workmanship or communication allegation with no injury, no dollar dispute in litigation, and no pattern behind it. That is a real category and most complaints fall in it.

The middle path is worth naming: have counsel review a response you drafted, rather than have them draft it. It costs a fraction of the time, and the review catches the two things owners get wrong, which are admitting a legal conclusion by accident and answering a question that was not asked.

Step 6: Write to the allegation, not to the story

Structure the response in four parts, in this order.

What was asked of us. The scope of work as it was actually agreed, sourced to the estimate or work order.

What we did. Dated, factual, sourced to records. No adjectives.

What the record shows about the specific allegation. This is where you address the wording you copied out in step 1, point by point.

What we propose. If anything.

Attach the artifacts, number them, and reference them by number in the text. A reviewer who has to hunt for the evidence supporting a sentence is a reviewer who discounts the sentence.

Two things to keep out. Do not characterise the complainant. A response describing a customer as difficult reads as a shop that had a problem with a customer, which is the impression you least want in a file. And do not argue about matters the authority does not decide; a fee dispute is not usually within their statute and raising it signals you have misread the forum. See related: What a Licence Complaint Process Usually Looks Like.

Step 7: Separate the remedy offer from the admission

You can offer to return and correct work without conceding that a violation occurred, and you should say so explicitly rather than leaving it to be inferred. Language along the lines of "without accepting the characterisation in the complaint, we have offered to return and complete the following" does that work in one sentence.

Whether to offer at all is a judgement. An offer that resolves the customer's actual grievance often resolves the complaint, because many authorities will close a matter where the consumer is satisfied and no independent violation is alleged. An offer made where the allegation is about conduct rather than workmanship does not help and can read as buying silence.

Worked example: a workmanship complaint answered on the record

The allegation, verbatim from the notice: the shop "never returned after 14 March despite repeated promises" and left the work unfinished.

Scope. The response opened with the signed work order, one page, defining the work.

The record. The shop pulled everything covering the 9 weeks from 14 March to the complaint date. It found 4 documented contacts in that window: 2 site visits and 2 phone calls.

The 2 site visits were solid. Both had dispatch records with arrival and departure times, and one had photographs with embedded dates. On the second visit the customer was not home; the tech's note recorded a knock, a wait, and a card left, and the dispatch record showed 22 minutes on site, which is consistent with that note and not with a no-show.

The 2 calls were not equally solid, and the response said so rather than counting them alike. One had a note in the job file recording what was discussed. The other existed only as an outbound call-log entry with a duration, which proves a call was placed and connected and proves nothing about what was said. The response presented it as exactly that. Overstating a weak artifact is how an otherwise credible response gets discounted in full, and a reviewer who catches one overstatement re-reads everything else looking for more.

The gap the response had to own. Between the second visit and the complaint, 5 weeks passed with 1 call and no scheduled return. That is a real service failure even though it is not the failure alleged, and the response named it plainly rather than letting the reviewer find it. The allegation said "never returned"; the record showed 2 returns, so the allegation as worded was not accurate, and the shop's actual failure was a different one that the record made obvious. Saying so is stronger than a clean denial, because the reviewer is going to reach the 5-week gap either way.

Outcome. Informal resolution: a corrective visit on a scheduled date, confirmed in writing, and the matter closed with no finding entered. That is one outcome among several available, and the authority chooses from its own ladder, not from your proposal.

What changed inside the shop. Not a policy about complaints. A rule that any open job with no scheduled next step gets flagged after 10 days, because the 5-week gap was not a decision anyone made, it was a job that fell out of the schedule and nothing was watching for that.

How to verify you handled it right

Three checks after the response goes in.

Confirm receipt, by the channel the notice specified, and keep the confirmation with the file. Submitted is not received.

Diary the next date. If the authority told you when to expect a response, calendar it and follow up if it passes. Silence is not closure, and a matter you assume closed can surface at your next renewal.

Then run the internal question, which is separate from the regulatory one and easy to skip once the pressure lifts: what in your process allowed this to reach an authority rather than being resolved with the customer. In most cases the answer is a communication gap with a date on it, and it is findable. See related: How to Close the Loop After a Complaint.

References

• Your state or local licensing authority, for response deadlines, service rules, permitted channels and its own complaint procedure
• Your liability policy's notice-of-claim clause and your surety's claim notice requirements, which govern how quickly you must report
• See related: What a Licence Complaint Process Usually Looks Like; The Bonds and Insurance That Usually Ride With a Licence; How to Keep Credential Records That Survive an Audit