The system that runs your skip hire yard

A typical business running one of these has 8 to 20 vehicles, skip loaders mostly with a roll-on-off and a grab lorry or two, somewhere between 400 and 1,500 skips in circulation, one yard with a weighbridge and a transfer station, and an office of three or four handling 60 to 200 movements a day. The job the system does for the yard is the same whichever generation built it.

In the office's words, it takes the booking by phone or from the website form that arrives as an email, prices it, books the council permit if the skip is going on the road, and puts the delivery on tomorrow's round. Each vehicle gets a printed run sheet: deliveries, exchanges and collections in order. Every skip has a number, and the system knows whether it is in the yard, on a customer's drive or on the back of a lorry. When a load comes over the weighbridge the ticket is written against the job. Each collection prints a transfer note, signed in the cab. At the end of the quarter the return goes to the Environment Agency from a report, and at the end of the week the invoices go to Sage.

What it knows is why nobody has replaced it:

• The price depends on the skip size, the postcode band and the waste type, with a surcharge for plasterboard and a refusal list the desk cannot override.
• A skip on the road needs a council permit, and the system knows which postcodes belong to which council, what each charges and how many days' notice each wants.
• A skip out longer than 14 days attracts a weekly rental charge, except for the account customers with extended hire written into their terms.
• Account customers charged by weight get the weighbridge ticket's net weight set against the job, over the tonnage their price includes.
• A transfer note does not print without the EWC code, the producer's SIC code and the carrier registration number on it.

The people who wrote those rules in have moved on. The rules stayed behind.

Written in the early 2000s by a contractor who knew the trade, and added to until around 2012. A Visual Basic 6 program with the data in SQL Server and a Microsoft Access database beside it for the permit letters and the reports. The weighbridge supplier's engineer wired the indicator into it over a serial lead, and the Sage export came later, when the accounts stopped being retyped. It runs on a server in the yard office and one PC in the weighbridge cabin.

The contractor has retired, and the firm that keeps the office PCs running leaves the program well alone. The server stays put because the weighbridge link is the one part nobody could wire back up, so it sits long out of support while the drivers carry paper.

The same yard system built between 2016 and 2022 by a local agency or a freelancer, as a web system in PHP or React, Angular or Node with a drivers' app in React Native, or put together in Zoho Creator or Bubble by someone in the office who had had enough of the grey screen. Bookings come in from the website priced, the drivers tick off the round on a phone, and the skip register opens in a browser.

The weighbridge is where it came unstuck. The indicator only speaks serial, and a system in a browser has no way to read a lead in the weighbridge cabin, so every ticket is still keyed in and the loads in and out never quite reconcile. Then a change to the postcode bands started booking permits with the wrong council, and the office has booked them by phone ever since. The agency has folded. From 2023 a few yards tried a fresh start in an AI app builder, and those tend to stall at the transfer note, which has to carry the EWC code and the carrier number every time. A generation younger than the VB6 program, and stranded at the same weighbridge.

Every skip is either earning or accounted for, and every movement gets billed.

The register is the heart of it. A skip is a numbered asset, and because every delivery, exchange and collection goes through the system, the yard knows where all of them are without walking round. A skip that has been on a drive for three weeks shows up on the list and the rental charge goes on the invoice. Nothing goes out unbooked and nothing comes back unbilled.

The paperwork is the other half. The transfer notes, the weighbridge tickets and the quarterly return all come from the same records, so when the Environment Agency visits or a customer's auditor asks for the duty-of-care trail, it exists. The weighbridge tie-up means the loads in and the loads out reconcile, which is what the return depends on. And the Sage batch keeps the accounts within a week of the yard.

Systems like this keep going long after the people who built them have stopped.

The weighbridge runs through a cable nobody can replace. The indicator talks to the system over a serial lead into one PC in the weighbridge office, and the database behind it sits on SQL Server 2008 R2, whose updates ended in July 2019, on a Windows Server 2012 box that ended in October 2023. The insurer's cyber questionnaire asked about both this year. The weighbridge supplier will service the indicator, but not the lead or the PC at the other end of it.

The transfer note is still a carbon copy. On the older systems it always was, and on the newer ones it is again wherever the drivers' app will not install. Every collection produces a paper note signed in the cab and filed in the yard. Mandatory digital waste tracking starts on 1 October 2026 for permitted and licensed waste receiving sites in England and Wales, with carriers and brokers following from October 2027. A yard with its own transfer station is in that first wave, and the system has no way to record what it receives as data.

