A dashboard can contain twenty charts and still tell the transport manager nothing useful.
The numbers look tidy. The colours move. Yet nobody can answer the questions that matter: Are we short of eight-yarders? Which jobs keep failing? Where are we losing vehicle time? Which customers have skips sitting far beyond the normal hire?
Good skip hire KPIs make the operation easier to run. They point to a decision, a problem or a pattern worth investigating.
Start with the decision, then choose the number
Do not begin with everything the software can count. Begin with what managers need to decide.
- Can we accept more bookings tomorrow?
- Do we need more of a particular skip type?
- Which route or area is causing wasted journeys?
- Are long hires tying up stock?
- Why are customers calling or complaining?
- Where is overtime coming from?
Each question needs a small amount of clean data. A report should help the manager act, not require another spreadsheet to interpret it.
Track completed work against planned work
Job volume on its own can flatter a difficult day. Compare scheduled movements with completed movements, then separate deliveries, exchanges and collections.
The gap matters. A missed collection may affect tomorrow’s stock. A failed delivery may need customer contact and a second journey. Record the reason while it is fresh so the weekly report says more than “not completed”.
Make failed jobs visible by cause
One failed job may be bad luck. Ten failures caused by blocked access are a process problem.
Use a short, consistent list of reasons such as customer not ready, access blocked, unsafe load, wrong details, vehicle issue or internal scheduling error. Review the pattern and decide where to intervene.
A better booking question might prevent access failures. A reminder might reduce not-ready collections. A route change might deal with repeated timing problems. The KPI is only useful when it leads back to the workflow.
Watch usable stock, not just total stock
Total skips owned is a slow-moving asset figure. Daily operations need availability by type and status.
- Available in yard
- Reserved against confirmed bookings
- On hire
- Awaiting collection or tipping
- Under repair
- Over the normal hire period
This view helps sales and transport make better promises. It also shows whether the business is genuinely short of stock or simply slow at turning assets around.
If a KPI cannot change a conversation in the morning meeting, ask why you are collecting it.
Measure time where it affects capacity
Average job duration can hide the awkward work. Break time down where possible: travel, site time, tipping and delays. Look for repeat outliers rather than judging drivers from one difficult day.
The aim is to improve planning assumptions. If commercial exchanges routinely take longer than domestic collections, schedules should reflect it. If one transfer-station visit creates a predictable queue, route planning should stop pretending otherwise.
Connect revenue with operational effort
Revenue by product or postcode is useful. Margin is better. A busy service area may be swallowing vehicle time. A popular skip size may carry disposal costs that pricing has not caught up with.
Combine financial data with movements, distance or vehicle time where your records support it. Do not invent precision from weak inputs. Start with broad patterns and improve the data before making fine-grained decisions.
Use different views for different roles
The owner may want weekly demand, margin and stock investment. The transport manager needs today’s exceptions and tomorrow’s capacity. The office needs unpaid or incomplete bookings and customers requiring contact.
Do not force everybody to use the same report. Keep each view focused on the decisions that person owns.
Keep the first scorecard short
A sensible starting scorecard could contain:
- Planned and completed movements by type
- Failed jobs by reason
- Available stock by skip type
- Long-hire placements needing review
- Bookings by source and postcode area
- Jobs requiring manual correction or follow-up
Once the team trusts those figures and uses them, add detail carefully. More data is not automatically more control.
Reporting starts with connected records
Fix definitions before comparing teams
Agree what each measure means. Is a job completed when the driver presses a button, when the skip reaches the site or when the office checks the evidence? Does a same-day reschedule count as failed? Does available stock include skips waiting to be inspected?
If two people use different definitions, the chart creates an argument rather than an answer. Write the rule beside the KPI, keep it stable long enough to see a trend and record deliberate changes.
Locovo is building reporting around the operational data held in the Dashboard. Advanced KPI reporting is part of the wider roadmap, so we will not claim every measure described here is available today.
The first step is dependable booking, stock and job data. Explore the Locovo Dashboard, or read why skip hire software and spreadsheets produce very different operational records.
