These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Tire Management
- Features
- Tire inspections
Tire inspections
Record tire identity, tread depth and position before asking for a maintenance decision.
OverviewLoads Default List×
Tire Management · Tire inspections
New
Loads Default List
Loads
| Record number | Subject | Status | Owner | Organization | Promised delivery at | |
|---|---|---|---|---|---|---|
| LDS-51352 | Draft lds-844 | Draft | ORG-2122 | 06 Oct | ||
| LDS-52827 | Planned lds-395 | Planned | ORG-5835 | 07 Oct | ||
| LDS-57896 | Dispatched lds-410 | Dispatched | ORG-3962 | 21 Oct | ||
| LDS-27002 | In transit lds-180 | In transit | ORG-6598 | 10 Oct | ||
| LDS-76558 | Delivered lds-307 | Delivered | ORG-9600 | 09 Oct |
6 of 6 records
Draft lds-844Loads · LDS-51352
DraftOrganizationORG-2122
Promised delivery at06 Oct
Actual delivery at14 Oct
What you can do
Start with the tire being inspected
A useful tire observation identifies the physical tire and where it was fitted when the reading was taken. Tire Inspector records its serial, inspection date, position and tread depth in thirty-seconds of an inch. The observation stays with its organization and parent load so the maintenance discussion has an operating context. Use the load assignment to confirm the vehicle actually inspected, especially when dispatch has substituted equipment.
An earlier reading remains useful after a rotation. Keep the previous observation and add the later dated observation for the same serial. A changed position should be explainable from the maintenance evidence. Do not replace yesterday’s position merely to make every historical entry show where the tire is today.
How the work is organized
- Identify the tire. Use the serial visible on the tire and the agreed position vocabulary. Resolve an unreadable or disputed identity with Fleet Coordinator before requesting a decision about that tire.
- Record the observation. Enter the measured depth and actual inspection date while the inspection is Draft. An absent reading should stay absent until the inspector can obtain it; entering zero would communicate a different condition.
- Submit the reviewed record. Check the parent load, organization and supporting files before moving to Submitted. Maintenance Reviewer needs the exact observation being considered for rotation or replacement.
What to agree during setup
Agree how the team writes axle and wheel positions, how serials are checked and which measurement practice the workshop uses. Maintenance Reviewer supplies the operating criteria for a decision. A numerical reading by itself should never be presented as a universal replacement rule. Keep the measurement unit visible during imports and daily entry.
Choose a load whose assignment can be checked with the inspector. Agree how staff identify the relevant vehicle if that load has several assignments. Decide who corrects a mistaken serial before submission and how the team preserves an already reviewed observation when later evidence differs. Use the organization’s time zone consistently when comparing inspection dates.
Check the handoff on an actual case
During a rehearsal, Tire Inspector records tire TM-214 at the left rear position with a depth of 7 thirty-seconds. An earlier observation shows the same serial at another position. Maintenance Reviewer follows the dated observations and the supporting attachment before deciding whether the current request concerns rotation or replacement. The fleet’s maintenance policy governs the decision in this rehearsal.
Next, substitute the vehicle on the parent load. The inspector must still be able to explain which assignment belonged to the inspection. If the new assignment makes that unclear, stop the decision and resolve the evidence. A load reference alone should not cause the team to attribute the old reading to the replacement vehicle.
What your team sees
- Custody Board by Status — Follow tire inspection work from Draft through review and completion.
- Loading Handoffs Default List — Read the submitted tire observations and supporting context before the maintenance decision.
Follow the work through
Prepare and submit an inspection, then review rotation or replacement. Use the data model to prepare import mappings.
What it keeps track of
Data model- Tire inspections
- Tire inspection records supporting approval of a tire rotation or replacement, with tire serial lineage and vehicle position history
- Loads
- Freight loads from pickup to delivery with promised windows, freight value and lifecycle
- Load assignments
- Driver and vehicle assignments to loads with committed start and end times
- Vehicles
- Fleet vehicles with equipment class, capacity, readiness and external fleet id
- Record attachments
- Evidence files attached to loads with visibility and evidence type
Who uses it
Permissions- Tire Inspector
- , Maintenance Reviewer, Fleet Coordinator.
- Tire Inspector
- Records the observation; Maintenance Reviewer makes the independent decision.
- Fleet Coordinator
- Resolves vehicle identity and readiness questions.
Set up Tire Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.