If a published figure, date, source label, calculation, or explanation is wrong, we correct the page and document a material change here. This log starts on September 27, 2026. It does not claim to reconstruct every edit made before that date, and a proposed fix is never described as published until it is live.
Public record
Corrections since this log began
September 27, 2026 · Publication status
Corridor table inclusion was described as search indexing
Earlier statement
The publication playbook at /playbook called the 368 state pairs passing the data gate “indexed corridors” and referred to “other indexed corridors.”
Corrected statement
Those 368 pairs appear in the ranked data table. Individual corridor pages are currently noindex,follow and are not listed in the sitemap; none is being presented as an indexed search page.
Primary evidence and release
The published sitemap excludes corridor detail URLs, and the California–Texas corridor page at /routes/california-to-texas carries a noindex,follow directive. The wording was corrected on the live playbook on September 27, 2026.
How to report an error
Write to privacy@yardpermit.com with the page address, the exact number or sentence, and the source you believe contradicts it. For a Census flow, include the origin, destination, dataset year, and table cell if you can. For an FMCSA company record, include its USDOT number. Do not send a moving estimate, phone number, or other private paperwork unless it is necessary to explain the issue. The contact page explains what the desk can and cannot change.
What we check before changing a page
The DueRiva compares a reported Census number with the published state-to-state T13 source and the version ingested by YardPermit. We check its year, geographic direction, estimate, and 90% margin of error separately. A change in survey vintage is a data update, not evidence that the earlier vintage was false. A derived rank, interval, or net direction is recalculated from those sourced inputs and checked against the documented migration method.
FMCSA records can change after a lookup. We compare a report with the current agency record and keep the dataset update date separate from the time a visitor requested it. We cannot edit the agency’s file or certify a company as safe. If the official record itself is wrong, the carrier must correct it with FMCSA; our page must continue to identify the agency as the source. We also check whether a wording correction changes the meaning of a limitation, such as treating a count of people as a count of shipments or a straight-line distance as driving miles.
How changes are published
We correct the affected page first, verify its rendered figure and source link, then add a dated log entry for a material factual correction. Minor spelling and layout edits do not receive entries unless they altered meaning. If a calculation cannot be verified, we remove or clearly withhold the claim while investigating. The methodology explains the current formulas and data limits; the about page identifies who publishes the site.