Bookings arrive twice. The website form emails the office, someone keys it into the system, then rings the customer back to confirm the price and the permit. The customer rings twice more to ask when the skip is coming. The morning goes on calls the system could have answered.

The margin per skip is known a month late. The tip's disposal invoices arrive weeks after the loads, and the yard manager matches them to weighbridge tickets by hand. Which skips lost money, which postcode band is underpriced and which account customer is over their tonnage are month-end questions, when they get asked at all.

The same booking desk, with the drivers, the weighbridge, the website and the tip connected to it.

Bookings that land in the system priced. The website form writes the booking straight in, with the size, the postcode band, the waste type and the permit worked out by the rules the desk uses, for the office to confirm rather than key.

The transfer note signed in the cab, as data. The driver's phone carries the round, the customer signs the note on it, and the record is complete with the EWC code and the carrier number the moment it is signed. With the weighbridge ticket beside it, that is the record digital waste tracking asks a receiving site for from October 2026.

The weighbridge on a supported link. The indicator's reading written to the ticket and the job as the lorry sits on the deck, off the serial lead and off the 2012 server.

The skip register, live. Where every skip is, from the driver's taps: which are over their hire period and due a rental charge, which are on the road on a permit that runs out on Friday, which have sat in the yard unused for a month.

Margin per skip the week it happens. The tip's disposal invoice matched to the weighbridge tickets and allocated to the jobs, so the underpriced postcode band shows up in a week rather than a quarter.

A server the insurer will accept. The database and the server it sits on both on versions that are still supported, with a backup that has been restored on purpose. The questionnaire gets an answer.

The old system is not switched off for any of this, whichever generation it is. It gets added to, and the desk decides when to stop opening it.

The comparing and the searching: tip invoices against weighbridge tickets, and the questions no report on the yard answers.

In a skip yard AI is useful wherever one piece of paperwork has to be checked against another, or the answer sits in the records and no report shows it. Two places:

Tip invoices matched to weighbridge tickets. The disposal invoices arrive weeks after the loads, on the tip's own references, and the yard manager matches them by hand. AI reads each invoice, matches its lines to tickets and jobs even when the references do not line up, and flags the lines that match nothing. At 60 to 200 movements a day a month's invoices run to hundreds of lines, so the day or more of matching typically comes down to a couple of hours on what is left, and the margin per skip shows while it is still news.

Questions put to the skip register. Which skips have been out longest, and on whose drive? Which account customers book inert and keep sending back mixed loads? AI answers from the bookings, the movements and the weighbridge tickets in plain words, and lists the jobs behind each answer so the desk can check them before ringing anyone. With 400 to 1,500 skips in circulation, each of those questions used to mean a morning with a printout and a highlighter.

Not worth doing: forecasting skip demand by postcode from a few years of bookings. The yard manager already knows the season.

A system still leaning on a serial lead and an unsupported server is no place to add anything, so AI follows the first stage. The assessment maps where AI would pay back on the system as it stands.

The server, then the receiving record, then the cab and the website, with the old program as the fallback throughout.

1. Stabilise. The VB6 source found and building, or the agency's code recovered, the database off SQL Server 2008 R2 and onto a version that is still supported, with a backup that has been restored, the weighbridge link proven against the new server, and a test copy of the system. This goes first because the 2012 server is the thing most likely to stop the yard.
2. The weighbridge ticket as the receiving record, and the digital waste tracking feed. Every load in written to its job as data, with the EWC code and the carrier, in the shape digital waste tracking asks receiving sites for from October 2026. It comes second because that date already applies to a yard with a transfer station.
3. The driver's round on a phone, with the transfer note signed in the cab, completing the same record from the collection end. The booking desk keeps the screen it knows.
4. Online booking straight into the system, priced by the desk's rules, confirmed by the office.
5. The tip invoices matched to tickets, and the register live. Each a stage, each priced on its own.
6. Retire the VB6 program when nothing depends on it. The last thing to go is usually the quarterly return report.

The assessment is from £395 + VAT, sized on a free one-hour consultation, with an exact price before you commit. For a skip hire system that means a few days with the booking desk, the weighbridge and the code, finding the rules and the risks, and a report with costed options and a fixed price for each. Each stage after that is priced before you commit to it. How we work, what drives the price and the payment terms each have a page, and so does each technology the system is built on: Visual Basic 6, Microsoft Access, SQL Server and Sage integrations, and for the newer generation old PHP, React, Angular and Node and the drivers' app in React Native.