Maintenance: logging service history and reading your rhythm

What the Maintenance tab shows

Every restoration operator runs a small fleet of trucks, vans, and trailers, and every one of them needs oil changes, tires, brakes, and the occasional repair. The Maintenance tab is where that service history lives: one row per event, across every vehicle you track. It is also where Verinode reads that history back to you as a rhythm, a Maintenance Rhythm tile that mines your own service dates for the typical interval between visits and flags which vehicles have gone quiet longer than their own normal pattern.

Verinode does not schedule service or decide when a vehicle is due. It reads the dates you log, works out what "normal" looks like for your fleet, and surfaces the vehicles that have drifted from it. You decide what to do about it.

Where to find it

Open Fleet from the sidebar at iq.verinode.ai/fleet. Fleet is a horizontal card slider with seven tabs: Roster, Maintenance, Compliance, Insurance, Drivers, Accidents, Costs. Maintenance is the second card.

You can also reach it from the Fleet home page (the same /fleet route, one level up from the slider): the Explore row carries a Maintenance tile (amber accent) with a running count of service records, and a Maintenance Rhythm tile (steel accent) with the mined cadence read. Clicking either tile opens the Maintenance slider card directly.

The Maintenance list

The list is a simple, reverse-chronological feed: newest service record first, across every vehicle in your fleet. Above the list, a line of context reads, for example, "6 service records across the fleet. Click a row to open the vehicle." (singular "1 service record" when you have exactly one). A + Log Service button sits beside it.

Each row shows:

• Service type, a pill in the left margin: Oil Change, Tire Replacement, Brake Service, Transmission, Battery, Annual Inspection, DOT Inspection, Collision Repair, Mechanical Repair, Detailing, or a custom label you typed in for Other.
• Vehicle name, the vehicle the service was logged against.
• Notes, if you added any, shown as a small line under the vehicle name.
• Cost, right-aligned, formatted as a dollar figure ($89, $1.2k, $2.4M as the number grows). A record with no cost logged shows a dash.
• Date and mileage, under the cost: the service date, and the odometer reading at the time of service if you captured one (e.g. "Mar 12, 2026 · 84,210 mi").

Click any row to open that vehicle's profile, where you can see this record alongside the rest of the vehicle's roster detail, compliance events, and costs.

Empty state. Before you have logged anything, the tab reads: "No service history logged yet. Track oil changes, tire replacements, brakes, and repairs here." The Log Service button is disabled with the hint "Add a vehicle first" until at least one vehicle exists on your roster: you cannot log a service record without something to attach it to.

Logging a service record: the Log Service modal

Click + Log Service from either the Maintenance tab or the Fleet home tile to open the modal. It asks for:

• Vehicle (required). A dropdown of your active vehicles, each shown as name, vehicle type, and license plate for disambiguation (e.g. "Truck 3 · Box Truck · ABC-1234"). Retired, sold, and totaled vehicles do not appear, so you cannot log a service against a vehicle that has left the active roster.
• Service type (required). A dropdown of the same eleven categories that appear as pills in the list: Oil Change, Tire Replacement, Brake Service, Transmission, Battery, Annual Inspection, DOT Inspection, Collision Repair, Mechanical Repair, Detailing, Other.
• Service date (required). Defaults to today.
• What kind of service (required only when you pick Other). A free-text field for anything the eleven fixed categories don't cover, for example "Diff fluid swap" or "Suspension overhaul." This becomes the label shown in the list in place of a generic "Other" pill.
• Mileage at service (optional). The odometer reading when the vehicle came in.
• Cost (USD) (optional). What the service cost, entered in dollars and cents.
• Notes (optional). A free-text field. There is no separate vendor field on this form, so if you want the shop or vendor on record, note it here, for example "Vendor: Jiffy Lube, synthetic oil + filter."

Click Log Service to save, or Cancel to discard. While saving, the button reads "Saving…" and the form locks. A few validation rules apply before the save fires:

• You must pick a vehicle and a service date.
• If you pick Other, you must fill in the "What kind of service" field, so nothing lands in your history labeled simply "Other" with no context.
• Mileage and cost, if entered, must be non-negative numbers.

Once saved, the record appears at the top of the Maintenance list and folds into the Maintenance Rhythm read described below.

Maintenance Rhythm: reading your fleet's cadence

The Maintenance Rhythm tile, in the Explore row on the Fleet home page, is where your service history becomes a pattern instead of just a list. It answers two questions in your own data: how often do vehicles in your fleet typically come in for service, and which vehicles have gone longer than that without one.

How it's mined. For each vehicle with at least two logged service dates, Verinode measures the gap in days between each consecutive pair of visits. Same-day duplicates or out-of-order entries contribute no gap. Every gap across every vehicle is pooled together, the most extreme outliers are dampened before the math runs so one unusually long stretch (a truck parked for a season) doesn't distort the whole fleet's read, and the median of that pooled set becomes your typical service interval.

What the tile shows. The headline number is that median interval, in days (formatted as, for example, "62d"). The line underneath reads one of:

• "On rhythm", when every vehicle's most recent service is within its normal window.
• "N overdue for service", when one or more vehicles have gone meaningfully longer since their last visit than the fleet's typical gap, roughly half again as long as the median before a vehicle is flagged, so a vehicle that's merely coming due doesn't get flagged as late.
• "Add service dates to map your rhythm", when there isn't yet enough history across your fleet for the median to mean anything. The tile shows a dash instead of a number in this state. This is not a bug, it just means you need a bit more logged history, spread across visits, before a rhythm is worth publishing. Keep logging service records and the tile fills in on its own.

Below the numbers, the tile's preview shows a row of dots, one per vehicle with at least one logged gap, with the overdue ones flagged in ember (red) against the rest in a neutral tone, so you can see the overdue share of your fleet at a glance before you even open the tab. Click the tile to jump straight into the Maintenance list.

Best-practice example

Say your Maintenance Rhythm tile reads "58d" with "2 overdue for service." That tells you your fleet typically comes in every two months or so, and two vehicles have gone well past that. Open the Maintenance tab, sort by the vehicle names showing the overdue flag on the home tile's dot preview, and check their last logged date against today. If a van's last oil change was four months ago against a fleet norm of two, that's a concrete, dated fact, not a guess, and it's worth a call to the shop before the gap turns into the kind of repair bill that shows up in the Costs tab instead of the Maintenance one.

Related reading

• Fleet Roster tab, the vehicle-by-vehicle detail this tab's rows link back into.
• Fleet Compliance tab, for dated obligations like DOT inspections and registration renewals (a different, deadline-driven read from the interval-based Maintenance Rhythm).
• Fleet Costs tab, for the recurring dollar side of running the fleet.
• Connecting your data, for how vehicle and service data flows into Verinode.
• Understanding your margin, for how vehicle costs roll into what you keep.

Data sources