# Known limitations (release candidate)
1. Insurance filings are reported filing evidence as of the stated source date, not verified coverage, adequacy or claims-paying ability. Scheduled cancellations are not visible in bulk; absence of a cancellation date means unknown.
2. Legacy authority and insurance tables were last refreshed by FMCSA on 2026-05-14. For dockets without a Motus record this edition can be five months out of date; an authority reinstated or suspended since then is invisible in bulk (observed example in validation: one reinstated authority).
3. Motus amounts are stored in dollars even though FMCSA's dictionary says thousands; legacy amounts are in thousands. This edition publishes dollars for both. The legacy table stores 0 for cargo, surety, trust fund and some BI&PD rows; those amounts are published blank with `amount_note = LEGACY_ZERO_NOT_REPORTED`.
4. Census self-reported fields (fleet, drivers, mileage, addresses, phones) are as registered by the carrier on the MCS-150 and may be stale (`mcs150_date`, `mcs150_age_days`).
5. Entity class is blank for most carriers; N1 withholds street, ZIP and phone only where the source says INDIVIDUAL. Unflagged individuals' details appear as in the public source.
6. A portal-versus-bulk validation sample found disagreements in a small number of dockets; the ones that could be explained were frozen-legacy age (item 2) and Motus source-table disagreement (item 12). Details and denominators: QUALITY_REPORT.md.
7. Crash and inspection aggregates: inspection window starts where the FMCSA inspection file starts; crash records are per vehicle report (a multi-vehicle crash can contribute several records to one carrier); crashes with no `dot_number` are unattributed.
8. Not included: email, fax, cell, officers, mailing address, BOC-3 agents, DUNS, policy numbers, SMS percentiles, per-incident and per-inspection detail, driver data.
9. This is a one-time dated edition. No updates, subscription or live feed are promised.
10. Recorded dates are published as filed. Some FMCSA records carry implausible years (for example far-future dates); they are NOT corrected. `data/DATE_ANOMALIES.csv` lists each one with identifiers, column, source table, source as-of date and an uncertainty flag. Where a carrier-level `insurance_latest_effective_date` inherits such a date it is flagged with the verify_live reason `IMPLAUSIBLE_RECORDED_INSURANCE_DATE` and must not be read as confirmed current coverage. Future policy dates inside the plausibility horizon are legitimate as-filed evidence.
11. Source rows that are exact duplicates in every column (blank-docket Motus authority rows) are published once; the count is in `docs/QUALITY_REPORT.md`. Distinct rows are never merged.
12. Two official Motus tables can disagree about an authority's status. This edition publishes the Motus Carrier-table status and does not overwrite it with the latest row of the Motus authority-history table. The two differ for 5,401 of 160,566 checked Motus authority rows (carriers flagged: 5,327), and the latest history date is a tie between conflicting statuses for 1,329 rows (carriers flagged: 1,199); flags: `MOTUS_STATUS_DISAGREES_WITH_LATEST_HISTORY`, `MOTUS_HISTORY_LATEST_DATE_TIE`. A flag means two official sources disagree and the status should be verified live; it does not show which source is right. In a one-time check against the official MOTUS portal of 67 observed dockets taken from the disagreement set (up to 10 listed examples per status pair, not a random sample), the portal agreed with the Carrier-table status for 60, with the history status for 6 and with neither for 1; with that denominator and selection the check does not support a population estimate.
13. E-mail-address substrings embedded in free-text fields of the source are replaced by `[EMAIL REMOVED]`; the surrounding text is unchanged. Counts are in `docs/QUALITY_REPORT.md`.