Skip permits: where the days go missing

Permits are not complicated. A skip on private ground needs nothing. A skip on the public highway needs permission from the council, and that permission has a cost, a lead time, an expiry date and conditions attached to it.

None of that is hard. What makes permits one of the most reliable causes of a failed delivery is that every part of it lives outside your business — on a council's timetable, in a council's format, at a council's pace — while the customer's expectation lives firmly inside it.

The four things that vary by council

If you work across more than one authority, you already know that "a skip permit" is not one thing. What varies:

• The lead time. Some authorities will turn an application round the same day. Others want several working days, and a few effectively want a week once you allow for how they process things.
• The duration and what happens after. Permits run for a fixed period. Some can be extended, some require a fresh application, and the difference matters when a customer asks to keep the skip another fortnight.
• The conditions. Lights, cones, markings, reflective plates, restrictions on where a skip may sit relative to junctions and crossings, and rules about which roads are excluded entirely.
• The paperwork. A portal here, an email there, an account with a purchase order somewhere else.

You cannot standardise the councils. You can standardise what your business does about them.

Where the days actually go

Three places, in roughly this order of frequency.

The permit was never applied for. The order was taken on the phone, the customer said it was going on the road, and the note got written on the order. The application was somebody's job later that afternoon, and later that afternoon a driver rang in with a problem and the day moved on. It surfaces two days later when the delivery is being loaded.

It was applied for too late. Nobody knew that this particular authority wants five working days, because that fact lives in the head of whoever usually does the applications and they were off.

It expired while the skip was still there. The hire ran long — customers keep skips longer than they say they will — and the permit ran out underneath it. Now you have a skip sitting on a public highway without authorisation, which is your problem rather than the customer's.

A permit failure never announces itself in advance. It announces itself as a driver in a cab with nowhere to put a skip.

The bit that costs more than the delay

A late delivery is embarrassing and it costs you a wasted journey. The expired permit is worse, because it is an enforcement exposure and because the fix is slow: you either get an extension through at speed or you send a vehicle to move a skip that the customer is still filling.

Both problems have the same root. The permit is a date-driven obligation attached to a job, and date-driven obligations are exactly what a paper system cannot watch for you. A diary does not know that today is four days before an expiry.

How to make it boring

The aim is that permits stop being something anybody remembers to do.

1. Ask the question at the point of order. Not "any special requirements" — a plain choice between private ground and public highway, asked every single time, including on online orders. Everything downstream depends on this answer being captured rather than assumed.
2. Hold the lead time per council, not in someone's head. Once the system knows that this authority needs five working days, it can stop the earliest available delivery date being one that you cannot legally meet — before the customer is promised it.
3. Make the application a task with an owner and a date. Attached to the order, visible on a list, not living in an inbox.
4. Store the permit against the job. The reference, the dates, the conditions, the document itself. When a driver or an inspector asks, it is on the order, not in a folder in the office.
5. Watch the expiry, not the delivery. A permit that ends before the skip is due off is the alert worth having, and it needs to fire days ahead, not on the morning.

Tell the customer what the permit means

Half the friction is that customers do not know the rules and assume you are inventing obstacles. A short, plain explanation at the point of ordering — the road is the council's, not yours; it costs this much; it takes this long; the skip needs lights on it — converts an argument into an administrative fact.

It also protects you when the customer wants to keep the skip longer, because the constraint has already been explained once. Extending a hire that sits on a permit is not the same as extending one that sits on a drive, and a customer who was told that at the start takes it much better than one hearing it for the first time.

Where this connects to everything else

Permits are the clearest example of a general pattern in skip hire: the business is a series of dated obligations — deliveries, collections, permit expiries, hire periods, invoices, and now waste records under digital waste tracking. Individually each one is trivial. Collectively they are more than a person can hold, and the failure mode is always the same. Nothing is checking.

That is the entire argument for a system, and permits make it more cleanly than anything else, because the consequence is so immediate: a vehicle, a driver, a skip, and a road you are not allowed to put it on.

SkipHub tracks permits against the order — application, reference, dates and expiry, with the lead time built into what the customer can be offered. The features pages cover how that fits with scheduling, and taking orders out of hours covers asking the road question properly on a website.