Rejected loads: what to do when a receiving site turns your waste away

A rejected load is one of the more awkward situations in waste operations, because it combines a commercial problem, an operational problem and a compliance problem in a single vehicle that is currently sitting on someone else's weighbridge with nowhere to go.

The commercial problem is obvious. The operational one — a driver, a vehicle and a round now disrupted — is manageable. The compliance problem is the one that gets handled worst, because the instinct in the moment is to find somewhere else to tip, and the decisions made in the next hour end up documented in a way nobody intends.

Why loads get rejected

Rejections cluster into a small number of causes, and knowing which one you are dealing with determines what happens next.

• –Contamination: the load contains material the receiving site is not permitted to accept, or that takes the load outside the description it was consigned under.
• –Misdescription: the paperwork says one thing and the load is another — frequently a classification judgement made at the point of collection that does not survive inspection.
• –Permit limits: the site is permitted for the material but has reached a limit, or cannot take that material that day.
• –Documentation: the transfer or consignment paperwork is incomplete, inconsistent or missing.
• –Carrier status: a check at the gate finds the carrier registration is not current, or does not cover what is on the vehicle.

The distinction that matters most is between a load that is wrong and a load that is right but inconvenient. A site at its daily limit is a scheduling problem. A load containing something it should not contain is a duty of care problem, and it does not stop being one because another site is willing to take it.

The hour after a rejection is where compliance is won or lost

The temptation, particularly late in a shift, is to ring round for somewhere that will take it. Sometimes that is the correct answer — if the rejection was capacity-related and the alternative site is properly permitted for the material, re-routing is simply operations.

Where it goes wrong is when a load rejected for contamination or misdescription is taken elsewhere without the underlying issue being resolved. At that point the business is knowingly moving waste that it has been told is not what the paperwork says it is, which is a materially different position from the one it was in that morning. Duty of care obligations follow the waste rather than the inconvenience, and what duty of care actually requires does not contain an exception for a difficult afternoon.

The safer sequence is: establish the reason for rejection and get it in writing from the receiving site, decide whether the load can be lawfully and accurately described for an alternative outlet, and only then move it. If the description has to change, the paperwork has to change, and that change needs to be a documented correction rather than a quiet rewrite.

What to record, at the time

• –Date, time and which site rejected it, with the name of the person who made the decision.
• –The stated reason, in the receiving site's words, and any documentation they issued.
• –The original description and classification the load travelled under.
• –Photographs of the load where contamination is alleged — taken at the point of rejection, not later.
• –Where the load went next, under what description, and with what paperwork.
• –Which collection or collections the material came from, if that can be established.
• –What the customer was told, and when.

The sixth item is the one that pays for itself. A rejection is evidence about a collection point, and it is only useful if it can be traced back to one. For a round that has tipped several customers' waste into one vehicle, this is harder — which is itself an argument for knowing what went on the vehicle and in what order.

The paperwork problem is usually upstream

Rejections for misdescription are rarely a surprise to anyone who looks at how the description was arrived at. Classification decisions are frequently made quickly, at a customer site, by a driver who is not a waste classification specialist and who has a round to finish. The code that goes on the paperwork is often the code that was used last time.

That works until a load contains something that changes the position. How waste classification and EWC codes work covers the framework, and the relevant guidance is the authority for anything specific — but operationally, the useful question after a misdescription rejection is not "who got it wrong" but "at what point in our process was that decision made, and with what information".

Similarly for documentation rejections: a transfer note that is incomplete at the gate was incomplete when it was created, and the gate is simply where it was first checked. What a compliant transfer note has to contain is the reference; the operational lesson is that your own check should be earlier than the receiving site's.

Receiving sites are a relationship, not just a destination

Firms that rarely get loads rejected generally have better information about their outlets than firms that do. Not just what a site is permitted to accept in principle, but what it will actually take, what its tolerance for incidental contamination is, what its hours and limits are, and who to ring before setting off rather than after being turned away.

That information deserves to be held centrally rather than in the heads of long-serving drivers, and it deserves reviewing, because permits and acceptance criteria change. What to check about receiving sites is the starting list. A rejection is also a prompt to re-check: if a site has tightened its acceptance criteria, you would rather find out from the first rejection than the fourth.

Tell the customer, and tell them properly

Where a rejection traces back to a specific customer's waste, the conversation is uncomfortable and necessary. It is also the only mechanism that prevents recurrence, because nothing about your own process will stop a customer putting the same material in the same bin next week.

Doing it well means being specific — what was found, in which collection, and what needs to change — and recording that it was done. A pattern of contamination from one source, documented and communicated, puts you in a defensible position and gives you grounds to act if it continues. The same contamination recurring with no record of ever having raised it does the opposite.

The review that should follow

A single rejection is an incident. A pattern is a process problem, and the pattern is only visible if rejections are logged consistently rather than resolved individually and forgotten.

Worth reviewing quarterly: rejections by cause, by receiving site, by collection round and by customer. Clustering by site may mean that site has changed its criteria. Clustering by round may mean a classification habit on that round. Clustering by customer is the clearest signal of all, and the easiest to act on.