Biennial MCS-150 update vs on-demand update
The 49 CFR §390.19T framework requires biennial MCS-150 updates every two years on a schedule keyed to the USDOT digits - the last digit sets the month under §390.19T(b)(2) and the next-to-last digit sets the year parity under §390.19T(b)(3) - and FMCSA registration guidance separately requires on-demand updates within 30 days of any change in carrier identifying information. Both are required; they do not substitute for each other. The biennial keeps the carrier's registration current as a baseline (vehicle counts, driver counts, mileage, business address); on-demand updates capture mid-cycle changes such as legal name, USDOT-holder address, or operating-classification changes (private to for-hire, intrastate to interstate). Missing a biennial update triggers USDOT deactivation under §390.19T(b)(4), which makes the carrier ineligible to operate until a fresh MCS-150 is on file and processed. Missing an on-demand update leaves the carrier record inaccurate and is enforceable through civil penalties under 49 U.S.C. §521.
Side-by-side comparison
| Dimension | Biennial Update | On-Demand Update |
|---|---|---|
| Trigger | Time-based (every 2 years) | Event-based (within 30 days of change) |
| Authority | §390.19T(b)(2)–(3) | FMCSA registration guidance |
| Schedule | Last digit of USDOT → month; next-to-last digit → odd/even year | 30 days from event date |
| Purpose | Confirm carrier still active | Reflect specific operational change |
| Form filed | MCS-150 (or B/C variant) | MCS-150 (or B/C variant) |
| Failure consequence | USDOT deactivation | Inaccurate carrier record |
Biennial update - the every-two-years anchor
The biennial update under §390.19T(b)(2)–(3) is the regular cadence that keeps the carrier's registration current as a baseline. The schedule is fixed: the deadline month is determined by the last digit of the USDOT (1=January … 0=October), and the year is determined by the next-to-last digit (odd or even calendar year). Carriers should track their biennial deadline because missing it is the most common cause of USDOT deactivation in the FMCSA system.
For carriers with no operational changes between biennial deadlines, the biennial filing is administratively simple - the carrier confirms existing data is still accurate, refreshes any mileage data, and submits. Most carriers can complete a biennial update in under 15 minutes through Motus (motus.dot.gov). SAFER reflects the updated record within 24-48 hours.
On-demand update - the event-driven trigger
On-demand updates required by FMCSA registration guidance must be filed within 30 days of any change in the carrier's legal name, principal place of business, ownership, operations classification, or any other significant change to the carrier registration data. The 30-day window starts on the effective date of the change, not the date the carrier "remembers" to update. Common triggers: business address change, legal-name change, ownership change (sale, merger, reorganization), operations-classification change (private to for-hire, non-hazmat to hazmat), or fleet vehicle count change of any significance.
For carriers with frequent operational changes, multiple on-demand updates may stack between biennial deadlines. Each event-triggered update is filed independently as a fresh MCS-150 through Motus. The biennial schedule is unaffected - even with multiple intervening on-demand updates, the next biennial filing is still due on its keyed deadline.
How they interact
Biennial and on-demand updates are complementary, not substitutive. The biennial provides the regular timeline anchor that prevents USDOT deactivation; the on-demand updates capture mid-cycle accuracy. Both run through the same MCS-150 form (or B/C variant); the difference is the trigger and the scope. A carrier can file an on-demand update one month before the biennial deadline and still has to file the biennial separately on schedule.
For carriers operating in multiple compliance regimes (UCR, IRP, IFTA, state DOT permits), the MCS-150 update typically triggers downstream notifications. Most state systems pull current carrier data from FMCSA SAFER, so an updated MCS-150 propagates automatically. For systems that don't auto-pull (some state-specific motor-carrier permits), the carrier may need separate notifications.
Frequently asked questions
Does an on-demand update reset the biennial cycle?
No. The biennial cycle is keyed to the last two digits of the USDOT and runs on a fixed every-two-years schedule regardless of intermediate updates. An on-demand update for an address change or fleet count change does not reset the biennial deadline.
What changes trigger an on-demand update?
Per FMCSA registration guidance: change in legal name, principal place of business, ownership, operations classification, or any other significant change to the carrier registration data. The 30-day window starts on the effective date of the change.
Can I skip the biennial if I just filed an on-demand?
No. The biennial schedule runs independent of on-demand updates. Even if the carrier filed an on-demand update for an address change one month before the biennial deadline, the biennial still has to be filed on schedule. The two trigger types do not substitute for each other.
Related comparisons
File biennial or on-demand MCS-150
Both update types use the same MCS-150 form. Track your biennial deadline and file on-demand updates within 30 days of any operational change.
File MCS-150