Solidify Before Disposal: Four Cities, Four Different Rules

A catering company running events across three neighbouring cities got a lesson in local rulebooks last spring. Same menu, same gelled bins, same contractor group. City one accepted every load. City two charged a contamination fee twice. In city three, a driver simply refused the bin, left it on the kerb, and the venue spent a weekend with a full food waste container in 28-degree heat.

Nothing about the waste changed. What changed was the wording of each municipality’s waste acceptance rules, and nobody on the operations side had read them. If your team moves between sites, or you cater events rather than running one fixed kitchen, “solidify before disposal” is not one rule. It is a different rule in every jurisdiction you collect from.

Why the rules differ in the first place

Food waste from commercial kitchens ends up in different places: anaerobic digestion, in-vessel composting, incineration with energy recovery, or landfill where it is still permitted. Each receiving site has its own tolerance for free liquid, because liquid is what wrecks their process. Digesters can usually take moderate moisture. Composting sites reject soupy loads because leachate management is their biggest cost. Landfills in many regions are legally barred from accepting bulk liquid at all, which is exactly why solidification became standard practice there.

So the same gelled bin can be a compliant load at a digester gate and a rejected load at a composting pad, on the same morning, in the same region.

Three questions to ask every local authority

Before a new site starts producing gelled food waste, get answers in writing to three questions. First: what is the free-liquid standard at acceptance? Many sites reference a paint-filter or drain test, where no liquid may drip from a sample within a set time. Second: is food waste required to go in a separate stream, and does solidified waste still count as that stream? Third: does the hauler or the receiving site do the compliance check, and what happens when it fails, contamination fee, load refusal, or both?

The third question matters more than operators expect. A municipality can have a friendly-sounding rule while the contracted hauler enforces it aggressively, and the hauler is who your driver actually meets at 5 a.m.

There is also a timing trap. Rules are written for the receiving site, but enforcement happens at the kerb, at five in the morning, by a driver with a schedule and a spill to avoid. A municipality that permits solidified waste in the food stream will still see a bin refused if the driver judges that liquid is present, because the driver, not the regulator, carries the risk of a burst bag on the pavement. Written rules tell you what is legal; the driver’s ten-second glance tells you what is collectable. Plan for the stricter of the two, and keep a copy of both.

What solidification changes in your paperwork

Most operators find that solidification simplifies the classification question rather than complicating it. A bin of free-flowing broth is hard to describe on a transfer note; a solid or semi-solid gelled mass is straightforward. What you should carry on file is simple: the product used, the dose applied, the waste description, and ideally a photo of the gelled result from a typical bin. When a load is queried at the gate, that four-line record settles the conversation in minutes instead of days.

Build a one-page rule card per site

Turn each jurisdiction’s answers into a single card kept in the cab of the collection vehicle or pinned in the bin room: acceptance standard, stream requirement, enforcement contact, and what to do on a refusal. Sites that do this cut their dispute resolution time dramatically, because the driver is not arguing policy from memory. For product selection by waste type and climate, the SAP powder product range lists grades suited to different acceptance standards.

This week, email your three questions to every local authority on your site list. Whatever comes back, turn it into those one-page cards before the next menu change, not after the first refused load.