How to put together your quarterly Environment Agency waste return

A quarterly waste return is a tally, not a report. For a three month period you tell the Environment Agency what waste came onto your permitted site, what left it, what the waste was under the List of Waste codes, how much of it there was, and where it came from or went to. You are not describing your business. You are adding up records you already made at the weighbridge and on the transfer notes.

The return is a condition of your environmental permit. That matters for two practical reasons. First, the exact fields, the reporting periods and the route you submit by are set out in your own permit and in the guidance current at the time, so read the condition on your permit rather than working from what a mate at another yard does. Second, because it is a permit condition, the record keeping behind it is as much part of your compliance as the site itself.

Most operators are working to calendar quarters, January to March, April to June, July to September, October to December, with the return due a set period after the quarter closes. Do not treat that as universal. Check the dates and the deadline named on your permit, and check the EA's current guidance before you build a template around it.

One thing changed this autumn and one thing did not. From October 2026 every licensed or permitted site that receives waste in England and Wales has to report the loads it takes in through Defra's digital waste tracking service, within two working days of receiving each load. The quarterly return did not go away with it: the guidance is explicit that operators carry on with waste transfer notes, consignment notes, consignee returns and the waste returns their permits require, alongside the new service. So a yard now runs two jobs off the same records, a fast one every couple of days and a slow one every three months.

The rest of this page is about the part nobody writes down for you: how to get from a shoebox of weighbridge tickets to a clean file in one afternoon instead of one week, and how to keep the two-day job from making the quarterly job harder.

Nothing in a quarterly return is created at the desk. Every figure already exists somewhere on site, usually in four places.

• Weighbridge tickets. The quantity. Gross, tare, net, and a timestamp that decides which quarter a load belongs to.
• Waste transfer notes. The waste description, the EWC code, the carrier and their registration, the origin or destination site, the transfer date and the signatures. This is the spine of the return. A missing note is a hole you cannot fill later from memory.
• Consignment notes. Hazardous loads run on their own paperwork and their own numbering. Keep them separate from the start so you are not trying to untangle them in week thirteen.
• Your own site records. Opening and closing stock, if your permit asks for it, plus anything you moved between skips or bays inside the yard.

The most useful thing to understand about the return is that its accuracy is decided at the gate, not at the desk. A note completed properly while the lorry is still on the bridge turns the quarterly job into an export. A weight written on the back of a ticket and keyed in on Friday turns it into an investigation.

That gate moment now has to carry more than it used to. Defra's receipt of waste template asks, per load, for things a traditional transfer note never spelled out: the date and time the waste was received, the form it was in, containers, hazard and POPs details, the vehicle, and the receiving site's own permit or authorisation number. Skiplog captures those receipt-of-waste fields on the transfer note itself, and holds the receiver site name, the environmental permit or authorisation number and the site contact details on the site screen, so the yard's own details are typed once rather than retyped per load.

That is also why the season ticket matters. Where you have repeat collections of the same waste from the same producer, one transfer note can cover the movements for up to a year. It cuts paperwork at the gate, but the quantities behind that ticket still need logging per collection, otherwise the return has a customer with a note and no tonnage.

And whatever route you use, the notes have to survive longer than the quarter they belong to. The regulations set a retention period for transfer notes that runs well past the return they feed, so file the records in a way you can still read next year and the year after. Skiplog is built to that shape: a note you take off your register stays on file for the two years the regulations require, so removing a duplicate from this quarter's return does not destroy the record of it.

The load counted twice

A driver logs a load at the gate. The office, not seeing it, keys it again from the ticket, and the quarter now carries nine tonnes that never arrived. Nothing looks broken: the total is simply too high, which can put you nearer a permit tonnage threshold than you really are, and it is the kind of discrepancy an inspector can spot against your own records. The defence is one record per load, made once at the point the weight is known, plus a weekly count of notes against tickets so a double entry surfaces while the driver still remembers the load. When you do find one, take the duplicate off the register rather than leaving two rows to argue with each other, and keep your own note of why it went. If the load has already gone to Defra under a reference, the correction is a job in its own right: Skiplog marks a corrected note that already carries a Defra reference as a correction still to report, so it does not quietly fall between the two systems.

The number that is not a number

A weighbridge ticket reads 3,240 kg. Typed into a field that expects a plain number, the comma makes it text, and a spreadsheet total quietly ignores it. Mixed units do the same damage more slowly: a column holding both kilograms and tonnes is wrong by three orders of magnitude on some rows, and nobody notices until the total is read out loud. Decide once whether your records hold kilograms or tonnes, convert in one place, strip the separators, and total a column you can trust.

The boundary

A lorry tips at ten to six on the last day of the quarter and the note is signed the following morning. Which quarter owns it? Either answer can be defensible. Two different answers in the same year is not. Write the rule down, keep to it, and make sure the dates printed on the return are the ones you intended.

There are three honest ways a small site gets this done, and the right one depends on how many loads a week come through your gate.

Paper and a spreadsheet of your own. For a handful of loads a week this genuinely works for the quarterly return. The cost is entirely in the last week of the quarter, when someone sits down with a pile of tickets and rebuilds three months of the yard's life from memory and handwriting. The risk is not the arithmetic. It is the notes that were never written, which cannot be recovered afterwards at any price. Be aware that your own spreadsheet is not an option for the Defra side of the work: the guidance says records go in either through Defra's own template, with no format changes and no substitutions, or through software connected to its API.

