The compliance object is not the oil change. It is the written plan that says when the oil change was due and the record that says it happened.
Key takeaways
You set preventive maintenance intervals inside a written maintenance plan and schedule that you can produce on demand, using the manufacturer’s recommendations as the floor and tightening them for the duty cycle the unit actually runs. Ontario states the requirement plainly: preventive maintenance inspections must be part of an operator’s maintenance plan and schedule and must be done by a qualified technician at prescribed intervals. British Columbia goes further and makes the plan itself a record a carrier must maintain, alongside its safety plan, at its principal place of business.
So the compliance object is not the oil change. It is the document that says when the oil change was due, the record that says it happened, and the ability to put the two in front of an auditor.
National Safety Code Standard 11, which the Canadian Council of Motor Transport Administrators publishes as Commercial Vehicle Maintenance and Periodic Inspection (revised January 2020), is the national reference. CCMTA states that all provinces and territories use the National Safety Code as the cornerstone of their commercial vehicle regulatory framework, with standards either adopted by reference into jurisdictional regulation or mirrored in provincial and territorial laws. Ontario says its safety inspection requirements are based on Standard 11, Part B.
The standard sets out what a maintenance and inspection program has to contain. It does not hand every carrier a single kilometre figure, because a highway tractor running long and light and a city unit doing forty stops a day do not wear at the same rate. Buy the current text from CCMTA or your regulator rather than working from a chart on a supplier’s wall — that is how out-of-date intervals spread through an industry.
1. The manufacturer’s service intervals. These are the starting point and the defensible floor. Where a component maker specifies an interval — brake adjustment checks, wheel-end service, aftertreatment maintenance — that interval belongs in the plan with the source named.
2. The duty cycle. Kilometres are a poor proxy on their own. Engine hours capture idle time that kilometres miss; door cycles, lift cycles and reefer running hours capture wear that neither captures. A schedule with one trigger will be too tight for half the fleet and too loose for the other half.
3. Your own defect history. The daily inspection reports are a free reliability dataset. If the same component appears on trip inspection reports before every scheduled service, the interval is wrong for that unit.
4. The periodic inspection date. The annual or semi-annual certificate is a fixed point in the year. Scheduling a full preventive service shortly before it converts the certificate inspection from a discovery exercise into a confirmation.
Worked example: setting intervals for a mixed five-unit fleet
The fleet. Two highway tractors averaging long single-drop runs, one regional tractor on multi-stop work, two trailers, one of them a reefer.
Trigger choice. The highway units run to a kilometre trigger with a calendar backstop. The regional unit runs to engine hours, because its kilometres badly understate its wear. The reefer carries a second schedule on refrigeration unit hours, independent of the trailer’s own service.
Alignment. Each unit gets its heaviest service in the month before its periodic inspection, so the certificate inspection is not the first time anybody looks at the brakes.
Feedback. Every trip inspection report is coded against a component. After two quarters the regional unit shows repeated air-system defects, so its interval moves in and its task list gains an air-dryer check.
What is produced on request. The plan, the schedule, the work orders against each unit, and the defect reports showing that each reported defect was cleared and certified before the vehicle moved again.
A schedule that only works when the truck is empty is not a schedule. Two habits keep it alive. First, put the service window in the same system that plans the loads, so a unit due for service is visibly unavailable rather than notionally due — the same discipline that makes time-stamped evidence work in billing. Second, treat a deferred service as an event that has to be recorded and approved, not as a silent slip. Deferrals happen in every fleet; undocumented deferrals are what an audit finds.
Ontario draws the line clearly. Certificate, annual and semi-annual inspections are done by a licensed motor vehicle inspection technician at a licensed station. Preventive maintenance inspections sit inside your plan and are done by a qualified technician at prescribed intervals. Daily inspections are done by the driver or another person on the operator’s behalf. Details of the first are in annual vehicle inspection in Ontario, and the record-keeping consequences of all three are in how long to keep inspection reports.
Provinces set the periodic inspection cycle — twelve months for most heavy trucks and trailers in Ontario, six months for most commercial vehicles above 17,300 kg in British Columbia — but the preventive maintenance interval between those inspections is yours to set and defend within your plan. That is why the plan matters: it is the document that makes your interval a decision rather than an accident.
If it runs under your safety certificate, its condition is your responsibility. Ontario’s CVOR program puts the mechanical safety and condition of the vehicle and fleet on the operator, including setting up a regular maintenance schedule and keeping the maintenance and repair records. Whose name is on the finance agreement does not change that.
Tighten, do not loosen, and write down why. Shortening an interval on the basis of your own defect history is a defensible engineering decision. Extending one past the manufacturer’s recommendation is a decision you would have to justify after a failure.
Deciding an interval is judgement and stays with the person who signs the plan. Everything downstream is mechanical: reading odometer and engine-hour data as it arrives, raising the work order when a trigger is hit, matching the completed work order back to the unit file, coding defects from daily reports so the pattern is visible, and flagging any unit whose service was deferred without an approval. That is exactly the kind of repetitive, high-volume record work a small carrier does badly by hand and never has time to fix.
A 30-minute call is enough to see how service triggers, work orders and defect history could hold together on their own.