What changes when a program exists
Without a program, tire decisions get made one at a time, by whoever is standing next to the truck. A driver picks a tire at a counter. A shop fits whatever is in stock. A casing goes in the scrap pile because nobody said otherwise.
A program moves those decisions to a desk, ahead of time, so the person at the truck is following a rule rather than inventing one. The gain is consistency, and consistency is what makes tire costs predictable.
Step 1: List what you actually run
Every unit, with its type, its tire size at each position, and where it is based. Fleets are often surprised at this step, because sizes and specs have drifted over years of reactive buying. Two trucks of the same model may be running different tires for no reason anyone remembers.
The list is also what a supplier needs to quote properly. See commercial and fleet for how Purcell approaches mixed fleets.
Step 2: Set a specification by position
Steer, drive and trailer positions do different jobs, and each gets its own spec: size, load range, tread type, and whether retreads are allowed there. Write it down. A spec that lives in one person's head disappears when that person is on vacation.
Standardizing sizes where you can is worth the effort. Fewer sizes means less stock to hold, fewer wrong fits, and an easier time at the roadside.
Step 3: Decide the pull point
The tread depth at which a tire comes off, by position. Pulling at a set depth, rather than running to the limit, protects the casing for retreading and keeps the tire out of the range where it is most vulnerable. Many fleets set a deeper pull point on steer tires than on trailer tires.
Write the numbers into the spec so the decision is not made under pressure on the day.
Step 4: Build the inspection routine
Who checks pressures, how often, and with what gauge. Who looks for damage, irregular wear and mismatched duals. Where the findings get written.
A short daily walk-around by the driver catches obvious problems. A scheduled, more thorough check by a technician catches the slow ones. Both matter. The tire pressure check article covers the pressure side in detail.
Irregular wear found at inspection often traces back to alignment. Heavy-duty truck alignment on a schedule, or whenever steer wear shows up, protects the tires you just specified.
Step 5: Plan for casings and failures
Two decisions that are easy to skip:
What happens to casings. Are they going to be retreaded, by whom, and which positions take retreads? Decide before the first casing comes off, or the default will be the scrap pile.
What happens at the roadside. Who authorizes work, which store a driver calls, and what tire goes on when the planned one is not available. Settling this in advance is what makes a roadside call quick rather than a negotiation.
Step 6: Record and review
Every tire event recorded: unit, position, date, mileage, reason for removal. Reviewed on a schedule, monthly for most fleets. The article on tire tracking and fleet reporting sets out which numbers to watch.
The review is where the program improves. A spec that keeps failing early gets changed. A unit that eats tires gets inspected. A position that wears irregularly gets an alignment check.
Common reasons programs stall
Most programs that fail do not fail on paper. They fail in the yard, for predictable reasons.
Nobody owns it. A program needs one named person responsible for keeping the spec current, chasing the records and running the review. Without an owner it drifts back to reactive buying within months.
The spec is too complicated. A spec with many exceptions is a spec nobody follows. Start with the fewest sizes and tire types that genuinely do the job, and add exceptions only when the records justify them.
Drivers are not told. The people most likely to make a tire decision at the roadside are drivers. If they do not know who to call, what is authorized and what to ask for, the program does not exist at the moment it matters. A one-page sheet in each cab solves most of this.
The review never happens. Records that nobody reads change nothing. Put the monthly review on the calendar and keep it short: what stood out, what changes, who does it.
It tries to fix everything at once. Begin with the problem costing the most, usually roadside failures or scrapped casings, and expand once that is under control.
Working with a supplier
A Purcell fleet account is built around the same structure: agreed specifications, scheduled work, consistent terms and records in one place. Bringing your program, even a rough first draft, to that conversation makes the setup faster and the result closer to what you actually need.
What to bring:
- The unit list with sizes and positions
- Where the vehicles are based and where they travel
- What is failing now
- How you want to be billed and who authorizes work
- What reporting you want