Fleet Maintenance Checklists: Preventive Checks by Interval

A fleet maintenance checklist works as a set of layers, each with its own interval and owner: daily driver walk-arounds, weekly yard checks on fluids, tyres, lights, and bodywork, and tiered A/B/C services triggered by mileage, engine hours, or calendar time — whichever arrives first. The layers feed one defect pipeline, so a fault found at any level becomes a tracked repair rather than a note in a cab. Structured this way, preventive maintenance stops being a binder and becomes a schedule the fleet actually runs.

The argument for prevention in fleet is brutally simple: a planned repair happens in your workshop, overnight, at parts cost; the same fault unplanned happens on a motorway shoulder, with a tow, a missed delivery, and an angry customer attached. The checklist structure below is how you keep repairs in the first category.

Layer 1 — Daily: the driver walk-around

The daily check belongs to the driver, takes minutes, and catches the failures that develop overnight or during a shift: lights, tyre damage, leaks, load equipment. It's covered in depth in our DVIR-style pre-trip inspection checklist, so here only its role in the maintenance system matters: the daily check is your highest-frequency sensor, and its defect reports are the leading indicator your PM schedule learns from. A fleet whose drivers report honestly needs fewer surprises absorbed by the workshop.

Layer 2 — Weekly: the yard check

Weekly checks catch slow-moving deterioration that dailies skim past. Done by a driver with extra training, a yard supervisor, or a technician, per vehicle:

1. Fluid levels checked cold and recorded as numbers: engine oil, coolant, brake/clutch fluid, power steering, washer, AdBlue/DEF where fitted
2. Tyre pressures with a gauge on all positions including inners and spare; tread depths recorded per tyre
3. Battery: terminals, mounting, visible condition; test on vehicles with a history
4. All lights and reflectors, including the ones a solo daily check struggles to verify (brake lights, trailer boards)
5. Wipers, washers, horn, mirrors, and glass
6. Bodywork and underside scan: new damage, corrosion, hanging components, fresh leaks on the parking spot
7. In-cab equipment: extinguisher, first aid, triangles, tachograph/telematics unit
8. Documents current: insurance, inspection certificates, permits

Recording numbers — pressures, tread depths — instead of ticks is what makes the weekly check valuable. A tyre losing 0.2 bar a week is invisible as a tick and obvious as a trend.

Layer 3 — Scheduled services: A, B, and C

Most fleets tier their workshop services. Contents vary by vehicle class and manufacturer schedule, but the shape is consistent:

Three scheduling rules keep the tiers honest:

• Dual triggers, whichever first. Mileage or engine hours for high-utilisation vehicles; calendar time for the van that barely moves but whose tyres, battery, and seals age anyway.
• The next service is created when this one closes. Completing a B-service at 84,300 km schedules the next trigger immediately — no separate planning step to forget.
• Manufacturer schedule is the floor, not the ceiling. Duty cycle (urban stop-start, construction sites, refrigerated bodies idling) shortens real intervals below the book.

If your scheduling currently lives in a spreadsheet with a colour code, the general mechanics of making recurring work self-scheduling are covered in the guide to scheduling recurring tasks.

The defect pipeline: one path from any layer

A finding from any layer — driver daily, yard weekly, or workshop service — should land in the same pipeline:

1. Defect recorded with vehicle, reporter, photo, and severity
2. Classified: vehicle grounded, repair scheduled, or monitor
3. Assigned to a workshop owner with a due date
4. Repaired, with parts and work noted
5. Verified and closed — by someone other than the repairer for safety-critical items

The verification step is the one fleets skip and regret. "Fixed" declared by the person who fixed it is an assertion; a closed corrective action with photo proof is a record. This is standard CAPA discipline applied to metal.

The pipeline also generates your best planning data. Defects clustered on one vehicle argue for early replacement; clustered on one component across the fleet, for a shorter inspection interval or a parts-supplier conversation; clustered on one depot, for a training look.

Measuring whether the programme works

You don't need a wall of KPIs. Four numbers tell the story:

• PM completion on time — the discipline metric; below target, everything else follows
• Overdue defects — pipeline health; an ageing open-defect list predicts breakdowns
• Breakdowns (unscheduled repairs) per vehicle — the outcome the whole programme exists to reduce
• Vehicle availability — the number operations actually feels

Review them weekly at fleet level, monthly per vehicle. A rising breakdown count with high PM completion means your intervals or checklists are wrong; with low PM completion, it means your schedule is fiction.

Running the schedule on software

Fleet PM dies in spreadsheets for a predictable reason: the spreadsheet records intentions and nobody sees the misses until the breakdown. Fleets run this on Task10x by scheduling daily, weekly, and service-tier checklists per vehicle and depot, recording readings with min/max limits, requiring photo evidence on checks and repairs, and letting failed items auto-create corrective actions tracked to verified closure — with missed services flagged the same day and a live dashboard of completion and open defects across depots. Setup patterns for transport teams are on the fleet industry page, and the template library on the product page includes inspection checklists to start from.

Preventive maintenance is a promise the fleet makes to its own future: pay in scheduled minutes now or unscheduled days later. Layer the checklists, wire every finding into one pipeline, and watch the misses — the rest follows.