Where the numbers in these calculators come from, and what happens when one turns out to be wrong.
Every calculator on this site runs on figures a restaurant chain has already published for its own menu. Nothing here is estimated from a photo of a plate or averaged from a third-party database. This page explains how that sourcing works and who is responsible for it. See the authors page for who does the writing and checking.
Each calculator's dataset is built from the nutrition PDFs and web pages a chain publishes for its own menu, the same disclosures most of these companies are required to make under the FDA's menu-labeling rule for chains with 20 or more locations. That means calories, protein, carbohydrates, fat and sodium get pulled item by item from a brand's own published figures, then entered once into the calculator so it can be recombined however you build an order. Full detail on the underlying rule is in the FDA's menu-labeling requirements.
Chains rotate their menus with the seasons, sometimes adding an item, sometimes changing a recipe enough to shift the nutrition numbers. This site rechecks each chain's calculator against the brand's current published values whenever a seasonal menu shift is likely, and immediately whenever a reader flags something that looks off, whichever comes first. A calculator that hasn't had a menu change in a while may simply not need an update yet.
If a total looks wrong, the fastest way to get it fixed is to name the exact item and chain through the contact page. That report gets checked against the brand's own current nutrition page, and if the figure has changed, the calculator's dataset gets updated, usually within a few days.
The calculators here do not average figures across locations, round numbers to something tidier, or borrow values from a nutrition app that isn't the chain itself. A dash on a results panel means that chain doesn't publish that particular field for that item, not that the true value is zero.