FLEET MAINTENANCE & INSPECTION RECORDS
Fleet Tire Inspection Checklist: Pressure, Tread Depth and Maintenance Records
A tire check is not finished when a number is written down. The record must identify the tire, explain the finding and show who will follow it through.
Quick Answer
A useful fleet tire inspection checklist connects each tire position to its pressure, tread condition, inspection date and follow-up action. Record the measurement conditions and units, compare against the approved specification, assign unresolved findings and retain the recheck result. A spreadsheet is a recordkeeping aid, not an automatic roadworthiness decision.
In a busy fleet yard, "rear tire low" creates more questions than it answers. Which vehicle? Which axle? Inner or outer tire? Was the measurement taken cold? Was the issue repaired, or merely written on yesterday's sheet?
This guide helps fleet managers, maintenance supervisors and service teams build a repeatable record. It complements a pressure-measurement procedure rather than replacing one, and applies to manually maintained sheets as well as workflows that use exported gauge data.
1. Prepare the specification before collecting readings
Identify the vehicle, tire size, service application and approved inflation reference before starting. For commercial tires, pressure requirements depend on load and configuration; the sidewall maximum is not a universal operating target. Use the relevant vehicle and tire guidance. Take cold-pressure readings for comparison with the cold specification, and label warm or unknown conditions rather than treating them as equivalent. Michelin's commercial tire pressure guidance explains these distinctions.
Park and secure the vehicle using the site's procedure. Use suitable measuring equipment and follow its instructions, including verification or calibration requirements. Do not inflate a damaged or severely underinflated assembly without qualified assessment.
For measurement technique, see How to Check Tire Pressure Correctly. Here, the focus is what the team records and how it acts on the result.
2. Use a checklist that leads to an action
| Check | Record | Why the field matters |
|---|---|---|
| Vehicle and tire identity | Fleet vehicle ID, tire ID if assigned, odometer and wheel position | Keeps the finding attached to the correct asset, including after rotation |
| Inspection date | Date, inspector and, where needed, time and time zone | Separates a current check from an old or incomplete record |
| Pressure | Measured value, units, cold/warm/unknown condition, approved target and reference | Prevents comparison of unlike conditions or the wrong units |
| Tread depth and pattern | Specified measuring locations, units, readings and unusual wear observations | Retains more detail than a single unlabelled depth value |
| Visible condition | Cuts, cracking, bulges, foreign objects, irregular wear and valve concerns | Flags matters that pressure and tread numbers alone do not explain |
| Defect follow-up | Finding ID, required action, owner, due date, work order and status | Makes responsibility and the next step visible across shifts |
| Recheck and review | Date, new reading, measurement conditions and reviewer | Shows what changed without erasing the original finding |
The US DOT tire advisory identifies visible tire damage, irregular wear and inadequate tread among inspection concerns and directs issues to a mechanic. Read the DOT tire advisory. A visual check does not establish that a tire is structurally sound.
3. Give every wheel position an unambiguous name
Define a position map before the first inspection. Number axles from the front and define left/right from the vehicle's forward-facing orientation. For dual assemblies, identify inner and outer tires separately. Add the trailer or other asset ID when the combination includes more than one vehicle.
Example naming convention: A1-L-S means axle 1, left, single; A2-R-I means axle 2, right, inner; A2-R-O means axle 2, right, outer. This is a suggested internal convention, not a universal industry code.
Keep tire identity separate from position. After rotation, a tire may move while its wear history should remain traceable. Record the move date and old/new positions in the maintenance history; do not rewrite earlier inspections as if the tire had always occupied the new position.
4. Record pressure and tread without losing context
Pressure: keep the original reading
Keep the initial reading and the post-service result separately. Do not replace an out-of-target value with the adjusted number. If the condition is warm or unknown, record that limitation and follow the fleet's recheck procedure. Repeated loss at the same tire should prompt investigation rather than an endless sequence of undocumented top-offs.
Tread: specify where the measurement was taken
Follow the tire and gauge instructions for valid groove locations and measurement technique. If your procedure uses inner, center and outer positions, define those locations consistently and keep the readings separate. Do not measure on a tread-wear indicator or treat an average that conceals a low reading as a release decision.
Record irregular wear as an observation, not a diagnosis. A wear pattern can justify checking inflation, alignment or other vehicle conditions, but a CSV row cannot establish the root cause. If a point cannot be measured, leave the numeric field empty and explain why; zero would incorrectly look like a measured value.
5. Follow an abnormal finding through to review
Identify
Give the issue a finding ID linked to its vehicle, tire and position. Preserve the original reading and condition notes.
Assign
Name the responsible technician or team, required next action, due date and work-order reference.
Recheck
Add the subsequent measurement and review outcome. Leave the issue open when evidence or authorization is missing.
Use simple statuses such as open, awaiting_review and closed, with a written definition for each. A technician finishing work and a reviewer approving closure are different events. The status belongs to the finding, not to a blanket declaration that the entire vehicle is safe.
For suspected serious damage, unsafe inflation condition or an unresolved safety concern, follow the site's hold/escalation procedure and obtain qualified assessment. A due date is not permission to keep operating with a defect.
6. CSV example: one inspection event per row
The example below is synthetic. Vehicle IDs, measurements, targets and dates illustrate record structure only; they are not recommended pressure settings, tread limits or actual customer data. It is an independent fleet template, not the DG11-APP app's export schema.
Keep numbers in numeric fields and units in separate columns. Use ISO-style dates (YYYY-MM-DD), retain stable IDs and quote CSV text fields if they contain commas, quotes or line breaks. Archive the original device export unchanged, then map it into your working record. Protect free-text imports from spreadsheet formula execution under your organization's import policy.
record_id,record_type,inspection_date,vehicle_id,tire_id,wheel_position,odometer_km,pressure_condition,pressure_unit,target_pressure,measured_pressure,tread_unit,tread_inner,tread_center,tread_outer,condition_notes,finding_id,action_required,assigned_to,due_date,work_order_id,status,recheck_date,recheck_pressure,closure_byDEMO-R001,inspection,2026-10-16,DEMO-V001,DEMO-T001,A1-L-S,120000,cold,psi,100,100,mm,8.2,8.0,8.1,no_visible_defect_recorded,,routine_record,,,,recorded,,,DEMO-R002,inspection,2026-10-16,DEMO-V001,DEMO-T002,A2-R-O,120000,cold,psi,100,90,mm,7.0,6.8,6.9,pressure_below_demo_target,DEMO-F001,technical_review,DEMO-TECH,2026-10-16,DEMO-WO001,open,,,DEMO-R003,recheck,2026-10-17,DEMO-V001,DEMO-T002,A2-R-O,120000,cold,psi,100,100,mm,,,,demo_work_order_recheck,DEMO-F001,review_recheck,DEMO-REVIEWER,2026-10-17,DEMO-WO001,awaiting_review,2026-10-17,100,
In this example, DEMO-R002 opens finding DEMO-F001; DEMO-R003 records a later recheck using the same finding ID. Its status remains awaiting_review. The original pressure reading is retained, and the recheck does not claim an approved return to service.
For production use, add your approved-specification reference and inspector identity, plus timestamps if checks can occur more than once a day. Do not assume every column can be captured or exported by a connected gauge: owner, due date and work-order fields may belong in your maintenance system.
7. Review the records for gaps, not just low readings
- Coverage: compare inspected positions with the vehicle's actual position map, including inner duals and any spare covered by the program.
- Open work: filter findings without an owner, due date, recheck or review outcome.
- Repeated events: look for recurring pressure findings by tire ID, without assuming repetition proves the cause.
- Data quality: check mixed units, missing conditions, impossible entries, duplicated IDs and measurement fields that were filled with zero for "not checked."
- Asset changes: reconcile tire replacements and rotations so a new tire does not inherit an old tire's readings.
Set inspection frequency through the fleet program, manufacturer guidance, operating conditions and applicable requirements. Keep pre-trip observations, scheduled measurements and defect follow-up distinguishable rather than calling every record the same inspection.
Where DG11-APP can support the workflow
The LEMATEC DG11-APP combines tire-pressure and tread-depth measurement with Bluetooth connectivity, iOS/Android app support and CSV export according to its official product page.
Those functions make it a candidate for evaluating measurement capture. They do not establish support for every fleet-management field, automated defect decisions or a direct connection to your maintenance software.
Before a bulk purchase, request a current sample CSV and app demonstration. Check available columns, units, vehicle/tire identifiers, position assignment, timestamps and how corrections are handled. Test the workflow on your own vehicle layout, including access to inner dual valves where relevant, and confirm which record fields must be maintained elsewhere.
Frequently Asked Questions
What should a fleet tire inspection checklist include?
Record the vehicle and tire identity, wheel position, inspection date, odometer, pressure condition and units, approved pressure target, measured pressure, tread readings, visible defects, action owner and follow-up result.
How often should fleet tires be inspected?
Set the schedule through the fleet maintenance program, vehicle and tire guidance, operating conditions and applicable requirements. Keep pre-trip observations separate from scheduled measurements and defect follow-up.
Can one tire pressure target be used for the entire fleet?
No. Use the approved specification for the particular vehicle, tire, load and axle configuration. Record the specification source rather than assuming one PSI value fits every vehicle.
Is the CSV example the DG11-APP export format?
No. It is an independent fleet recordkeeping example. The DG11-APP product page lists CSV export, but the actual app columns and supported record fields must be confirmed with LEMATEC.
Does closing an inspection record approve the vehicle for service?
No. Administrative closure does not replace the fleet's authorized technical review, required repairs or return-to-service procedure.
About the Author: Vic Chen
Vic Chen shares LEMATEC application and procurement guidance for technical buyers. This guide separates fleet recordkeeping suggestions from verified device functions and the technical decisions that require qualified review.
Connect with Vic Chen on LinkedInEvaluate the measurement-to-record workflow
Review DG11-APP for your fleet's pressure and tread-depth checks. Ask for the current app workflow and sample export before deciding how it fits your maintenance records.
Explore DG11-APP