Fleet & heavy-dutyGuide

Build a Preventive Maintenance Plan from Vehicle Evidence

Use manufacturer requirements, duty cycle and service history to plan work rather than guessing a universal interval.

Fleet coordinator reviewing a maintenance checklist beside delivery vans

A preventive maintenance plan should explain why a service is due, not merely repeat the date of the last visit. Vehicle configuration, manufacturer requirements, operating conditions and service history can all affect the plan. A single interval applied to every vehicle can conceal those differences.

Build the plan from verifiable vehicle information and current technical guidance. This article describes recordkeeping and scheduling, not a universal maintenance schedule or a vehicle-specific service procedure.

Establish the vehicle’s starting record

Confirm the vehicle identity, relevant configuration and available maintenance history. Record mileage, operating hours or other applicable usage measures with their dates and units. If a value is missing or uncertain, mark it as such instead of filling the gap with an estimate that later looks authoritative.

Distinguish documented completed work from a customer’s recollection or an old recommendation. Both may be useful, but they carry different levels of certainty. Identify any initial assessment needed before adopting an ongoing schedule.

Use the applicable requirements

Consult current manufacturer information for the vehicle and relevant components, and identify any additional requirements that apply to the operation. Evaluate how duty cycle and operating conditions affect the applicable schedule using the appropriate technical guidance.

Do not shorten or extend an interval simply because it fits the workshop’s marketing calendar. If a recommendation differs from the standard schedule, document the technical basis and the person qualified to make it. A report should be clear about what is required, what is recommended and what remains to be checked.

Separate maintenance from newly discovered repairs

A planned visit may reveal a condition outside the original service scope. Record the finding and obtain any additional authorization required before carrying out the extra work. The maintenance appointment itself is not blanket permission for unrelated repairs.

Use the inspection reporting guide to explain new findings. Keep observations, measurements and recommendations distinguishable. If the inspection is limited, state the limitation rather than allowing an incomplete check to appear comprehensive.

Schedule around real usage and availability

Coordinate the plan with the customer’s operating needs and the workshop’s capacity. For commercial accounts, identify who supplies updated usage information and who approves the planned downtime. A reminder based on outdated mileage may not represent the vehicle’s current position.

An illustrative fleet process could review the due list with the customer, confirm recent usage, identify required parts and agree on a booking. When the vehicle arrives, verify the information again. This is a planning example, not a prescribed compliance interval.

Preserve an auditable completion record

After the visit, record the actual service date, usage reading, completed scope and relevant results. Connect supporting documents to the correct asset. Do not reset a future service reminder merely because an appointment was booked or an invoice draft was created.

For U.S. motor carriers, consult the FMCSA Motor Carrier Safety Planner and the applicable regulations for the operation. The planner is a guide, and responsibilities can extend beyond the workshop. Confirm any inspection, documentation and qualification obligations with appropriate expertise rather than assuming an ordinary maintenance visit satisfies them.

Review changes, not only dates

Reassess the plan when the vehicle’s duty cycle, ownership, configuration or condition changes. Repeated unexpected findings may justify a technical review of the plan, but do not turn a small sample into a claim that a particular service prevents every failure.

Start with one vehicle and verify the chain from requirement to due calculation, booking, completion and next review. Use the heavy-duty workflow article for the commercial handoffs. When discussing SaSa Shop OS, ask how the current product handles the records and reminders you need. This article does not establish automated maintenance scheduling or regulatory compliance functionality.

All resources

YOUR PEOPLE. YOUR PROCESS. YOUR SHOP.

Your shop's next chapter.
Let's build it together.

Bring the work you do every day. Explore what SaSa could bring together, with a conversation shaped around your team.