KubitDocs · Guides

What a site waste management plan has to contain, and why the client asks for it

A site waste management plan says, before the first skip arrives, what waste a project will produce, how it will be separated, who will carry it, where it will go and how much will stay out of landfill. Month by month the waste log is reconciled against it; at completion the client's report is written from it.

Why the client asks for something the law stopped requiring

In England the Site Waste Management Plans Regulations 2008 made a plan compulsory for projects over £300,000. They were revoked in December 2013. There has been no statutory site waste management plan in England since, and a contractor who says so is right.

The client asks anyway, for three reasons. The planning permission often carries a condition requiring one, to be discharged before work starts. The client's own reporting, and any environmental scheme the building is scored under, need the tonnages and the diversion rate, and those figures come from nowhere else. And the duty of care under section 34 of the Environmental Protection Act 1990 sits on everyone who produces, carries, keeps or disposes of waste — the contractor as producer, and the client wherever it arranges a removal itself. When a load is traced back, the regulator arrives at the site named on the consent.

That duty is the law that still applies. Every load leaves with a registered carrier on a transfer note, kept two years under regulation 35 of the Waste (England and Wales) Regulations 2011, or on a consignment note for hazardous waste, kept three years under the Hazardous Waste (England and Wales) Regulations 2005. Regulation 12 of the 2011 Regulations requires the waste hierarchy to be applied — prevention, preparing for re-use, recycling, other recovery, disposal, in that order. From October 2026 the receiving site records the load on the digital waste tracking service; the producer's note and its retention are unchanged until the Regulations are. A plan is how a site shows it thought about the hierarchy before the waste existed.

What it has to contain

  1. The project and its waste. What is being built, demolished or stripped out, and the phases that produce most of it; where there is an existing building, the pre-demolition audit.
  2. The forecast. One line per waste stream: its List of Wastes code, an estimated quantity, the activity it comes from, whether it is segregated, and its route — re-use, recycling, other recovery or disposal.
  3. Segregation and storage. Which skips and bays, where they stand, what goes in each; plasterboard out of the mixed skip; hazardous waste locked, bunded and labelled.
  4. Carriers and destinations, checked. The carrier's registration checked against the regulator's public register, not a photocopy; the destination's permit or exemption checked for the waste sent to it.
  5. Targets. The diversion-from-landfill figure the tender or the client set, re-use on site, and where the specification asks, the recycled content of what is bought.
  6. Responsibilities. Who owns the plan, calls the skips, raises the notes and checks the carriers; each subcontractor consigns its own hazardous waste.
  7. Monitoring. The monthly reconciliation of the waste log against the forecast, and the plan revised when a stream appears that was never forecast.
  8. Completion. Actuals against forecast, the diversion achieved, the notes filed for their retention period, and what to change next time.

The two mistakes

The plan written for the tender and never opened again: a forecast with no reconciliation is a guess with a signature. And the plan that reads as a waste policy — pages on the hierarchy, nothing on which skip stands where.

What a template does not do

A template gives the plan its headings, the codes and the legal driver printed on the sheet. It does not know what this project will produce, it cannot check a carrier, and a target nobody reports against is decoration. The competent person running the site writes the plan and reconciles it, and no document makes anyone compliant. Why we will never call a document "compliant".

Documents for this work