Defra's template, keyed by hand. Downloading the template and typing each load into it costs nothing but time. If your volumes are low, your yard has reliable signal and someone in the office has a clear slot every day or two, this is a reasonable answer and you should not let anybody tell you otherwise. The thing to be honest with yourself about is the clock: two working days per load, every week, including the weeks when the loader breaks and the office is one person short.

Software that holds the record. What you are buying is not the return. It is the gate. A record captured once, on a tablet, in under two minutes, while the lorry is still there, with the code and the carrier and the weight attached to it. Both jobs then start from records already held in the shape they want: Skiplog exports receipt rows in Defra's template column order for the date range you pick, for your yard to upload, and the quarterly return as a one-click CSV in a configurable EA column layout. The checking is still yours to do. That trade is worth paying for when the yard does enough loads that hand keying falls behind, or when there is no dedicated compliance clerk and the person doing it is also the person running the site.

Two questions decide it for most yards. The first is signal: a weighbridge in a cutting or a yard behind a steel building will drop connection several times a day, and anything that needs a live connection to save a note will lose notes. The second is who writes the note. If the record is made by the person who saw the waste, at the moment the weight is known, both the two-day job and the quarter look after themselves. If it is made later by somebody working from handwriting, no amount of software further down the line will put back what the handwriting left out.

The October 2026 mandate changes the shape of this work rather than the substance of it. The information Defra's service wants is largely the information a transfer note already carries, plus a few fields most yards had on the ticket and not on the note. What changes is the rhythm. The quarterly return is a thirteen week job with a deadline; the receipt of waste report is a two working day job with a deadline, over and over, every week of the year.

If you are already keying notes into a tablet, both jobs become closer to print jobs. If you are still on duplicate books, the honest sequence is to fix the gate first and the paperwork second. Sorting out a quarterly export while the underlying notes are still handwritten just moves the retyping to a different week, and a two-day clock makes that worse, not better.

Four practical things to line up. Get your waste code list audited, because a digital record propagates a wrong code faster and further than a paper one. Get the receiver's details, your permit or authorisation number and the site contact, recorded once in one place, because every Defra row wants them. Get your carrier registrations in front of you with warning before they lapse, which our page on waste carrier, broker and dealer registration expiry alerts covers. And decide now who in the yard is allowed to change a recorded load and how that change gets documented, because an inspector will ask how a figure came to be amended, and because a load Defra has already accepted has its own correction window.

Skiplog is built around that rhythm rather than bolted onto it. Each receipt row is checked against Defra's upload rules before it leaves, on the receipts screen and again on the note form when the operator saves, so a field that would bounce the spreadsheet is flagged at the gate instead of at the upload. The export sends only the rows that pass, says how many it held back, and links each failing row to the screen where it is fixed. After a download it asks whether you have uploaded them, and on your confirmation stamps each note in the batch as reported. Where Defra gives you a waste tracking reference it is stored against the load; where Defra rejects one, you can record the date on the rejection notice and Skiplog sets the new deadline from it. A dashboard card lists the loads not yet reported, grouped as overdue, due today and due tomorrow, worked out from the two working day rule.

If you want the mechanics of the quarterly export itself rather than the process around it, see the page on the quarterly waste return export in the EA column layout, and the page on what format the Environment Agency wants a quarterly return in. For the view across a quarter as it fills, notes logged and tonnage by waste type, see the waste site compliance dashboard page. For the day an officer arrives and wants the records in front of them, see the page on pulling the records together when the Environment Agency turns up. And if you want this written for your kind of site specifically, there are pages for waste transfer stations and for recycling facilities.

You do not need a compliance department for this. You need a habit at the gate, a short slot every couple of days, and twenty minutes a month at the desk.

Daily, at the gate. Every load gets a note as it happens, written by whoever is on the gate, with the waste description, the code, the weight off the bridge, the date and time it came in, the carrier and their registration, and the origin or destination site. No exceptions for regulars, no exceptions for small loads, no notes finished later. The weighbridge and the office can each sign in as themselves, so every note names who wrote it rather than the yard sharing one login.

Every second day, the Defra upload. Export the receipt rows for the days since the last batch, upload them, then confirm it so the loads are marked reported and the clock stops on them. If a row is held back, fix the field it names rather than editing the spreadsheet, because the fix has to live on the record you keep, not just in the copy you sent.

Weekly, ten minutes. Count notes against weighbridge tickets for the week and resolve any mismatch while the driver is still reachable. This is the single cheapest control in the whole process, and it is the one most yards skip.

Monthly, twenty minutes. Look at tonnage by waste type and ask whether the split looks like the month you actually had. An odd figure a month out is a question. The same figure on the day the return is due is a problem.

Quarter end. Walk the yard if your permit wants stock held. Close the period. Check the quarter's notes against what went to Defra. Produce the file, check the period dates, check the hazardous codes, check the total against your own sense of the quarter. Submit by the route on your permit, then file the sent file with the notes behind it.

None of that is difficult. It is just work that has to happen at the time, because the one thing no software and no spreadsheet can do is produce a record of a load nobody wrote down. Get the gate right and both deadlines stop being events.