Broker guideMCS-150, publication and observation dates explained
Avoid confusing the carrier filing date with the age of your lookup.
Updated 2026-09-13 · CarrierTrail product workflow
Keep the clocks separate
The MCS-150 date is a reported filing field. Publication describes the underlying dataset version. Import and observation dates describe when CarrierTrail obtained or compared data. The time you opened a page is a fourth event and does not make the underlying information newer.
Use dates to frame the next check
When a packet contains a recent change, compare its date with the source publication before treating a mismatch as a contradiction. If the public snapshot predates the claim, record that limitation and check the appropriate official source. Do not infer a filing violation from an older date alone.
Illustrative example
A contact change is described as occurring Tuesday but the available source was published Monday. Wednesday’s page view still displays Monday’s data. Your note should explain the timing gap and the follow-up performed, rather than saying the change did not occur.
Date comparison note
Carrier filing date: __. Source published: __. Observed by CarrierTrail: __. Claimed change date: __. Review date: __. Timing gap and verification step: __.
Worked review example
Illustrative scenario. A profile shows an older carrier-reported filing date and a recent census publication date. Another reviewer assumes the recent publication means the company updated every field recently. These dates measure different events and should remain separate in the evidence record.
A practical review sequence
Identify
Record the MCS-150 date as the carrier-reported filing date shown in the census. Record the census publication date in a separate field.
Interpret
Check whether the question concerns when the carrier filed information, when the source was published or when your team reviewed it.
Follow up
Where timing matters to the shipment decision, consult the relevant official record and document any more recent confirmation obtained separately.
What to put in the review record
Use a timeline with carrier filing date, source publication, CarrierTrail observation and reviewer check time. Add a claimed change date only when you can identify who supplied that claim.
Before closing this review
An older date is a reason to understand the record's age. It does not, by itself, explain which fields changed or prove that every current operational detail is out of date.
Why retain both the filing date and the publication date?
They let another reviewer understand two different timelines. The filing date shown on the record relates to carrier-reported information, while the source publication identifies the dataset version being used. Your review date adds a third event. If you retain only the newest date, older information can look newly reported even when it was simply included in a later dataset. Keeping the dates separate also makes it easier to explain why a subsequent page may show a newer source without a changed field.
Can two reviews use the same source version?
Yes. Record each review's date and purpose while preserving the common publication date. A repeated review may add external confirmation or a new decision without changing the underlying public snapshot.
Use these steps alongside your organization’s verification process. CarrierTrail presents public records and saves team decisions; it does not certify carriers or insurance coverage.
Read the data methodology → · All broker guides →