Every month your client's monitoring system produces a list of things you allegedly did not do, and deducts for each one. The deduction is applied automatically. The burden of disproving it sits with you — and the evidence you need is almost always already sitting in your own systems, unreconciled. We go and get it.
This is the part operators underestimate. A contract penalty is not an accusation you get to answer at leisure — it is a deduction that has already happened. The monitoring report is treated as correct, the money comes off the next payment, and the only thing that reverses it is evidence produced inside the dispute window.
The consequence is quiet and expensive: penalties that are never contested are not penalties at all — they are a permanent price reduction. Operators routinely absorb six figures a month this way, not because the penalties are valid, but because nobody has the time, the data access, or the method to answer thousands of individual lines before the window closes.
Any operator whose payment is reduced by a counterparty's measurement of their performance:
The counterparty differs. The structure never does: their system measures, their system deducts, and you are assumed wrong until you prove otherwise.
We take the penalty schedule line by line and attach the strongest evidence available for each one. Nothing is argued in general terms — every contested line carries a named source, a timestamp and a figure that the other side can go and verify.
We work down this order, using the strongest source that exists for that trip:
A single source is rarely decisive on its own. The strength comes from corroboration across systems that have no reason to agree with each other — a ticket sold at 06:14 and a GPS fix at the same stop at 06:13 is a much harder thing to dismiss than either on its own.
One principle does a disproportionate amount of the work. If the vehicle can be shown at the route's starting point at the scheduled time, a later actual departure is usually a driver holding for passengers — an operational reality the contracting authority generally recognises — rather than a failure to operate. Establishing origin presence for every penalised line, from the operator's own claimed vehicle, converts a large share of a typical schedule.
On recent monthly submissions for subsidised transport contracts we have defended 96–97% of penalty lines raised, across schedules running to several thousand lines a month. The remainder are accepted — deliberately. An operator who contests everything, including the indefensible, loses credibility on the lines that matter.
We will always tell you which penalties to accept. A contest file that the other side can pick holes in is worse than no contest file at all.
The same evidence spine answers an audit. Where an operator is sampled and asked to prove that specific trips ran, we build trip-level evidence packs in the exact format the auditor requires — one sampled trip per page, sourced from the operator's own ticketing and tracking records, with the system screenshots that back each figure. Where a returned pack comes back with the auditor's own annotations on it, we amend only the pages that must change and leave the rest untouched.
If some of that does not exist yet, say so early. Part of the value of this work is that it shows you exactly where your operational record is too thin to defend you — and that is fixable before the next month's penalties land.
Reconciling ticketing against tracking against sign-on tends to surface things nobody was looking for: trips run but never ticketed, revenue collected and not banked, vehicles signed out to one duty and driven on another. We report what we find. It is frequently worth more than the penalties.
That analytical work sits alongside our operational intelligence platform, which is how contested months stop being a scramble — the evidence is already assembled when the schedule arrives.
In most contracts, yes, within a defined dispute window. The penalty stands by default and falls away when you disprove it. The window is the binding constraint, which is why the work has to start when the schedule lands and not at the end of the quarter.
Usually yes. Most operators already generate far more usable evidence than they think, spread across systems that have never been reconciled against each other. We start by establishing what your data can and cannot prove.
We price per contract, based on fleet size, schedule volume and the state of your data. Talk to us about which model suits your operation.
Done properly it does the opposite. A contest file that is accurate, sourced and honest about what should be accepted builds standing with the contracting authority. The operators who damage relationships are the ones who dispute everything on principle and can prove none of it.
Send us a single month's penalty schedule and give us access to the underlying systems. You will get back a line-by-line contest file with the evidence attached, a list of what we recommend accepting and why, and an honest assessment of what your data will and will not support going forward.
Defence rates cited are drawn from our own recent submissions and depend on contract terms and the quality of the operator's underlying data. Every contract is different; we will give you an honest view of yours before you commit.