Skip to content
cccskills
FreePublished on GitHub

da-return-to-duty-workflow

Use this skill when a driver is returning to safety-sensitive duty after a positive test or refusal. Covers the SAP clearance, RTD test requirements (observed collection), and Clearinghouse update sequence.

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

Run score Not tested

See how to install

Files included (1)

  • SKILL.md3.3 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Return-To-Duty (RTD) Workflow

A driver who tested positive or refused cannot return to safety-sensitive work until completing the full RTD sequence under § 40.305 + § 382.605.

The sequence

  1. Removal from safety-sensitive functions (immediate, day-of test result)
  2. SAP evaluation completed (initial)
  3. Treatment/education completed per SAP plan
  4. SAP follow-up evaluation — SAP issues "may return" report
  5. Return-to-duty test — controlled substance test (alcohol if SAP prescribed)
    • Must be observed collection per § 40.67 (one of three triggers)
    • Result must be negative
  6. Driver returns to safety-sensitive work
  7. Follow-up testing schedule begins (per § 382.605)

Observed collection requirement

Per § 40.67, the RTD test (and follow-up tests) must be observed:

  • Same-gender observer
  • Observer watches the urine leave the body
  • Observer not the same person who collects the test (typically)

Clearinghouse updates

  • Day of positive test: report to Clearinghouse within 3 business days
  • Day of SAP report: update Clearinghouse with SAP info + follow-up schedule
  • Day of negative RTD test: update Clearinghouse — status moves from "prohibited" to "not prohibited"
  • Each follow-up test result: report within 3 business days

Common timeline

  • Removal to SAP eval: 1-2 weeks
  • SAP eval to treatment completion: 4-12 weeks (varies)
  • Treatment to follow-up SAP eval: 1-2 weeks
  • SAP report to RTD test: 1 week (often same day)
  • RTD test to return-to-duty: same day if negative
  • Total typical: 6-16 weeks

What carriers commonly get wrong

  • Returning driver before SAP follow-up evaluation (must be the second SAP visit, not the first)
  • Conducting RTD test as a regular pre-employment test (must be observed)
  • Forgetting to update Clearinghouse on the negative RTD test → driver shows "prohibited" forever
  • Allowing a driver to drive for personal/yard purposes before negative RTD test

CFR citations

  • 49 CFR § 40.305
  • 49 CFR § 40.67
  • 49 CFR § 382.605
  • 49 CFR § 382.701

How Compass surfaces this

This skill is searchable in the Compass Ask interface and runs against the carrier's actual fleet data when invoked from within the relevant tracker. It is read-only — no actions are taken 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=da-return-to-duty-workflow

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