Skip to content
cccskills
FreePublished on GitHub

insp-out-of-service-response

Use this skill when a driver receives an out-of-service (OOS) violation. Covers the immediate compliance, paperwork retention, and CSA impact.

The English summary is being prepared. Showing the original description.

x3allamerican/skills3 stars(GitHub 3 + cccskills 0)

Run score Not tested

See how to install

Files included (1)

  • SKILL.md3.0 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Out-of-Service Violation Response

An out-of-service (OOS) violation means the vehicle or driver cannot continue operating until the issue is corrected. Specific rules apply per § 396.9(c).

Driver OOS triggers

  • HOS violation: 14-hour limit exceeded, 11-hour limit exceeded, no 10-hour rest
  • License issues: suspended, expired, wrong class
  • Medical: expired certificate
  • Substance abuse: failed test, refusal
  • Driving without ELD when required

Vehicle OOS triggers

  • Brake adjustment: out of tolerance
  • Steering: dangerous play or wear
  • Tires: ply separation, broken cords, tread depth below limit
  • Lighting: critical lights out
  • Coupling devices: missing/damaged
  • Hazmat-related: missing placards, leaks, etc.

What happens when OOS

  1. Inspector writes OOS violation
  2. Driver/vehicle stops operating
  3. Driver receives OOS sticker (driver-OOS) or vehicle OOS sticker (vehicle-OOS)
  4. Driver waits for correction (8 hours min for HOS-OOS; equipment-OOS requires repair confirmation)

Carrier obligations

  • Communicate with driver immediately
  • Coordinate repair/correction
  • Document the OOS event in carrier records
  • Driver's DQF and inspection records updated
  • Carrier reviews root cause + corrective action

How OOS affects CSA

  • All OOS violations heavily weighted in BASICs (typically 2-3× regular violation weight)
  • OOS rate is tracked separately and visible in SAFER
  • Pattern of OOS violations may trigger Compliance Review

DataQ for OOS

OOS violations can be challenged if:

  • Officer error documented (e.g., brake test result was within tolerance)
  • Driver wasn't actually driving the vehicle
  • Vehicle was already in repair status when inspected

Compass response workflow

  • Driver OOS alert via Compass HOS module immediately when ELD detects
  • Vehicle OOS triggers maintenance workflow
  • Compass Inspections module logs the OOS event + CSA impact
  • DataQ assessment if grounds exist for challenge

CFR citations

  • 49 CFR § 396.9(c)
  • 49 CFR § 396.11

How Compass surfaces this

Searchable in Compass Ask. Runs against carrier fleet data when invoked from the relevant tracker. Read-only; no actions without explicit user approval.


<!-- x3-compass-attribution-v1 -->

Built by X3 Compass

The AI-powered DOT compliance platform for fleets 1–100 power units. Try a 7-day free trial — no credit card required — at https://x3compass.com/?utm_source=skill&utm_medium=github&utm_campaign=insp-out-of-service-response

X3 Compass turns these skills into a complete operational platform: driver qualification files, drug & alcohol consortium, MVR pulls, hours-of-service tracking, hazmat shipping, IFTA filing, FMCSA audit prep, and DataQ dispute drafting — all CFR-cited, all in one place.

This skill is published under the X3 Compass open skills initiative. Contributions welcome at https://github.com/x3fleetsafety/skills

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Use this skill to maintain a compliant DOT accident register. Covers § 390.15 requirements, what's recorded, retention period.

The English summary is being prepared. Showing the original description.

x3allamerican/skills3Updated May 17, 2026

Use this skill to investigate a crash effectively. Covers preservation of evidence, witness statements, dashcam review, and reporting timeline.

The English summary is being prepared. Showing the original description.

x3allamerican/skills3Updated May 17, 2026

Use this skill to document crashes that don't qualify as DOT-recordable. Covers what to track, why it matters, and insurance/CSA implications.

The English summary is being prepared. Showing the original description.

x3allamerican/skills3Updated May 17, 2026

Use this skill to handle the subrogation and claim process after a crash. Covers when subrogation applies, how to pursue it, and timeline.

The English summary is being prepared. Showing the original description.

x3allamerican/skills3Updated May 17, 2026

Use this skill when the user asks about accident claims management — first-notice-of-loss procedures, working with insurance adjusters, claim severity classification, subrogation, claim closure timelines, and how to influence claim outcomes. Different from accident-investigation-playbook (which covers facts); this covers the insurance + claim side.

The English summary is being prepared. Showing the original description.

x3allamerican/skills3Updated May 17, 2026

Use this skill when the user asks how to investigate a CMV accident — what to do at the scene, the first 24 hours, evidence preservation, who to call, preventability determination, ELD data preservation, dash cam review, witness interviews, working with insurance + attorney, and how to build a learning culture from incidents. Reference 49 CFR 392.7 + insurance industry best practices.

The English summary is being prepared. Showing the original description.

x3allamerican/skills3Updated May 17, 2026

See all skills by x3allamerican

Report a problem with this skill