Skip to content
AviorIT Solutions

Avior FieldOps Platform

Field operations software that can prove what happened.

Avior builds AxleGrid — dispatch, a fitter app, and hash-chained evidence — for UK mobile tyre and roadside teams working under fleet and framework contracts.

In development, pre-pilot. We will show you the working system and tell you what is not finished.

Live operations

Dispatch board

Tenant verified

Control queue

  • AXG-260517-5163Roadside tyre serviceM6 northbound12m
  • AXG-260517-5164Fleet depot visitBay 4, Droitwich26m
  • AXG-260517-5165Location link pendingAwaiting customerHold
  • AXG-260517-5166Evidence review3 photos, chain intact41m

Job detail

AXG-260517-5163

Roadside tyre service

  • Competence checkedHGV · roadside reaction
  • Location confirmedConsented link
  • 3 photos capturedMetadata stripped
  • Chain intactSHA-256 verified

SLA — response

38m of 60m target

atomic permissions
288atomic permissionsAuthorisation is a model, not a role dropdown.
evidence chain
SHA-256evidence chainPer job, verified before an invoice is raised.
UK framework profiles
4UK framework profilesCCS RM6353, TPPL, YPO and ESPO pack shapes.
certifications claimed
0certifications claimedBecause we do not hold any yet.

How the work runs

From the call coming in to the evidence going out.

Mobile tyre and roadside work usually runs across calls, messages, photos and memory. AxleGrid gives it one path, and puts a check at each point where the work normally goes wrong.

  1. 01

    Intake

    Ten channels into one queue.

    15-minute acknowledgement clock

  2. 02

    Dispatch

    Assigned to someone who can do it.

    Competence and stock are hard gates

  3. 03

    Locate

    The customer says where they are.

    Consented link, no token stored

  4. 04

    Field

    The fitter works the job on the phone.

    Retorque obligation raised on fitting

  5. 05

    Evidence

    Photos captured, stripped and sealed.

    SHA-256 chain per job

  6. 06

    Pack

    The month, evidenced for the customer.

    Self-audits before you release it

Avior AxleProof

The record has to survive the argument, not just the day.

A folder of timestamped photos feels like proof and rarely is. It cannot show that nothing was removed, and it cannot tie an image to the job it belongs to.

AxleProof seals each step of a job into a chain: every record carries the hash of the one before it, so a missing or altered link breaks everything after it. The bundle reports its own integrity before you invoice — not eighteen months later when a fleet customer asks.

  1. Job accepted

    4c1e…08af

    Fitter, time, location

  2. Before

    9b73…21dd

    Tyre condition, tread

    ← carries 4c1e…08af

  3. After

    e0a5…7f19

    Fitted, torque applied

    ← carries 9b73…21dd

  4. Retorque due

    2d84…b6c0

    Obligation raised

    ← carries e0a5…7f19

  5. Bundle sealed

    9f2a…c41d

    Chain verified intact

    ← carries 2d84…b6c0

What this does not prove. A chain shows the record has not been altered since it was sealed. It does not prove a photograph shows what someone says it shows. Those are different claims and we do not conflate them.

Where it earns its place

Winning the contract is the easy part.

Reporting on it every month is what costs you. AxleGrid produces the evidence a fleet or framework contract demands, from the same records the work already created.

Measured SLA attainment

Response and fix clocks per job class, with pause reasons, breach events and contractual credits.

Self-auditing packs

One pack per contract and period, SHA-256 stamped, naming its own gaps before you send it.

Competence gating

HGV, EV high-voltage, roadside and split-rim checks block dispatch rather than warn about it.

Waste transfer notes

EWC-coded, carrier and permit validated, reconciled against what left the van.

Services

The work around the software, done by the people who built it.

Field software fails in the first fortnight, not the first year. These four are the services Avior actually performs — and the list stops there on purpose.

Onboarding and setup

Field software fails in the first fortnight, not the first year.

What it covers

Data migration

The history you need in a dispute is in the system you are leaving.

What it covers

Custom reports

Every fleet framework wants the same facts in a different shape.

What it covers

Custom integrations

Your customer’s system, your accounts package and your ordering do not talk to each other, so somebody retypes the same job three times and the third copy is wrong..

What it covers

Status, honestly

What is built, and what is not.

Every vendor’s site in this category reads like a brochure. Ours names its own gaps, because that is the thing most likely to survive a procurement process.

  • In development, pre-pilot.

    The platform runs in Avior’s development environment. There is no production environment yet and no customer has been onboarded.

  • Evidence handles JPEG and PNG.

    A general-format path is blocked behind an open malware-scanning item. PDF and HEIC are not accepted.

  • The mobile app is not published.

    Built for iOS and Android from one codebase, and not yet released to the App Store or Google Play.

  • No certifications.

    Cyber Essentials Plus and SOC 2 are on a 2027 roadmap. We do not hold them today and will not imply otherwise.

  • Pricing figures are not signed off.

    The model is published in full; the numbers follow when the commercial policy is approved.

Next step

Bring us your most awkward contract.

The quickest way to judge this is to put a real obligation in front of it. Send the contract or the dispute you keep losing, and we will show you what the system produces for it — including where it comes up short.