Two working days, measured from the gate: what the clock really means

If you hold a permit or licence to receive controlled waste in England or Wales, every load that comes through your gate has to go into Defra's Report receipt of waste service within two working days. The count starts on the day after the waste arrives, not on the day it arrives, and weekends and bank holidays do not count at all. The gov.uk guidance gives the plain version: waste received at 9am on a Monday has to be submitted, and a unique reference number received back, by 11.59pm on the Wednesday.

Two words in that rule do all the damage. "Working" means the clock stops dead on a Saturday, a Sunday and a bank holiday. "After" means the rest of the day the skip tips is free. And one more rule sits behind both of them: if the service or your software tells you a submission has an error, the correction has to land inside the same two working days. A rejection does not restart the clock.

Count it in this order

Start from the date the waste was received at your site. Not the date on the carrier's ticket, not the date somebody keyed it in.

1. Begin on the next calendar day.
2. Walk forward, counting working days only.
3. The second working day you land on is the deadline, and you have until 11.59pm that night.
4. The submission has to be accepted by then, with a reference number back. Typed in is not the same as accepted.

That last point is the one worth writing on the wall of the weighbridge hut. Uploaded and bounced is not uploaded.

A normal week, with a trap in it

Take the week of Monday 12 October 2026. Nothing unusual in it, no holidays.

• Load in on the Monday. Deadline 11.59pm Wednesday.
• Load in on the Tuesday. Deadline 11.59pm Thursday.
• Load in on the Wednesday. Deadline 11.59pm Friday.
• Load in on the Thursday. Friday is working day one, the weekend is dead air, Monday is working day two. Deadline 11.59pm Monday.
• Load in on the Friday. Monday is day one, Tuesday is day two. Deadline 11.59pm Tuesday.

Read the bottom two lines again. Thursday and Friday loads give you the most calendar time and the least usable time, because the only two working days you get are the two days the office is at its worst: a Monday with the weekend's tickets in a pile on the desk, and a Tuesday that was already full before you started.

If you take skips in on a Saturday morning, the same arithmetic applies and it works in your favour. Sunday is not a working day, so day one is the Monday, day two is the Tuesday, and the deadline is 11.59pm Tuesday. The Saturday itself buys you nothing and costs you nothing.

The week where the clock stretches

Christmas is where yards either gain time they do not realise they have, or assume the opposite and submit late. In England and Wales, Christmas Day 2026 is the Friday, 25 December. Boxing Day is the Saturday, so the substitute bank holiday is Monday 28 December.

• Received Wednesday 23 December. Thursday 24 is working day one. Christmas Day, the weekend and the substitute Monday are all out. Tuesday 29 December is working day two. Deadline 11.59pm Tuesday 29 December.
• Received Wednesday 30 December. Thursday 31 is day one. New Year's Day 2027 is the Friday, then the weekend again. Monday 4 January is day two. Deadline 11.59pm Monday 4 January, five days after the load tipped.

The arithmetic is not the hard part. The assumption is. A yard that thinks a bank holiday shortens the window spends the quiet week chasing itself. A yard that thinks the window is simply "two days" and shuts the office until the second of January has missed everything it took in on the twenty-third.

Where a yard actually loses the day

Four places, and none of them are the counting.

• The ticket pad. Friday afternoon's loads sit in the hut over the weekend. Nobody keys them until Tuesday after lunch, and the deadline for those loads was 11.59pm that same Tuesday. The clock had already spent both its working days before the paperwork was opened.
• The rejection. You upload at four o'clock on the deadline day. One row has an EWC code that does not match the description, or no vehicle registration. The error notice comes back and the correction is due the same night, inside the same two working days. Finding out which row is wrong is the expensive part.
• The handover. With tickets in a van and a spreadsheet in the office, nobody can answer the only question that matters, which is which loads are still unreported and when each one is due.
• The outage. The guidance is specific. If the service is unavailable you still have to make and keep a written record of the receipt data within two working days from the day after the load came in, and then get that record into the service within seven working days starting the day after the outage is resolved. An outage buys you a transfer window, not a holiday from recording.

This two working day receipt duty is the England and Wales regime. If you move waste across a border, check what applies on the other side before you assume one process covers everything.

What Skiplog is built to do with this clock

Skiplog has not launched yet, so this is what it is built to do rather than what a yard will tell you it does.

The receipt fields are captured on the transfer note itself, including date and time received, alongside the EA-mandated fields for waste type, EWC code, quantity, carrier and destination, and the note is meant to be completable in under two minutes on a tablet at the weighbridge. The note saves to the device first with a visible queued, syncing or synced status, and syncs on its own when connectivity returns, so the operator can see which state a record is actually in rather than guess at it.

From there the deadline is the product's job, not the operator's memory. A dashboard card lists the loads not yet reported, grouped as overdue, due today and due tomorrow. Receipt rows are checked against Defra's upload rules before anything leaves the building, the export sends only the rows that pass, each failing row points at the field that needs fixing, and the same check runs on the note form when the operator saves, so the bad row is caught at the weighbridge rather than at four o'clock on the deadline. The export itself is in Defra's own template column order. After a download Skiplog asks whether the rows went up, stamps the ones you confirm as reported, and stores Defra's reference against each receipt. If Defra rejects one, there is an action to record the rejection and the new deadline it creates, and a correction to a note that already carries a reference is flagged as something to report again.

None of that signs for your compliance. The dates, the weights and the EWC codes are yours, and Skiplog is built to help you meet the requirement rather than to guarantee the outcome. What it is built to do is count the two working days for you and put Friday's load on that dashboard card as overdue, due today or due tomorrow, so the question of what is still unreported has an answer on a screen rather than in somebody's head.