Use this skill to maintain a compliant DOT accident register. Covers § 390.15 requirements, what's recorded, retention period.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when the user asks about FCRA adverse action procedures — what to do when a background check (MVR, criminal, drug test) returns information that may lead to denying employment or terminating a CDL driver. Covers the 5-business-day pre-adverse-action notice, FCRA Summary of Rights, final adverse action notice, state-specific add-ons (CA, NY, etc.), and how to handle disputes. Cite 15 USC § 1681 (FCRA) and 49 CFR 391.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
When a consumer report (MVR, criminal background, drug test verified result, PSP, Clearinghouse) returns information that may cause an adverse action (refusal to hire, termination, suspension), federal law requires a specific 2-step notice + waiting period process.
If the action is based ON the consumer report (even partially), FCRA applies.
Send the driver:
Wait at least 5 business days before taking adverse action. (Some states require longer — see state additions below.)
This 5-day window gives the driver time to:
If you decide to proceed:
For each adverse action, retain:
Retention: at least 2 years (FCRA recommends 5). Treat as part of the driver's terminated employment file.
| State | Additional requirement |
|---|---|
| California (Investigative Consumer Reporting Agencies Act) | Detailed notices + driver's right to receive copies; specific format required |
| New York (Article 23-A) | Special procedures for criminal record-based adverse actions; consider rehabilitation |
| Massachusetts | "Ban the Box" — limits on when criminal records can be considered |
| Illinois (Job Opportunities for Qualified Applicants Act) | Restricts consideration of criminal history pre-offer |
| Washington | Sealed/expunged convictions can't be considered |
| Maryland | Disclosure requirements at offer stage |
| Connecticut | Time limits on consideration of criminal records |
| Many cities (Seattle, NYC, San Francisco, etc.) | Local "Fair Chance" / ban-the-box rules |
Always check your state + local rules. A federal-compliant adverse-action process can still violate state law.
A driver who reads the pre-adverse notice and disputes can:
You should pause adverse action pending dispute resolution if the dispute appears credible. Talk to your attorney if the dispute is substantive.
For drug test results specifically:
A verified positive is NOT subject to the standard FCRA adverse-action process — it's covered by DOT's separate D&A regulations. The driver is "prohibited" via Clearinghouse and cannot operate until SAP + RTD complete.
Day 0 - Checkr "consider" status received via vendor-result-webhook
Day 0 - send-compliance-notification fires with severity=warning
Day 1 - Safety manager reviews report in app.x3fleetsafety.com/background-checks.html
Day 1 - Decision: pre-adverse action notice sent (using adverseActionPrepEmail template)
Day 2-7 - Driver can dispute via Checkr's portal
Day 8 - If no dispute resolution OR confirmed adverse → Final adverse-action notice
Day 8+ - Driver removed from active fleet
X3's vendor-result-webhook flags report.completed events with status=consider as bg_check_consider event. The send-compliance-notification Edge Function fires the adverseActionPrepEmail template to the safety manager with the FCRA timeline. The notification_routing helper resolves this event to email (it's a 5-day workflow, not 1-day urgent).
The _shared/email_templates.ts adverseActionPrepEmail template includes:
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=adverse-action-prep
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
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Use this skill to maintain a compliant DOT accident register. Covers § 390.15 requirements, what's recorded, retention period.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill to investigate a crash effectively. Covers preservation of evidence, witness statements, dashcam review, and reporting timeline.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill to document crashes that don't qualify as DOT-recordable. Covers what to track, why it matters, and insurance/CSA implications.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill to handle the subrogation and claim process after a crash. Covers when subrogation applies, how to pursue it, and timeline.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.