Skip to content
AviorIT Solutions

Fleet contract work

Fleet tyre management software for the provider’s side of the contract.

Most software described as fleet tyre management is built for the fleet: tyre policy, cost per kilometre, when a vehicle is due. AxleGrid is built for the company that has to turn up, do the work, and then prove it happened the way the contract said it would.

Show me a contract pack

The problem this solves

Winning the contract is the easy part. Reporting on it is what costs you.

A fleet or framework contract usually commits you to response and fix times, to evidence for every job, to closing retorques, to using technicians who hold the right competence, and to disposing of casings lawfully. Then it asks for a periodic return that shows all of it.

Most providers assemble that return by hand, from job sheets, a photo gallery, a spreadsheet of retorques and whatever the accounts system can export. It takes days, it is out of date when it is sent, and nobody can tell whether it is right.

AxleGrid’s position is that if the system already records the work, the return should be a query, not a project — and it should tell you what is wrong with it before your customer does.

What the platform produces

The obligations a tyre contract creates, each with something that answers it.

  • Measured SLA attainment

    Response and fix clocks are computed for every completed job under an SLA policy, by job class, with the breach detail read from the audit ledger rather than typed in afterwards. Where a job could not be measured, the count of measured jobs is stated on the report instead of quietly averaging it away.

  • Contract packs

    One pack per agreement and period: scope, SLA attainment with credits and breach detail, retorque closure and grades, evidence completeness with a link to each job’s bundle, invoices issued, the technician competence register with expiry states, disposal, and open items. Section order follows the framework profile; the numbers do not change with it.

  • Hash-chained evidence

    Each photo or document a fitter uploads is SHA-256 hashed and linked to the previous item on the job. The bundle reports whether the chain is intact and which checkpoints are complete, and a job can be held out of billing until they are.

  • Competence gating on dispatch

    An assignment is checked against the fitter’s competences on the day. An expired one is named first, because someone once qualified may not know it lapsed. A block can be overridden by a named person with the permission, with a reason, and both the block and the override are in the ledger.

  • Waste transfer notes

    A note per collection: EWC-coded lines with quantity, weight and outcome; carrier name, registration number, tier and expiry; destination and its permit reference and expiry; both signatures. Validation runs before a number is issued, so an expired carrier registration fails without consuming a sequence number. Landfill is recorded and flagged, never silently accepted.

  • Van waste reconciliation

    Casings taken out of service in a period, against tyres transferred on issued notes, against what is on the van today — per waste code. The gap is the question worth asking, so the system shows it rather than a tidy total.

What that evidence has to cover depends on which dispute you are trying to close.

The part we would argue about

A pack that audits itself before you send it.

When a contract pack is built it does not go straight out. It sits in a self-audit window and lists its own gaps.

The gaps are the point. A pack with no gaps is a good month. A pack with six is a conversation you would rather have internally, in the two days before release, than in a contract review.

Once released, a pack is immutable and carries its SHA-256 in the footer — a correction is a new pack, so an old link can never show superseded evidence.

Self-audit · 2 days remaining

6 open items
  • SLA could not be measured on 3 jobs
  • Evidence incomplete on 1 job
  • 2 retorques still open at period end
  • 1 competence expired inside the period
  • Account requires a purchase order and has none
  • Disposal register empty for week 36

pack sha256 c74b…19e2 · released packs are immutable

Who this is for

Independent and regional providers doing contracted work.

  • Mobile tyre fitting

    Vans running scheduled fits and roadside call-outs for fleet customers, where the response clock and the evidence are what the contract is actually about.

  • Roadside and breakdown

    Emergency work where the job class changes the SLA, the competence requirement and who has to be told what, in the moment.

  • Fleet maintenance providers

    Operations serving several fleet customers on different agreements, where each one wants its own period return in its own shape.

Status, honestly

What is built, and what is not, as of September 2026.

Everything above is implemented in the AxleGrid codebase and covered by automated tests. Some of it sits on the development branch rather than in a live environment on any given day, so ask for the current state when you book a walkthrough.

Not built yet: the fleet customer portal
Portal users, site filtering and authorisation limits exist behind the API. The front end your fleet customer would log into is a later piece of work. Today they receive keyed links to the pack and the invoice instead.
Not built yet: scheduled pack generation
Packs are built on demand. Generating them automatically on the agreement’s cadence follows once the automation module lands.
Not built yet: native PDF and spreadsheet renderings
A pack exports as framework-shaped HTML, which prints to PDF, and as long-format CSV. Native PDF and XLSX renderings are a later addition.
No certifications yet
Cyber Essentials Plus evidence and a SOC 2 Type 1 readiness assessment are on the 2027 roadmap. Until then the controls on the security page are the claim, and they can be inspected.

Next

Bring your worst contract.

Send the reporting schedule from a contract you already hold, and we will show you which parts a pack answers today, which parts it does not, and what your team would still do by hand.

Book a walkthroughHow pricing works