Auth dot number update requirements
Skill x3fleetsafety/skills/skills/auth-dot-number-update-requirements
Open-source Agent Skills for DOT / FMCSA compliance. Drop in any AI coding agent (Claude Code, Cursor, Cowork) so it knows trucking regulations like a fleet safety pro.
npx -y skills add x3fleetsafety/skills --skill auth-dot-number-update-requirementsAssembled 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.
What its author says it does
Copied from the file, not written here
Use this skill to understand when to update your USDOT number registration (MCS-150). Covers triggers, frequency, and consequences of late updates.
SKILL.md
2.5 KB, as published. Nobody here has run it
DOT Number + MCS-150 Update Requirements
Per § 390.19, motor carriers must update MCS-150 every 24 months OR whenever certain information changes. Failure can result in revocation.
Required update triggers (any of these)
- Every 24 months (biennial update)
- Carrier name change
- Address change
- Number of power units changes
- Number of drivers changes
- Type of operation changes
- Operating authority changes
- Owner/officer changes
- Hazmat carrier changes
When to update
- Biennial: 24-month anniversary of last update
- Immediate: any of the trigger events
What's updated
- Carrier identification
- Operations data
- Vehicle counts
- Driver counts
- Hazmat status
- Insurance status
- Officer information
How to update
- USDOT/MC Online (preferred): fmcsa.dot.gov
- Form MCS-150 (PDF download + mail)
- Through carrier services representative
Consequences of failure
- Initial: warning letter
- Continued: registration deactivation
- Severe: revocation of operating authority
- Restart: must apply for reinstatement
Common errors
- Update missed by 1-3 months
- Update made but data incorrect
- Multiple operations not consolidated
- Officer changes not reported
Carrier oversight
- Compass tracks MCS-150 update dates
- Reminder 90 days before 24-month deadline
- Alert when triggering event occurs
- Audit-quality documentation
CFR citations
- 49 CFR § 390.19
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=auth-dot-number-update-requirements
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