AxleGrid runs in Avior’s development environment and has not been through a customer pilot. Everything on this page can be shown working; the gaps are listed at the bottom rather than left out.
Avior AxleGrid
Secure field operations software for mobile tyre and roadside teams.
Dispatch, a fitter app, customer location and proof of work in one tenant-safe workspace — so the job record that settles a fleet argument exists before the argument starts.
The problem this solves
The record that would settle it is on somebody’s phone.
Mobile tyre and roadside work runs across calls, messages, photos and memory. That is survivable until a fleet customer queries an invoice, disputes an SLA or asks for eighteen months of retorque records in a period return. Then the cost of a scattered record arrives all at once.
How it fits together
One product, on a platform built to carry more than one.
AxleGrid is the first product on the Avior FieldOps Platform. Its modules are shared foundations, not separate purchases — and the platform underneath is why a second product will not need a second security model.
Surfaces
Avior FieldOps PlatformThe foundation every Avior product is built on
- Tenancy and isolation
- Identity and RBAC
- Audit ledger
- Evidence storage
- Plans and limits
- Notifications
Product surfaces
Two places people work, one record underneath.
AxleGrid Console
The office view: intake, dispatch, competence and stock checks, contract packs, invoicing and the audit ledger.
In development
AxleGrid Mobile
The fitter’s view: accept, navigate, capture evidence, record retorque obligations and close the job.
In development
Built for iOS and Android from one codebase. Not yet released to the App Store or Google Play.
Fleet portal
Read-only visibility for the fleet customer, served from the same read model the provider sees.
Designed, not built
The read model is built; the customer-facing front end is not.
The operating loop
From enquiry to proof, every job keeps its shape.
Each stage carries the check that belongs to it, so the record is complete because the work was done properly — not because somebody remembered to fill it in afterwards.
01
Intake
Ten channels into one queue.
15-minute acknowledgement clock
02
Dispatch
Assigned to someone who can do it.
Competence and stock are hard gates
03
Locate
The customer says where they are.
Consented link, no token stored
04
Field
The fitter works the job on the phone.
Retorque obligation raised on fitting
05
Evidence
Photos captured, stripped and sealed.
SHA-256 chain per job
06
Pack
The month, evidenced for the customer.
Self-audits before you release it
What is inside
The parts that do the work.
Dispatch that checks before it assigns
Jobs carry a state machine, an owner and a timeline. Competence is a hard gate — HGV, EV high-voltage, roadside reaction and split-rim requirements are checked before assignment, and an expired competence blocks the job and says so. Van and depot stock is a filter, not a note, so a job that needs a tyre nobody is carrying gets a collection leg inserted rather than a phone call.
Limitation. Overriding a competence gate needs a named permission and a written reason. Both are recorded.
Evidence built as a chain, not a folder
Completion photos are byte-signature validated, stripped of metadata before storage, and hash-chained with SHA-256 per job. The bundle reports whether the chain is intact and whether the checkpoints are complete — before an invoice is raised, not after a dispute starts.
Limitation. JPEG and PNG only today. A general-format path is blocked behind an open malware-scanning item, and PDF and HEIC are not accepted.
Customer location without an app to install
A consent-based link asks the customer where they are, with a typed fallback when GPS will not help. Raw tokens are never stored, responses are no-store and noindex, and every link has a scoped, revocable history.
Measured SLA attainment, not asserted
Response and fix clocks run per job class, with pause reasons, breach-risk warnings, breach events and contractual credits. The number on the contract pack is computed from the job records, so the customer can check it against their own.
Contract packs that audit themselves first
One pack per contract and period, SHA-256 stamped, with a two-day self-audit window in which the pack names its own gaps before you release it. HTML and CSV export, with framework profiles for CCS RM6353, TPPL, YPO and ESPO.
Limitation. Generation is on demand. Scheduled generation and native PDF or spreadsheet output are not built.
Waste transfer notes that refuse to be wrong
EWC-coded lines, carrier registration with tier and expiry, destination permit checks and two signatures — all validated before a note is numbered. Landfill is flagged rather than quietly accepted, and van waste is reconciled against what left the depot.
An append-only audit ledger
Tenant isolation sits in the query layer, not in a filter someone can forget. Roles are scoped and dated, secrets are Key Vault backed, and the ledger is append-only in Azure SQL: 288 atomic permissions and around 260 catalogued event types, so "who changed this" has an answer.
Sign-in that suits who is signing in
Office staff on Microsoft Entra; fitters and fleet contacts on a one-time code — one token format and one authorisation policy behind all three.
Limitation. The passwordless code path is implemented but its delivery channel is not yet configured in any environment.
Status, honestly
What is not built, as of September 2026.
This list is here because it is the part of a vendor website that is usually missing, and because you will find it out anyway.
- There is no production environment yet. Everything above runs in Avior’s development environment and has not been through a customer pilot.
- Billing and payment collection are not implemented. A single sandbox transaction is the whole of the evidence.
- Native push notifications and general offline editing on mobile are not built.
- No certifications. Cyber Essentials Plus and SOC 2 are on a 2027 roadmap and are not held today.
The security page sets out the controls that do exist and how the platform is run.
Questions buyers ask
AxleGrid, in plain answers.
The questions that come up first, answered in a paragraph each. Every answer links to the page that goes into detail.
- What is AxleGrid?
- AxleGrid is job management software for UK mobile tyre fitting and roadside operations that work under fleet and framework contracts. It covers intake, dispatch, a fitter app, customer location links and hash-chained photo evidence, and it produces the contract packs a fleet customer asks for. Avior IT Solutions builds it as the first product on the Avior FieldOps Platform.
- Who is it for?
- The company that turns up and does the work: independent and regional mobile tyre fitters, roadside and breakdown operators, and fleet maintenance providers. It is built for the provider’s side of the contract rather than for the fleet that owns the vehicles. Fleet contract work sets out what it does for the provider’s side of a contract.
- How is it different from fleet management or telematics software?
- Fleet management and telematics software serves the fleet: vehicle tracking, tyre policy, cost per kilometre, when a vehicle is due. AxleGrid serves the provider that does the work: checking a fitter is competent before the job is assigned, capturing evidence at the roadside, and proving to the fleet customer that the work met the contract.
- What does hash-chained evidence mean?
- Each photo or document a fitter uploads is fingerprinted with SHA-256 and linked to the previous item on the job, so altering an item afterwards breaks the chain; the evidence bundle reports whether the chain is intact and which checkpoints are complete. That shows the record has not been altered since capture. On its own it does not prove a photo shows what someone says it shows; the guide Proving the job was done explains the difference.
- Can I use AxleGrid today?
- Not in production yet. AxleGrid runs in Avior’s development environment and has not been through a customer pilot. Everything described on this page can be shown working in a walkthrough, and the list above says what is not built.
- How is it priced?
- By package, not per fitter: Trial, Basic, Professional and Enterprise, separated by jobs per month, branches, users and evidence storage. Figures are quoted in writing after one conversation. How pricing works.
- Where is the data held?
- In Microsoft Azure, UK West region, on a subscription owned by Avior IT Solutions: Azure SQL for records, and private blob storage with per-tenant paths and retention dates for evidence files. The security page lists the controls.
See it working
Pick a job type you argue about.
We will run it through intake, dispatch, the fitter app and the evidence chain, and show you the pack it produces at the end of the month.