Glossary termELD Compliance
Out-of-Service Order
A directive issued by a roadside inspector or enforcement officer that prohibits a commercial vehicle or driver from operating until specific safety violations are corrected, often triggered by critical HOS violations, equipment defects, or driver condition.
Compare eld compliance platforms on verified pricing and deployment detail before you shortlist: every eld compliance platform we have reviewed.
Driver vs. vehicle out-of-service orders
Common OOS triggers by category
| Category | Common OOS Trigger | CFR Citation |
|---|---|---|
| HOS, Driver | Driving beyond 11-hour or 14-hour limit | 395.3(a)(2), 395.3(a)(3)(i) |
| HOS, Driver | Falsified log or no record of duty status when ELD is not exempt | 395.8(a), 395.8(e)(1) |
| HOS, Driver | 60/70-hour weekly limit exceeded | 395.3(b)(1), 395.3(b)(2) |
| Brakes, Vehicle | Brake adjustment out of spec (s-cam, air disc) | 393.51, 393.52 |
| Tires, Vehicle | Tread depth below 2/32 inch on steering axle | 393.75(a)(1) |
| Lights, Vehicle | Inoperable required lamp (brake lamp, head lamp) | 393.9 |
| Steering, Vehicle | Steering wheel lash exceeds specification | 393.209 |
| Driver condition | Driver impaired, ill, or fatigued to a degree of being a hazard | 392.3 |
| CDL/Medical | No valid CDL or expired medical certificate | 391.11, 391.41 |
The North American Standard out-of-service criteria
Roadside inspectors across the U.S., Canada, and Mexico use the Commercial Vehicle Safety Alliance (CVSA) North American Standard Out-of-Service Criteria (OOSC) as the operative standard for declaring vehicles and drivers out of service. The OOSC is updated annually and identifies specific defect thresholds, brake adjustment limits, tire condition minimums, lighting requirements, that trigger immediate OOS declarations. The OOSC is not the same as 49 CFR Part 393 (vehicle equipment standards). Part 393 sets the compliance standard; the OOSC sets the inspection threshold for immediate prohibition. A vehicle can have a defect that violates Part 393 without meeting the OOSC threshold for an OOS declaration, though both situations generate inspection violations.
When a driver OOS cascades
Why a driver OOS order costs far more than the violation
The citation is rarely the expensive part of an out-of-service order. A driver placed out of service on an hours-of-service violation cannot move the vehicle until enough off-duty time has accumulated, which on a 10-hour reset strands the load for most of a shift. The carrier then absorbs a chain of costs that the violation itself never names: a relief driver’s wages and deadhead miles to reach the inspection site, the late-delivery remedy in the customer contract, the administrative cost of processing the CSA violation, and the effect on the carrier’s Safety Measurement System percentile for the next 24 months. Price those five lines against your own contracts and wage rates and the real exposure becomes clear. The root cause is usually dispatch: a stop added mid-shift without recalculating the driver’s remaining drive-time budget. Recalculating that budget every time a route changes is the control that prevents the whole chain.
After an OOS order
Once an OOS order is issued, the driver must cease operation immediately and cannot resume until the condition is corrected. For HOS-related driver OOS orders, this means waiting until sufficient off-duty time has accumulated to bring the driver back into compliance, typically 10 consecutive hours. For vehicle OOS orders, the carrier must arrange repair either on-site or at a facility authorized by the officer to receive the disabled vehicle. Once corrections are made, the driver or carrier must have the OOS order lifted by an authorized officer before operation resumes. Operating in violation of an OOS order is treated far more seriously than an ordinary paperwork violation, and it carries penalties well above the underlying defect or hours-of-service citation. The governing amounts are in the FMCSA civil penalty schedule at 49 CFR Part 386, Appendix B, which is revised for inflation annually; check the current table rather than a circulating figure.
- Implement a pre-trip DVIR process that specifically checks the most common vehicle OOS triggers: brake adjustment, tire tread, and operational lighting
- Set ELD alerts at 10 hours and 10.5 hours of driving to give dispatch time to make re-routing decisions before the 11-hour limit is reached
- Maintain a list of certified repair facilities along your primary corridors so dispatch can direct vehicle OOS situations efficiently instead of scrambling for options
- Train drivers that operating after an OOS order is a criminal violation, drivers who believe a vehicle OOS order was incorrectly issued should call their safety manager, not drive away
- Track your fleet's OOS rate (OOS orders divided by total inspections) monthly, a vehicle OOS rate above 20% or a driver OOS rate above 5% warrants immediate review of maintenance and HOS compliance programs
- Review every OOS violation within 48 hours to determine root cause. Most OOS events are preventable and the fix is usually a process gap, not a single driver error
Terms like this one decide what a vendor is really quoting for, so it is worth checking the fleet software profiles that document how each platform handles it, and modelling the cost with a fleet cost calculator before a vendor call.
Platforms to check against Out-of-Service Order
These are eight of the 28 products we have reviewed in ELD Compliance, ordered by how closely each one’s published research covers Out-of-Service Order. Being in that category is what puts a product on this list; the order is relevance to this term, not a score against each other.
Best fit: Owner-operators and small carriers
PriceQuote onlyNo published pricePer truck subscription plus upfront hardwareBest fit: DOT-regulated US fleets, compliance first
Published price$14.99 per vehicle/mo, DC contractPer vehicle per month, quote onlyBest fit: 10 to 60 light vehicles, tracking first
Published price$25 per vehicle/mo, publishedPer vehicle, three published tiers · Minimum term: Four years by default on a silent orderBest fit: Maintenance-first fleets, 5 to several hundred
PriceQuote onlyNo published pricePer vehicle per month, unlimited users · Minimum term: Annual on Professional and PremiumBest fit: Canadian and cross-border fleets needing native ELD
PriceQuote onlyNo published pricePer vehicle and per asset, five packages · Minimum term: 36 months where the order form is blankBest fit: School bus and government fleets
Published price$14.70 per bus/mo, district contractPer vehicle per month, modular, quote only · Minimum term: Three years by defaultBest fit: 5 to 50 vehicles, tracking only
Published price$13.95 per vehicle per monthPer vehicle, month to month, published · Minimum term: None, 30 days' notice either wayBest fit: Owner-operators, one to three trucks
Published price$249.99 one-time, no subscriptionHardware purchase, part 010-01876-00 · Minimum term: None, there is no subscription
Out-of-Service Order FAQ
Quick answers to the questions buyers usually ask once the category, software, or rollout details start getting more specific.
Yes. Every roadside inspection, including those resulting in OOS orders, is recorded in the FMCSA inspection database and displayed on the carrier's profile in the SAFER system and the SMS. OOS violations carry higher severity weights in the CSA calculation than non-OOS violations of the same type. Inspections with no violations are also recorded and contribute positively to the carrier's SMS percentile calculation by increasing the denominator of inspections without adding violation points.
Yes, through FMCSA's DataQ system (dataqs.fmcsa.dot.gov). Carriers and drivers can submit challenges to inspection data they believe is inaccurate within 2 years of the inspection date. The reviewing agency is typically the state that conducted the inspection. DataQ challenges do not suspend the CSA impact of the violation during the review period, but successful challenges result in the violation being modified or removed from the SMS retroactively.