Your drivers carry your product, your customers’ trust and often your cash. They work alone, all day, on roads you are not on. You cannot stand next to them, and you should not try to. Calling a driver every hour makes him slower and angrier, and it still does not tell you what happened at stop number nine.
The better approach is to agree a small set of facts that are recorded every day, review them together at the end of the day, and keep the rules the same for everyone. This guide covers what to measure, how to keep it fair and what to do when something goes wrong.
Why accountability fails
Most owners start with suspicion. Jars are missing, cash is short, so the driver must be the problem. Sometimes he is. More often, the system is. If nobody wrote down what the driver was meant to deliver, what he took back and what he collected, then nobody can show where the gap came from. The driver feels accused and the owner feels cheated, and neither has facts.
Accountability works when it is built on records that both sides can see. The goal is that a gap can be traced to a stop, a day and a reason, without anyone shouting.
What to measure for each driver, each day
Keep the list short. Four measures cover most of what matters.
1. Stops done
How many stops were planned, and how many were completed. This is the basic shape of the day. A driver who completes eleven of twelve stops is doing fine. A driver who completes six of twelve every day needs a conversation about the route, the vehicle or the workload.
2. Skips with reasons
A skipped stop is normal. Customers are away, shops are shut, gates are locked. What matters is that every skip has a reason. “Customer not home,” “shop closed,” “customer said no jars needed” and “could not reach, vehicle problem” are all useful. A skip with no reason is a skip you cannot judge. Make the reason a rule, and follow up on patterns. If the same customer is skipped three days running, someone should call that customer.
3. Short and extra
Compare what was planned with what was delivered. If the plan said two jars and the driver left one, that is a short of -1. If he left four, that is an extra of +2. Neither is wrong by itself. Customers change their minds. But each difference needs a cause you can name. The guide on short and extra deliveries goes through the usual causes.
4. Empties returned
How many empty jars the driver brought back, stop by stop, and in total against the jars he took out. Empties are money. Each missing jar is a replacement cost. Count empties on every stop, including skipped ones, since a customer may hand empties to the driver even when the delivery did not happen. See empty jar tracking for the full method.
These four give you the day. Add cash collected if drivers collect, but resist adding a dozen more measures. A driver who has to fill in twenty things will fill in none of them properly.
Rules that drivers accept as fair
Drivers can tell very quickly whether rules are fair. They will follow fair rules, and they will work around unfair ones. A few principles help.
- Same rules for everyone. If one driver may skip without a reason and another may not, the second will resent it and the first will take advantage.
- Rules you can explain in one sentence. “Every skip gets a reason. Every stop gets an empties count.” If you need a page to explain it, it is too complicated.
- Count the problem, not the person. “Six jars did not return this week” is a fact. “You are stealing jars” is an accusation. Start with the fact.
- Allow for honest error. A miscount happens. Set a tolerance for small differences, and agree it in advance. A driver who is punished for every single jar will stop recording honestly.
- Reward consistency. If a driver completes his stops, records every skip and returns his empties, say so. Respect is part of the control system.
- Explain why you record. Tell drivers the records protect them too. When a customer says “you never came,” a recorded stop is the driver’s defence.
The close-of-day review
A short review at the end of the day does more than any amount of calling during it. Ten minutes, per driver, every day.
- Stops. Planned against completed. Any left over, and why?
- Skips. Read the reasons. Anything unclear, ask now, while he remembers.
- Short and extra. Look at each difference. Was it the customer’s request, or a problem?
- Empties and bottle balance. Jars out, jars back. Does it add up?
- Cash, if relevant. What was collected, and does it match what was recorded?
Ask open questions. “What happened at the third stop?” gets a better answer than “why did you skip?” Most differences have a boring explanation, and you learn it in thirty seconds.
Lock the day
Once the review is done and the numbers are agreed, close the day. Locking the day means the figures stop changing. This matters for two reasons.
First, it gives you a clean record. A number that can be edited next week is not a record. Second, it protects the driver as much as you. Nobody can say later that the day looked different. If something was wrong, it is raised that evening, corrected before locking and noted.
Make the lock a habit with a fixed time. If a correction is needed after locking, handle it as a separate, visible change and not as a quiet edit.
Handling a dispute with a driver
Disputes will come. A jar count does not match, or a customer complains, or cash is short. A calm process matters more than the outcome of any one dispute.
- Look at the record first. Find the stops behind the number. Most disputes shrink when you see the actual entries.
- Talk privately. Never raise it in front of other drivers or customers.
- Ask for his account. Listen to the whole version before you respond. Take notes.
- Check the record against his account. If they agree, the issue may be the customer, the plan or the process.
- Separate error from pattern. One miscount is a mistake. The same difference every Friday for a month is a pattern.
- Agree one action. A clear next step, with a date to review. “Count empties at the door before leaving,” for example.
- Follow up. Come back on the date and say whether it worked.
If a pattern is real after fair review, act on it. A fair process means that when you do act, nobody is surprised and the rest of the team sees that the rules mean something.
Language matters
Many drivers read Hindi more easily than English. A record-keeping tool they cannot read well will be filled in badly or skipped. If your drivers are more comfortable in Hindi, use tools and paper forms in Hindi. Accuracy depends on understanding.
How Pyaau helps
Each driver gets the day’s route, built every night from customers and standing orders. The driver swipes a stop delivered or skipped. A skip needs a reason, and empties are kept on a skipped stop. On a stop he sets jars delivered and empties taken back, and a one-tap Match sets empties equal to the jars delivered. Short and extra show on the stop as -1 or +2. The office gets a close-of-day summary with delivered, skipped, extras, empties, bottle balance, short jars and above planned, and can use Lock Run to close the day. The app can run in Hindi.
The office and the driver are two roles in the same Android app.
If you run several drivers, running multiple delivery routes covers how to split the work. The for drivers page describes what the driver sees.