Taking a forklift out of service is the easy half. Somebody finds a fault, hangs a red tag, and walks away. What happens after that is where most facilities lose control, because the return to service is nobody's defined job.
The result is familiar. A unit sits red-tagged for three weeks because the work order was never raised. Or it is back in the aisle by lunchtime because a supervisor needed a truck and decided the fault was minor.
What the standard requires
1910.178(p)(1) is the governing text. If at any time a powered industrial truck is found to be in need of repair, defective, or in any way unsafe, it must be taken out of service until it has been restored to safe operating condition. And 1910.178(q)(7) requires that defects, when found, be immediately reported and corrected.
Two words carry weight. Restored, which means the condition is actually corrected, not tolerated. And authorized, because the standard puts repairs in the hands of authorized personnel, not whoever was driving.
Two conditions get named specifically. A truck emitting hazardous sparks or flames from the exhaust comes out immediately and stays out until the cause is eliminated. A truck with any part running above its normal operating temperature to the point of creating a hazard comes out too. Neither is a judgement call.
Where the process breaks
No work order. The tag is the whole action. Nothing enters a maintenance queue, so nothing is scheduled and nobody owns it.
Pressure removal. Peak season, a unit down, a supervisor under pressure. The tag comes off without a repair. Because a hang tag has no name and no lock, nothing records that it happened.
Repair without verification. A technician fixes something and the truck goes back. Nobody confirms the original reported fault is the fault that was fixed, or that the unit passes a full check now.
No trail. The tag flips back to green and the red is gone. The fault, the wait, and the repair leave no trace, so the same fault next month looks like a first occurrence.
A process that holds
- Fault found and recorded. Whoever finds it, whenever they find it. Not only during the pre-shift check, since 1910.178(p)(1) applies at any time. Record the specific condition, with a photo where there is something to see.
- Unit goes red. Out of service. Tag on the truck, status changed in the system so it is visible to anyone looking at the fleet, not only to somebody standing next to it.
- Work order raised automatically. The fault record becomes the work order. If raising it is a separate manual step, it will be skipped.
- Repair by authorized personnel. With lockout/tagout applied under 1910.147 if the technician is servicing the unit. That is a separate device from the red tag, applied and removed by the technician.
- Verification. Somebody other than the person who did the repair confirms the fault is corrected and the unit passes a full inspection. Not a glance.
- Named return to service. A specific authorized person clears it, and that clearance is logged with their name and the time. The red tag comes off last.
Measure the middle
The interesting number is the time between step two and step six, per unit and per fault type.
Long durations usually mean parts availability or a maintenance backlog, both fixable once visible. Suspiciously short ones mean units are going back without real repairs. A fault that recurs on the same unit means the repair is treating a symptom.
None of that is visible when the record is a tag that gets flipped. It requires the red state to be a logged event with a beginning and an end.
Escalation for units that sit
A red tag with no repair after seventy-two hours should reach somebody more senior automatically. Not because the standard says so, but because a truck sitting broken for a month is a truck somebody will eventually put back in service without fixing.
The part that protects everybody
The single most valuable element is that the return to service carries a name. When clearing a truck is a logged decision attached to a person, the informal removal of a red tag stops happening. Not because anyone is punished for it, but because it is no longer anonymous.
That is also the answer if an incident later involves a unit that had been red-tagged: you can show the fault, the repair, the verification, and who authorized the return, with times attached to each.
Related reading
- What the green tag and red tag convention leaves out
- Red tag and lockout/tagout, and how they stack
- Putting a name and a time on every equipment handover
- The pre-shift examination that finds most faults
Out of service is easy. Back in service is the part that needs a name on it. TagRite holds the red state against the unit, raises the fault from the failed checkpoint, and logs who cleared it, all from a tap on the zip-tie NFC tag on the truck. Free onboarding covers setting return-to-service authority and escalation timers.