Da return to duty workflow

Skill x3fleetsafety/skills/skills/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.From its SKILL.md

Install

npx -y skills add x3fleetsafety/skills --skill da-return-to-duty-workflow

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.3 KB, 748 tokens by cl100k_base, as published. Nobody here has run it

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

Removal from safety-sensitive functions (immediate, day-of test result)
SAP evaluation completed (initial)
Treatment/education completed per SAP plan
SAP follow-up evaluation — SAP issues "may return" report
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
Driver returns to safety-sensitive work
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.

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

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.