Workshop & operations

Tyre management

Uneven wear is the reason a workshop measures all four wheels. That is exactly how it is captured: four values per visit, as a time series with date and odometer, evaluated against two different thresholds.

Request a demoView pricingIn every installation
Readings per measurement4 wheel positions
ThresholdsStatutory and seasonal, separate
Defaults1.6 mm · 4.0 mm winter · 3.0 mm summer
Change anchorsOctober and Easter Monday

Four wheels, four readings — not one average

A tread depth without a threshold is a number without a statement. So the module keeps two: the statutory minimum below which a vehicle must not be driven, and the seasonal recommendation at which a fleet swaps. Both are configurable per tenant, because Austria requires more of a winter tyre by law than Germany does.

What it does

What the module actually does

Tyre sets per vehicle

Summer, winter or all-season, mounted or in storage, with dimension, storage location and change history. A change writes both sides: the outgoing set is dismounted, the new one mounted.

Tread measurements at four wheel positions

Front left, front right, rear left, rear right — each measurement with date, odometer and a 'new tyres' flag. The lowest value of the most recent measurement is the vehicle's tread depth.

Two thresholds, because these are two questions

The statutory minimum (default 1.6 mm) marks a vehicle as unsafe to drive. The seasonal recommendation (default 4.0 mm winter, 3.0 mm summer) is the point at which a fleet swaps — and what the pre-season list is actually about.

All-season counts as winter

An all-season tyre is driven through the winter, so the stricter value applies to it. An unknown season falls back to the stricter value too, rather than guessing 'probably summer' and understating the risk.

Seasonal change campaign

The winter change is anchored in October, the summer change on Easter Monday; the lead window is configurable. The reminder goes out as an automation to the assigned driver and names the mounted set, target set, storage location, dimension and tread depth.

A missed change does not stay red forever

If a change is missed it rolls into next year. The useful statement in November is 'you are on summer tyres and the winter change was due', not 'you are 400 days late' — a permanently red row eventually goes unread.

Tyre types as a catalogue

Makes and types as a tenant-maintained catalogue, plus a fleet-wide set list that highlights sets below the minimum. A type in use is deactivated rather than deleted.

Driver submission with room to correct

When a driver reports the change themselves, the review confirms or corrects the change date and odometer. The odometer then joins the same series as every other reading — not a side path straight onto the vehicle.

Frequently asked questions

Because uneven wear is precisely the information a single number hides — and because a tyre worn on one side points at a suspension problem, not at mileage. Wherever a single number is needed — tyre list, driver report, lease return — the lowest value of the most recent measurement applies.

It does, which is exactly why both thresholds are configurable per tenant. The statutory value is preset to 1.6 mm following German regulation; you set it to the value that applies to you.

Through the same automation engine that already sends inspection and contract deadlines: a 'seasonal tyre change due' date source, a threshold trigger and the e-mail action with the assigned driver as recipient. No separate service, no second recipient logic.

Yes, with storage location and dimension on the set. It is not a bin-management system for storage racks — if you manage shelf positions, that is what warehouse management is for.

See this module with your own data

30 minutes, no sales pressure: we show the module in the context of your fleet — self-hosted in your data centre, GDPR-compliant, made in Germany.