Vehicle Inspection and Documentation
This domain covers how a technician performs a systematic inspection and records what was found. The core skill is a repeatable walk-around and under-hood sequence so nothing is missed: start high and outside (lights, mirrors, glass, body damage, leaks under the truck), move to the engine compartment, then work front-to-rear along the chassis. Understand the difference between a safety inspection (defects affecting safe operation) and a maintenance inspection (wear and serviceability), and know that documentation must be objective-record measurements and observations, not opinions.
Know the elements of a good inspection record: vehicle identification (VIN/unit number), odometer, date, technician identification, item inspected, condition found, action taken, and parts used. Understand DVIR (driver vehicle inspection report) concepts: drivers report defects, the carrier reviews and certifies repairs, and the record is retained. A trap is assuming the technician signs off a driver's report without verifying the repair.
Common question traps: confusing "recommend" with "repair," skipping the post-repair verification, or documenting a defect without noting whether it was corrected. Another trap is failing to distinguish a leak that is a weep (monitor) from an active leak (repair). Also watch for questions about inspection intervals-condition-based findings drive service decisions more than a single mileage number.
Rule of thumb: if you did not write it down with a measurement or clear description, it did not happen. Worked example: you find a cracked spring hanger. Correct documentation: note location, describe the crack (length, orientation), mark it out of service if it compromises safety, record the repair or referral, and re-inspect after repair before returning the truck to service.