Corrections
Send a correction to [email protected]. There is no form on this page, because this site accepts no submissions and stores nothing you type into it.
If a number on this site is wrong, we want to know which number and why. This page says exactly what to send so that a report can be acted on without a round trip, what happens to it afterwards, and what we will not do with it. There is no form here on purpose: the site has no write operations at all, and a report is more useful in your own words than in our fields.
What to include
The page URL, or the page name if you copied it out of a PDF. If the error is in a class value or a density band, the subprovision number identifies it faster than a description does.
The value you expected, and where it comes from. A link to the primary source is the strongest form of this; a screenshot of a tariff page is workable; "this looks wrong" is not enough to act on but is still worth sending.
If the error is arithmetic rather than factual, the inputs you used are enough for us to reproduce it exactly: length, width, height, and weight, with the units you selected.
What happens to a report
Reports about a class value or a density band go to the front of the queue, because one wrong band makes every page that uses it wrong at once. Those are checked against the primary source before anything else is touched.
If the report is correct, the data file changes, the version identifier moves, and a new entry appears on the changelog page. Corrections are not applied silently: the record of what changed is part of the fix.
If the report is not correct, the reply is the source and the arithmetic rather than a disagreement. You should be able to check the conclusion the same way we did.
What we will not do
We will not change a value to match a carrier quote. A rate is not a class, and a carrier's tariff is not the scale. If a carrier is classifying your shipment differently, the useful question is which of the three non-density characteristics applies, not what the class should be.
We will not remove a changelog entry because it is unflattering. The point of keeping one is that it cannot be quietly rewritten.
We will not ask you for an account, for an email address beyond the one you write from, or for anything else that turns a correction into a lead.
Frequently asked
Is there a form?
No. The site has no write operations and no database, so there is nothing to submit to. A plain email to [email protected] is the whole mechanism.
How long does a reply take?
A report about a class value or a density band is checked against the primary source before other work, and we aim to answer everything else within ten business days. If that window has passed, send it again — a message that went astray is more likely than a deliberate silence.
Do you publish who reported an error?
No. Reports are read and acted on, but nothing identifying a reporter is published. If a correction is worth describing, we describe the error rather than the person who found it.
Data source verified:
Primary source: NMFTA Disposition Bulletin 1371 — density and class breaks for the 13-subprovision structure
Archived copy: snapshot 0, snapshot 1