The maintenance half of a facility audit is narrower than carriers fear and more specific than they expect. Four record families, and the one that is usually missing is the fourth.
Key takeaways
Ontario publishes the scope. A Ministry of Transportation facility audit includes an examination of records related to driver qualifications, driver training, driver hours of service, driver behaviour, collision reporting and review, vehicle inspection, maintenance and repair, and any related supporting documents. The maintenance half of that is the last two items, and it resolves into four families:
Carriers reliably hold the first three and reliably struggle with the fourth, because the first three are generated by someone whose job it is to generate them and the fourth depends on somebody closing a loop.
In Ontario an annual safety inspection valid for twelve months is required for most trucks, trailers and converter dollies, alone or in combination, with a total gross weight, registered gross weight or manufacturer’s gross vehicle weight rating of more than 4,500 kg, for tow trucks regardless of weight, and for concrete pumps and mobile cranes. A six-month cycle applies to vehicles with seating capacity for ten or more passengers and to school-purposes and accessible vehicles. These inspections must be completed by a licensed motor vehicle inspection technician at an inspection station licensed by the Ministry of Transportation, and their content is based on Canada’s National Safety Code, Standard 11, Part B — power train, suspension, brake systems, hydraulic and air brakes, steering, instruments and auxiliary equipment, lamps, electrical system, body, tires and wheels, and coupling devices.
If a unit fails, Ontario allows the repaired vehicle to be returned to the same inspection station for re-inspection within 10 days, and repairs need not be done at the inspecting facility. Keep the failure report as well as the pass. An audit trail that shows a failure, a repair and a pass is stronger evidence of a working programme than a file containing only passes.
British Columbia runs the same idea on a different clock, and it is worth naming because carriers with BC-plated units get this wrong. An inspection certificate of approval expires on the last day of the sixth month following issue by default, but twelve months applies to a commercial trailer other than one used with a logging truck or equipped with a dump box, and to a commercial vehicle other than a bus, taxi or logging truck with a licensed gross vehicle weight over 8,200 kg but not more than 17,300 kg. An interim certificate expires 14 days after issue, and a copy of the inspection report must be carried in the vehicle.
This is the family that separates a programme from a habit. Ontario states that preventative maintenance inspections must be part of an operator’s maintenance plan and schedule, and must be done by a qualified technician at prescribed intervals. Three testable things sit in that sentence: there is a plan, it specifies intervals, and the person doing the work is qualified.
So the audit-ready version is a document, not a folder. One page per vehicle class stating the interval basis (distance, hours or calendar), the inspection content at each interval, and who is authorised to perform it — plus the completed inspections showing the intervals were actually met. A carrier that services “when it comes in” can produce invoices but cannot produce a schedule, and an auditor can tell the difference in about a minute.
These are driver-generated and they are also maintenance records, because they are the input to the repair loop. Ontario requires the driver to record any defects discovered on the inspection report and notify the operator, and to record “no defect” where none is found. British Columbia sets out the report contents in the regulation: plate, unit or trailer number where applicable, any defect in each listed item, any other defect that may affect safe operation, or a statement that no defect was discovered, plus date and signature.
Two audit-relevant habits. File them by unit as well as by date, because the question an auditor asks is about a vehicle, not a week. And keep the “no defect” reports — their absence looks like missing inspections, not like clean trucks.
Here is the failure mode, stated plainly. A driver reports a defect. The shop fixes it. Nobody writes down which repair answered which report. Six months later the auditor has a stack of inspection reports showing defects and a stack of invoices showing work, and no way to connect one to the other. The carrier did nothing wrong operationally and cannot demonstrate it.
Ontario puts the obligation on the operator: the operator is required to repair any defects that do not meet the performance standards, and for a major defect the vehicle must be repaired prior to being driven. British Columbia states the record duty directly: the owner must maintain, during the last three years of ownership and for six months after disposal, a record of each inspection and of every replacement and repair made to the vehicle and each component following each inspection.
The mechanism that closes the loop is a work order carrying the defect reference. A work order workflow for a small shop sets out how to run it with two people and no software.
When those periods conflict, keep to the longest. Nobody has ever been penalised for retaining a repair record too long.
Worked example: two hours that changed an audit outcome
A carrier with eight power units and fourteen trailers had every annual inspection certificate, a folder of shop invoices going back four years, and a filing cabinet of daily inspection reports in date order.
The gap surfaced during a voluntary audit the owner had requested — Ontario allows an operator to request a voluntary facility audit to improve its safety rating, with the caveat that violations found during a voluntary audit can still result in charges. The auditor picked one trailer and asked to see the life of a single reported defect.
The carrier could show the inspection report where the defect was raised. It could show an invoice from the same week with work on that trailer. It could not show that they were the same event, because the invoice described the work and not the defect.
The fix took two hours and no software. Every reported defect now gets a sequential number written on the inspection report. The shop writes that number on the work order. The work order records unit, odometer, the complaint as reported, the cause found, the correction made, parts, technician and date. Invoices from outside shops get the number written on them by whoever authorises the work.
The next audit tested three defects at random and closed all three in under ten minutes. The maintenance had never been the problem.
In British Columbia, yes — the obligation runs for six months following disposal, unless the records are delivered to the purchaser with their consent, in which case the purchaser must retain them as if they had owned the vehicle. Handing the file over at sale is both good practice and a way of discharging the duty.
For the tax side the Income Tax Act contemplates it directly, requiring records kept electronically to be retained in an electronically readable format for the retention period. For the maintenance side, what matters is that the record exists, is complete and can be produced — a scanned work order with a legible defect reference is a better record than a paper one nobody can find.
The other five families on the Ontario list: driver qualifications, driver training, hours of service, driver behaviour and collision reporting. Orientation is where several of those records are created — see what driver orientation should cover.
In Ontario, yes. The Ministry allows an operator to request a voluntary facility audit by completing a request form. Read the caveat first: violations identified during a voluntary audit may result in charges being laid against the operator, driver or both. It is a real option, not a free rehearsal.
Number your defects and put the number on the work order. It costs nothing, requires no system, and closes the one gap that is present in most small-carrier files.
A short call is enough to test three defects at random against your own records and tell you whether the loop closes.
