How Daymark checks carrier records

How a check works

Enter a USDOT number. Daymark retrieves FMCSA census registration, authority and authority history, insurance filings and BOC-3 process-agent records from public U.S. Department of Transportation datasets. It then searches census and BOC-3 records for direct matches to the carrier’s identifiers.

Every fact carries a source link, fetched-at and source-updated-at. The latter is the dataset publication time, not necessarily a carrier event date. Record dates appear when available. A source link can change as the publisher updates records; a response hash identifies the retrieved response rather than a permanently hosted snapshot.

What is compared each night

The nightly job reads published registration, authority, insurance and process-agent feed rows and matches their USDOT numbers against the working set. The watchlist compares those matches with your selected carriers and shows new matching raw rows since your last view. It does not infer a verified before-and-after change from each row. Matching records remain visible for seven days; feed gaps can occur. Matches expire cached profiles so later checks can retrieve updated facts. Blank fields never mean a filing was removed or a carrier lost authority. No email alerts are included in v1.

Coverage and limits

SMS (Safety Measurement System) publishes monthly with lag. Daymark v1 does not include SMS safety measures, safety ratings or out-of-service coverage. Insurance amounts are withheld pending unit reconciliation. Missing fields stay unknown. Sources can lag or fail, and a blank result does not establish a clean record. This is a partial check, not a guarantee of operating status or suitability.

How candidate relationships are found

Phones match after removing punctuation and an optional US country prefix, across phone and cell-phone fields. Officer names match after changing letters to uppercase and collapsing spaces. Addresses must have a street, city, state and ZIP and match the full physical address, including country. BOC-3 agents match on the listed company name. We do not check whether two people with the same name are the same person. We do not use approximate names, map coordinates, address validation or state company records.

Phones can be reassigned, addresses can be shared offices or homes, and officers can share names. A shared BOC-3 agent means a shared service provider, not an ownership link. Historical filings may remain in the source. A match does not prove that two carriers operated together or that their connection is current.

Common identifiers and search limits

Daymark suppresses an identifier used by more than 10 distinct carriers, counting the requested carrier. It also suppresses an identifier if the bounded search returns 101 rows, even when repeated historical records explain the count. These limits reduce noise; they are not risk thresholds. Common dispatchers, offices and process agents may therefore be missing from the relationship view. Suppression reasons and query evidence remain visible.

We search at most 12 distinct identifiers per carrier, starting with census phones, officers and address, then BOC-3 agents in source order. We search direct matches only and do not follow matches outward. The retained result can have at most 108 neighboring carriers. Unusual formatting, spelling, blank fields and incomplete source coverage can hide matches. No results never proves no relationships.

Dates, caches and capacity

Each relationship retains the field values and source evidence for both carriers, including publication and retrieval dates. Those dates may differ between sides. Census publishes daily with lag; BOC-3 coverage is incomplete and agent names are often blank. Profiles can stay cached for 24 hours, missing census results for one hour, and relationships for one hour. A new relationship search may combine a cached carrier profile with a newer query.

The working set holds up to 1,500 carriers. Relationship storage and search sizes are bounded. Source or capacity errors fail explicitly instead of returning a silently shortened success. Insurance filings are not a coverage determination, and historical authority actions are not current status. Confirm material decisions with the underlying records and the carrier.

Source dates and observed history

Source: FMCSA data via data.transportation.gov. Each profile section carries its own publication date and source link. Census, authority, insurance filings, authority history, insurance history, authority orders, out-of-service orders and rejected filings archive can run on different clocks. History lists recorded events; it cannot reconstruct a past profile. Identity changes are observations by Daymark on the date shown. Missing Motus records use census evidence and leave authority coverage unknown. Insurance filings are labeled primary, excess or ambiguous; amounts remain withheld while source units are unresolved. Unknown codes show “(unclassified)”. Shared vehicle evidence joins inspection units to inspections; it does not establish ownership.