The First Quarter After Fitting

The hardware arrives working. Whether anything changes depends almost entirely on the first three months.

Watch weekly

Devices reporting against devices fitted, which is never equal at the start.

Odometer agreement on a sample, which finds the devices that calculate rather than read.

Alerts fired and acted on, which is where the volume problem becomes visible.

And the first fault codes, which build the triage list.

Verify before trusting

One vehicle of each model, checked against its dashboard: odometer, fuel level, engine hours.

Because a field list from a vendor is a specification and the vehicle is the measurement.

Any model where they disagree needs a conversation before its data is used for anything.

Change one thing

Move service triggers to actual usage for one vehicle type, not the whole fleet.

See what it does to the workshop's schedule.

Then extend.

A fleet that switches everything at once produces a month of booking chaos and blames the system.

Build the triage list

Log every code with the vehicle, the date and what happened next.

After a quarter you have the beginnings of the three groups.

Without this log the list never exists, and every code remains either an emergency or noise.

Resist the reporting

Do not build dashboards in the first quarter.

The data quality is not yet established and a confident wrong number circulates further than a caveat.

Produce the three cost figures manually, which keeps the attention on whether the data is right.

Talk to the drivers again

A month in, ask what they have noticed.

Unplugged dongles, devices that came loose, warning lights that appeared after fitting.

And whether anything they were told has turned out not to be true, which is the question to ask directly and to act on immediately.

The review at week twelve

Devices reporting, odometer agreement, alerts acted on.

One service type switched to usage-based, with the result.

A triage list with three groups.

And an honest answer on whether the deployment is doing anything yet, which at twelve weeks is frequently "not much, and here is why" — which is fine if the reason is named.

Change one vehicle type at a time

Not the whole fleet.

Move service triggers to actual usage for one type, see what it does to the workshop's schedule, then extend.

A fleet switching everything at once produces a month of booking chaos and blames the system for an operational change nobody planned.

One type, one month, then the next.

A practical configuration prompt

During configuration, use remote employee monitoring for mobile operations to prompt questions about identifiers, ownership and output. Treat the page as a starting point and document each assumption.