Standards

Editorial and accuracy standards

How regulatory claims on this site are sourced, checked and corrected — and what to do when you find something wrong.

Primary sources only

Every label format is implemented from the regulation itself — 21 CFR 101.9 for the US, Regulation (EU) No 1169/2011 for the EU, RDC 429/2020 for Brazil, and the equivalent instrument for each of the other markets — not from a competitor's output or a secondary summary.

Where a page states a threshold, a rounding rule or a required statement, it names the paragraph it comes from. If we cannot cite it, we do not assert it.

Clean-room implementation

No text, layout measurement or code is reproduced from another labelling product. Formats are built from the regulation text and the agency's own reference specimens. The repository carries ATTRIBUTION and CLEAN_ROOM_PROCESS files documenting that trail.

Automated verification

Claims that can be checked by machine are checked on every build rather than trusted. A verification script asserts plan limits, prices, format counts, route coverage and page counts against the real constants and the live site, and the build fails when a claim and the code disagree.

Rendering is diffed too: all 304 label variants are rendered on each build and compared against the previous output, so a change to one format cannot silently alter another.

Watching for rule changes

Regulations move, and they rarely announce themselves. A scheduled regulatory-watch job monitors the sources behind the formats we implement, so a changed threshold surfaces as a task rather than as a customer's rejected label.

Where a rule has a known future compliance date — Canada's front-of-pack deadline, for example — the affected pages say so explicitly instead of describing only today's requirement.

Corrections

When something is wrong, it is corrected at the source and the correction is dated in the repository's verified-facts record, which distinguishes what has been checked from what has not. Claims that were tested and found false are recorded as such rather than quietly deleted.

If you find an error in a format, a threshold or a citation, report it. Regulatory accuracy is the product; an unreported error costs somebody a print run.

What this site is not

NFL is software, not a regulatory consultancy, and nothing here is legal advice. The tool implements the rules as written and cites them so you can check the work — but responsibility for the label on your package remains yours, and for a novel or high-risk product a qualified regulatory professional is still the right call.

Found an error?

Regulatory detail changes and mistakes happen. Tell us and it gets fixed and dated.

Report an inaccuracy