Commercial vehicle inspection schedule in Canada: three calendars to keep apart

A Canadian commercial fleet usually needs three connected inspection schedules: the driver's trip inspection, the carrier's preventive-maintenance programme, and any mandatory annual or semi-annual periodic inspection. They have different purposes, people and legal triggers. A daily check does not renew a periodic inspection certificate; an annual sticker does not replace a driver defect report; a repair invoice does not prove the next preventive inspection was planned. The actual frequency depends on vehicle class, use, registered jurisdiction and applicable provincial or territorial law.

The Canadian Council of Motor Transport Administrators (CCMTA) National Safety Code includes Standard 11 for maintenance and periodic inspection and Standard 13 for trip inspection. The standards support harmonisation, but a carrier must use the law of the relevant province or territory and applicable interjurisdictional rules. Do not copy an Ontario schedule into a British Columbia or Alberta fleet without checking local requirements.

Make one asset-by-asset schedule

Start with a register for each truck, tractor, trailer, bus or other covered unit. Include the trailer separately; a tractor's inspection evidence does not automatically cover a trailer. Record the registered province, weight/class, passenger use, routes, owner/operator, unit identifiers and whether the vehicle is leased or subject to another party's maintenance arrangement. Then determine which trip, preventive and periodic rules apply to that unit.

Eligibility first, dates second. A date calculator cannot decide whether a particular light truck, school bus, motor coach, trailer, farm vehicle or leased unit falls within the same inspection rule as a standard commercial truck. Confirm the category under local law and keep the source/date with the fleet record.

1. Trip inspection and defect response

Trip inspection is the driver's or other authorised person's check of the vehicle and its condition for use. It uses a prescribed schedule and a report where required, with minor and major defect handling. For an Ontario example, the MTO truck handbook describes the 24-hour report process, Schedule 1 for trucks/tractors/trailers, recording and reporting minor defects, and not driving with a major defect. The controlling text is Ontario Regulation 199/07, which contains different schedules for different vehicle types. The Ontario example is not a national 24-hour rule for every unit.

Record who completed the check, which prescribed schedule applied, when it was done, the vehicle/unit, observed defects and the operator's response. Keep the report and schedule available as the local law requires. Do not mark a major defect “repaired” based only on a driver tick box; identify the person who assessed/repaired it and the release evidence. A defect found during a trip may require action even when the morning report showed no issue.

The carrier must train drivers and supervisors to distinguish minor from major items in the applicable schedule. A generic “lights/tyres/brakes OK” list is not a substitute where the law prescribes specific defect classifications.

2. Preventive maintenance inspections

Preventive maintenance is the carrier's planned system to keep vehicles safe and correct defects before a breakdown or enforcement event. NSC Standard 11 expects a systematic programme for covered commercial vehicles and notes that the standard itself does not specify one predetermined time interval for every maintenance cycle. The operator sets intervals suited to equipment, usage and condition, subject to any province's maximum time or distance rule. A monthly service for one duty cycle may not be adequate for another; the manufacturer's instructions, prior defects and actual use matter.

Your maintenance schedule should identify inspections by system or service level: brakes, steering, suspension, tyres, lights, coupling, wheels, body, accessibility and emergency equipment where applicable. State the time, distance or engine-hour trigger, who performs the work, the standard used, parts/measurements, defects found, repair authority and next due point. Track overdue work as an operating decision, not simply a calendar reminder.

Example: A dump truck repeatedly develops brake defects on a steep, stop-start route. The carrier's interval should be reviewed using the defects and service pattern. Keeping the old interval because “annual inspection passed” misses the change in actual duty. A certified periodic pass is a snapshot against a specific standard; it does not eliminate ongoing maintenance duties.

3. Mandatory periodic inspection

Periodic mandatory commercial vehicle inspections are performed to the applicable jurisdiction's standards by authorised inspection personnel/facilities. They may be annual or semi-annual depending on class and jurisdiction. Ontario's commercial inspection page distinguishes annual/semi-annual certified DriveON inspections, preventive maintenance and daily trip checks. It also discusses some out-of-province acceptance conditions. NSC Standard 11 provides the shared maintenance/periodic inspection framework but refers repeatedly to applicable jurisdiction requirements. The schedule must record the actual rule for each unit.

Do not assume an inspection passed because a decal appears current; check the correct unit and certificate/report. Do not assume a passed home-province inspection is automatically accepted in every operating jurisdiction without checking the reciprocity rule. Separate emissions or specialised vehicle checks may also apply.

Build the working calendar

For each unit, put three types of event on the calendar, not one “inspection due” label:

1. Trip checks: the required driver/inspector event and defect handling for each operating period.
2. Preventive maintenance: time/distance/hour triggers, qualified work, follow-up and revised intervals after defects or duty changes.
3. Periodic certificate: statutory due date, booking, pass/repair/reinspection, proof in vehicle and new due date.

Assign one role to monitor upcoming dates and a different competent role to certify repairs or release safety-critical defects. A dispatch process should see vehicles on hold. Build in lead time for appointments and parts; a reminder sent on expiry day is too late if the unit must be inspected before further use. Maintain trailers, spare vehicles and seasonal equipment in the same system so an infrequently used unit does not return to service with stale evidence.

Weekly fleet review card

Common schedule mistakes

• One interval for all provinces and vehicle types. The NSC harmonises, but provinces and territories implement and exempt differently.
• Treating daily, preventive and periodic inspection as the same event. Each has different evidence and purposes.
• Forgetting trailers and combinations. Each relevant unit needs its own classification and record.
• Closing a defect with a note but no repair or release evidence. A safety-critical issue is an operating hold.
• Using a fixed maintenance interval after duty changes. Route, load, environment and defect history can require a new interval.
• Assuming a sticker proves every requirement. Check the report, vehicle identity, defect correction and local evidence rules.

Complys and the product boundary

The proposed /ca/commercial-vehicle-compliance-software money route in the manifest was not confirmed live in this writer-side search. The observed Complys Canada pricing page lists transport/fleet and a vehicle check form builder for a plan, but public marketing does not establish an implemented inspection scheduler, defect hold or provincial-rule engine. Before linking a money page or CTA, the integrator must verify the exact live route, plan and function. A safe future CTA is: Ask Complys to demonstrate how its current Canadian fleet records can store each unit's trip reports, maintenance and periodic certificates. Do not claim that software performs a certified inspection, classifies legal vehicle coverage, signs off repairs or guarantees NSC compliance.

Source, claim, owner, link, product and writer-side QA register — 5 October 2026

Terminal writer-side disposition: READY. No live site or Complys repository was modified.