Grievance Management for the Complaint That Becomes a Resignation
Drivers are the hardest role in transport to keep. A complaint about pay, a vehicle or a supervisor that has nowhere to go does not disappear — it leaves. KO Fleetz gives the complaint a place to land, a type, an owner and an escalation rule that moves it before the man moves on.
He did not resign on Tuesday. He resigned in March.
A driver stops at the office window on his way out of the yard. The clutch has been slipping for a month, he says, and he has mentioned it twice. The supervisor is on a call. The driver waits, then leaves, because a load is waiting and he has done this before. Nothing about that conversation exists anywhere.
Repeat it four times over a season, across an advance that came late, a route he was promised and did not get, and a supervisor who spoke to him in front of other men. None of it was serious enough to escalate on its own. All of it was noticed. In August he takes a job with the operator two kilometres down the road for a marginally worse rate and does not explain why.
The exit interview, if one happens, produces the word 'personal reasons'. Management concludes it was money and raises the rate, which is expensive and often wrong. The real trail was four small things that were each said once, to someone busy, and written down nowhere.
A place for it to land and a rule that moves it
KO Fleetz raises a grievance as a record with a type behind it. Typing matters, because a complaint about a vehicle, a complaint about pay and a complaint about a person are three different problems with three different owners, and lumping them into one suggestion box guarantees none of them reaches the right desk. The types are yours to define against the things your drivers actually raise.
Escalation rules are the part that does the work. A grievance that nobody has touched does not sit in an inbox indefinitely — the rule moves it up, by type and by age, to a named person above the one who has not answered. That is the whole mechanism, and it exists because the common failure is not refusal. It is a supervisor with eleven trucks and no time, and a complaint that quietly ages out.
Drivers get their own view, separate from the management one, so a man can raise something and see where it went without asking the person he is complaining about. Feedback closes the loop back to him. Be clear about what this cannot do: it will not fix a slipping clutch, settle a pay dispute or manage a supervisor. It is a channel and a record. The fixing is still done by people, and a fleet that turns this on and answers nothing has built a faster way to disappoint drivers.
Capabilities
What KO Fleetz grievance management gives your team
Grievance types you define
Vehicle condition, pay and advances, roster and route, conduct. A complaint routed by its type reaches someone who can act on it rather than a general inbox.
Escalation rules by age and type
An untouched grievance moves up to a named person above the one who has not answered, which addresses the real failure: not refusal, but a busy supervisor.
The driver's own view
A separate view where an employee raises his grievance and follows it, without having to ask the supervisor he may be complaining about where it went.
Feedback back to the person
The outcome returns to whoever raised it. A complaint answered badly still teaches a driver the channel works; one answered with silence teaches him it does not.
Attribution and timestamps
Who raised it, who held it, how long each of them held it. That trail is what turns a disputed history into a readable one months later.
Restricted visibility
A grievance about a supervisor should not be readable by that supervisor. Permissions on the record are the thing that decides whether anyone uses this twice.
Pattern by type and depot
Six vehicle complaints from one yard is a maintenance signal. Six conduct complaints naming one man is a different signal entirely, and neither is visible one at a time.
Open and ageing list
What is outstanding and how long it has been outstanding, on one screen, so nothing depends on a manager remembering an unwelcome conversation.
Sits with the employee record
KO Fleetz keeps grievances against the same person as attendance and role, so the history is one history rather than a folder somebody keeps separately.
How it works
How KO Fleetz does it
Step 1: Name the types honestly
Write the categories against what your drivers actually raise, including the awkward one about supervisors. A type list that omits conduct is a decision, and drivers read it as one.
Step 2: Give every type an owner
Each category needs a named person, not a department. A grievance addressed to the workshop is a grievance addressed to nobody, and it will sit until the escalation rule rescues it.
Step 3: Set the escalation clock
Decide how many days a type may sit before it moves and who it moves to. Set it to a period you will actually honour rather than an ambitious one you will mute by month two.
Step 4: Tell drivers it exists and then answer them
The first ten grievances decide whether there is an eleventh. Answering them, even to say no, is what builds the channel. Ignoring them closes it permanently.
Outcomes
What changes
- Somewhere for the complaint to land
- A channel
- Escalation by age, not by memory
- It moves
- Who held it, and for how long
- Attributed
- Six complaints read together, not one at a time
- Patterns
Frequently asked questions
On its own, no, and we are not going to pretend otherwise. Software cannot pay a man more, mend the clutch he keeps reporting, or make a supervisor speak to him decently. What it does is make sure the complaint reaches someone with the authority to do one of those things while it is still a complaint. A fleet that raises grievances and answers none of them will have the same attrition it has today and a worse reputation, because the driver now knows he was heard and ignored rather than merely unheard.
Most of them will keep doing exactly that, and that is fine. The channel is not there to replace the conversation at the office window; it is there for the ones that conversation cannot carry — a complaint about the supervisor himself, or a third repetition of something that went nowhere twice. Expect volume to be low. Low volume is not failure here. One recorded grievance that stops a man from leaving in August is worth more than a hundred tickets nobody meant.
Permissions and the escalation rule, and this is the single design decision that determines whether the module gets used. A conduct grievance is typed as one, routed to an owner outside that reporting line, and restricted so the person named cannot read it. Set this up wrong on day one and you will get one grievance, ever. Drivers talk to each other about what happened to the first man who tried it, and that conversation is faster than any rollout you have planned.
Not by default, and there is a real trade-off worth thinking about. A named grievance can be investigated, answered and closed with the person who raised it — an anonymous one often cannot, because the follow-up questions have nowhere to go. Anonymity buys you complaints that would otherwise never be made, and it costs you the ability to resolve most of them. Fleets tend to want it most for exactly the category where investigation matters most. Decide that policy deliberately rather than discovering it after the first serious allegation.
A register records. It does not move. KO Fleetz adds the escalation rule: a complaint sitting untouched for a week goes up to somebody else automatically, and it does so whether or not the person holding it is having a good month. Almost every grievance register in a transport office dies the same way, which is not malice — it is a supervisor with eleven trucks, a compliance deadline and a driver short, who genuinely intended to get to it. The rule is what survives that.
It gives you a dated record of what was raised, when, who held it and what was said back. That is more than most fleets have and considerably better than a reconstruction. It is not legal advice, it is not designed around any particular statutory process, and it will not tell you what your obligations are under Indian labour law. Talk to your own counsel about what you must record and retain. What we will say is that the record cuts both ways honestly, which is the point of keeping it.
Give the complaint somewhere to go
Tell us the three things your drivers raise most and who currently hears them. We will map them into KO Fleetz and show you what the escalation rules would look like against your own reporting lines.