Managing conflict in delivery operations is different from managing it in an office, and the difference is the clock. An argument between two people at desks can wait until Thursday. An argument between your packer and your driver happens eleven minutes before a van has to leave with forty orders on it, and whatever you do in those eleven minutes is the decision.
That pressure is why delivery teams produce a specific kind of friction. Nobody is being difficult for sport. The packer is defending a standard, the driver is defending a route time, dispatch is defending a promise someone else made to a customer, and all three are right about the part of the day they can see. Conflict in this setting is usually a coordination problem that arrived wearing a personality.
This guide covers the whole subject: what the friction costs, the four conflicts that actually show up in an operation that sends its own orders out, which conflict management style fits which situation, how to run the conversation itself, and what to change afterwards so the same fight doesn’t come back on Friday. Two neighbouring subjects get a short summary here and the depth elsewhere. The relationships that bring you accounts in the first place are covered in real networking strategies for businesses that deliver, and the sales habits that decide whether your driver inherits a happy customer or an argument are covered in how to upsell without sounding pushy.
The Bottom Line
- Conflict is expensive long before anyone quits. Acas puts the cost of workplace conflict to UK employers at £28.5 billion a year, just over £1,000 per employee, with recruitment and lost output from people who resign making up the largest share (Acas, 2021).
- It mostly doesn’t get resolved. In Acas polling of 1,081 British employees in August 2025, 44% said workplace conflict had risen over the previous three years, against 13% who said it had fallen (Acas, 2025).
- The retention effect is the one that hurts a small operation. CIPD’s Good Work Index found 33% of employees who had experienced conflict said they were likely to leave within 12 months, against 16% of those who hadn’t (CIPD, 2024).
- Most delivery conflict is structural. If the same argument recurs weekly, you have a routing, load-time or information problem, and no amount of calm conversation will fix a schedule that was never possible.
- Resolve the person and the cause separately. The conversation settles the relationship; a change to the run sheet, the cut-off time or the handover settles the recurrence.
Lower your delivery costs by 23%
How we reduce costs:
- No delivery vehicle expenses
- Optimized local routes
- Pay-per-delivery model
- Average 23% delivery cost reduction
What conflict in a delivery operation actually costs
The bill arrives in four places: the hour you spend on it, the order that goes out wrong while you’re spending it, the person who leaves, and the customer who notices.
The people cost is measurable. Acas estimates that close to 10 million people in the UK experience conflict at work each year, that around 485,800 resign over it, and that replacing them costs employers £2.6 billion in recruitment with a further £12.2 billion in lost output while replacements get up to speed (Acas, 2021). Scale that down to a business with six drivers and one of them walking out in March is a double-digit percentage of your delivery capacity gone in a week, during which the remaining five absorb the routes and start resenting the schedule.
The operational cost compounds quickly, because a distracted handover produces a failed delivery, and failed deliveries are not cheap. Industry estimates put the cost of a failed first attempt at roughly $17 to $18 per order once the redelivery, the support contact and the refund risk are counted, with recipient-not-home and bad address data the two leading causes (Locus, retrieved 2026-10-23). A morning where two people aren’t speaking is a morning where address corrections don’t get passed on.
Then there’s the part nobody invoices. CIPD found that only 54% of employees who had experienced conflict were satisfied with their job, against 77% of those who hadn’t, and that 42% of them felt exhausted always or often, against 18% of colleagues with no conflict to report (CIPD, 2024). Exhausted people drive worse and check less.
The four conflicts that show up when you run your own deliveries
Almost everything in a delivery operation sorts into four recurring arguments. Naming which one you have in front of you is most of the work, because each has a different cause and a different fix.
Driver against dispatch
The classic. Dispatch sees a map and a promise; the driver sees a loading bay, a one-way system and a customer who takes nine minutes to answer the door. The driver thinks the schedule was written by someone who has never parked a van on that street. Dispatch thinks the driver is padding times.
This is an information conflict pretending to be a respect conflict. Neither party has the other’s data. The fix is structural: agreed check-in points, real ETAs rather than optimistic ones, and a route plan built from actual historical stop times rather than straight-line estimates. Training that has dispatchers and drivers role-play each other’s job is a standard recommendation in fleet communication guidance, and it works because it transfers the missing information rather than relitigating the tone (Drive My Way, retrieved 2026-10-23).
Production against the route
The kitchen, the cold room or the packing bench against the load time. Someone is finishing an order at 9:52 for a van that left at 9:45, and someone else is explaining that the order wasn’t ready. This conflict is nearly always caused by a cut-off time that exists on paper but has never been enforced, so both sides have learned a different real deadline.
You against your courier or delivery partner
Different register, same structure. A missed window, a damaged box, a driver who didn’t follow the access instructions. The temptation is to argue about fault; the useful move is to argue about documentation, because better delivery records mean fewer disputes to have. Clear access notes, photo proof of delivery, defined service expectations and a single written channel for exceptions remove most of the ambiguity a partner conflict feeds on.
The customer conflict your driver inherits
The driver is standing at the door being held responsible for a promise made by your website, your order taker or your own optimism. This is the conflict most likely to end up in a public review, and it is created upstream. If your team adds items at the point of order, the way they do it decides what the driver walks into. A helpful suggestion produces a pleased customer, and a pressured one produces someone who feels oversold and takes it out on whoever arrives. The habits that keep that clean sit in the non-pushy approach to upselling an order. Customer complaint handling itself is its own discipline and this post stays out of it; what belongs here is the rule that your driver is never the person who should be defending a commitment they didn’t make.
The five conflict management styles, and when each fits a delivery day
The Thomas-Kilmann model splits conflict behaviour into five styles (competing, collaborating, compromising, avoiding and accommodating), and the practical skill is not having a favourite but picking the one the situation deserves (Indeed, retrieved 2026-10-23). In an operation with a load time, the clock does a lot of the picking for you.
| Style | What it looks like | When it fits a delivery operation | What it costs if overused |
|---|---|---|---|
| Competing | You decide, now, and explain later | Van is loading, two people disagree on load order, something unsafe or illegal is proposed | Team stops raising problems because the answer is always yours |
| Collaborating | Both sides work the problem until there’s a third answer neither side started with | Recurring route friction, cut-off times, how handovers work, done off the clock | Slow; useless at 9:52 with a van waiting |
| Compromising | Each side gives something to keep moving | Two drivers want the same shift, neither claim is stronger | Nobody’s underlying problem gets solved, so it returns |
| Avoiding | You deliberately don’t engage yet | Heated moment mid-shift; park it to a named time today | Becomes neglect fast, and the team reads it as weakness |
| Accommodating | You concede the point | Low stakes, or the other person is simply right | Standards drift, and the loudest person sets the schedule |
Two notes that matter more here than in a generic workplace. First, avoiding is legitimate only with a timestamp attached: “not now, 4 p.m., in the office” is a style; “let’s not make a thing of it” is a decision to let it grow. Second, competing in the ten minutes before a van leaves is not bad management. The error is staying in that mode at 4 p.m., when collaborating is what actually closes the issue.
How to run the conversation: a five-step process
Take it off the floor. A conflict conversation held in front of the packing bench has an audience, and an audience makes both parties defend a position instead of describing a problem.
- Separate the event from the pattern. Ask the person to describe what happened today, specifically, before anybody characterises anybody. “The order left without the two extra boxes” is workable. “He never listens” is not yet a sentence you can act on.
- Listen until you can repeat it back. Active listening in a dispute means playing the other person’s account back in your own words and getting confirmation that you’ve got it, which is the single technique that appears in nearly every piece of credible conflict guidance and the one most often skipped. You cannot do this and plan your rebuttal at the same time.
- Name the interest under the position. The driver’s position is “the route is impossible”. The interest is “I don’t want to be blamed for being late when the plan was wrong”. Those need different responses, and only one of them is about the route.
- Decide what changes, and who changes it. End with a specific, owned, dated action. Not “we’ll communicate better”, but “cut-off moves to 9:30, Maria enforces it, starts Monday, we review in two weeks.”
- Write down what you agreed. One or two lines in a shared place. This is not bureaucracy; it’s what stops the same argument restarting next month with two different memories of the outcome.
Keep the conversation short and the follow-through long. Most of these are fifteen minutes. The part that actually resolves the conflict is whether the agreed change is still in place in three weeks.
Driver and dispatcher communication habits that prevent most conflict
The cheapest conflict management is the fight that never starts, and in a delivery operation that comes down to a handful of routines.
- A morning handover that happens out loud. Two minutes, out loud, covering what’s awkward today: the access problems, the fragile orders, the customer who needs a phone call before arrival.
- Structured check-ins rather than constant ones. Agreed points (loaded, first stop done, halfway, finished), so the driver isn’t being chased and dispatch isn’t guessing. Fleet communication guidance consistently recommends set protocols for updates, delays and exceptions over ad-hoc contact (Cartrack, retrieved 2026-10-23).
- One channel for exceptions. When a delay lives in a text message, a WhatsApp group and someone’s head, the next conflict is already booked.
- Clear ownership of the customer call. Decide, in advance, whether the driver or the office tells a customer they’re running late. Both calling is annoying; neither calling is a complaint.
- Route plans built from real stop times. If your plan says four minutes and the street has always taken twelve, you are not running a schedule, you are running a daily argument.
A dedicated pickup area and a visible order-status screen do the same job physically: separating the handover from the production space reduces the number of interruptions that turn into friction, which is why it’s standard advice for kitchens handling driver pickups (Menuforma, retrieved 2026-10-23).
Delivery scheduling conflicts need a fix to the schedule, not the people
When the same two people clash every Friday, stop treating it as a relationship. Friday is the variable.
Scheduling conflicts have mundane causes: double-booked windows, a cut-off that doesn’t survive a busy morning, two orders promised the same slot, a van with less capacity than the order book. Conflict-prevention guidance for schedule clashes is unglamorous and effective: surface clashes automatically rather than discovering them at load time, check the day’s plan early enough that you still have options, and contact the affected customer yourself with an alternative rather than letting the driver discover the problem at the door.
The test for whether you have a people conflict or a schedule conflict is simple. Swap the people. If the argument happens anyway with different staff, you have a schedule problem, and the mediation you’re doing every week is the cost of not fixing it.
What to do after the conflict is resolved
A resolved conflict is not a neutral outcome; it’s an opportunity, and this is where managing conflict turns into better collaboration rather than just quieter mornings.
Three things make the difference.
Close the loop publicly where the change is public. If the cut-off time moved because a driver raised it, say that’s why it moved. The message that complaints produce changes is the single strongest thing you can do for the next problem being raised early, at the cost of nothing.
Repair the relationship separately from the process. The process change doesn’t automatically fix how two people feel about each other. A short, direct conversation a few days later (“we good?”) does more than another meeting.
Watch what happens to the quiet ones. The people who don’t raise conflict are not necessarily content; CIPD’s data on exhaustion and intention to leave suggests a lot of unresolved friction simply goes underground until someone resigns (CIPD, 2024). In a six-person team, one unnoticed resignation is a capacity crisis.
Communication habits are the substrate under all of this, and they generalise well beyond conflict. The broader set is covered in the communication skills every business should master.
When to escalate, document, or let someone go
Not every conflict is a misunderstanding. Three categories are not conflict management problems at all, and treating them as such is its own mistake.
Conduct, not conflict. Discrimination, harassment, intimidation, anything unsafe. CIPD’s data on the forms conflict takes is a reminder that a meaningful share of what gets filed as “a clash” is a conduct issue needing a formal process rather than a mediated chat: being undermined or humiliated (48%), shouted at (35%), verbally abused (34%), discriminatory behaviour (20%) (CIPD, 2024).
Repeat offenders against a settled agreement. Once is a misunderstanding. The third time, after a written agreement, it’s a performance conversation.
Capability wearing conflict’s clothing. When someone argues constantly because they can’t do the job, more conversation makes it worse. Pay and working patterns were the top two reported causes of conflict in Acas’s 2025 polling, at 25% and 22%, a useful reminder that some conflict is a signal about terms, not temperament, and is solved by changing the terms (Acas, 2025).
Keep a short, factual, dated note of serious incidents and what was agreed. Not to build a case, but to stop the pattern becoming invisible.
Frequently asked questions
What is the first thing to do when two staff argue mid-shift?
Separate them and set a time. Deal with whatever the van or the order needs immediately, make it clear the matter isn’t dropped, and name the hour you’ll handle it today. Postponement with a timestamp is a decision; postponement without one is avoidance.
Should I mediate between my dispatcher and my drivers, or let them sort it out?
Let them try first if it’s a one-off, and step in as soon as it’s a pattern or the operation is being affected. As the owner you’re not a neutral mediator anyway: you own the schedule that usually caused it, which means the fix is often yours to make rather than theirs to negotiate.
How do I handle conflict with a delivery partner rather than my own staff?
Move it from fault to record. Agree what evidence exists for each delivery, what the service expectation actually is, and one written channel for exceptions. Partner conflicts run on ambiguity, and documentation is the cheapest thing that removes it.
Can conflict ever be good for a delivery team?
The useful kind is disagreement about how the work should be done, surfaced early and settled with a change. That’s where better routes and saner cut-offs come from. The damaging kind is personal, repeated and unresolved, and the CIPD retention data is clear about where that ends.
The short version
Conflict in a delivery operation is a timing problem with people attached. The argument happens at the worst moment because that’s when the constraints bite, and the content is usually a coordination failure rather than a character one.
So handle it in two separate pieces. Run the conversation properly: off the floor, listening until you can repeat it back, naming the interest under the position, closing on one owned and dated change. Then go and fix the thing that caused it, because the schedule, the cut-off and the handover are what decide whether you have this conversation once or every Friday. A team that has seen a complaint turn into a changed run sheet raises the next problem a week earlier, which is the whole return on doing any of this well.
