How we check every recipe
August 1, 2026 · 5 min read
A wrong quantity in a scalable table doesn't stay wrong once. Scale it to feed six and the error scales with it; toggle to grams and it carries into the metric column too. A step grouped in the wrong stage sends you reaching for an ingredient before it belongs in the pan. That's the risk a table format takes on that a plain list doesn't, so we check every one before it goes live.
The table is generated from the recipe. What earns your trust isn't that it's generated — it's what happens after: an independent pass that re-derives the numbers and confirms the groupings against the written steps. Accuracy is the gate the format has to clear, not a courtesy we add when there's time.
The quantities get re-derived
Every ingredient in the table becomes one row with a structured amount, unit, and metric-gram weight. We don't eyeball those against the recipe card. Each value is re-derived from the source recipe and matched back to it: the amount, the unit, and the gram equivalent.
The gram weights get the most scrutiny, because a cup of chopped spinach and a cup of shredded cheese weigh nothing alike. A grams figure that was merely plausible is a grams figure that was never actually checked, so each one is confirmed against the ingredient it describes, not against a generic density.
The cooking stages get checked against the steps
A table groups ingredients by the stage that first uses them, then reads left to right as the dish comes together. That grouping has to match the written method exactly. If the recipe browns the aromatics before the liquid goes in, the table has to show that order too.
So the stage columns are read back against the numbered steps, one at a time. An ingredient sitting in the wrong column, or two stages merged out of sequence, gets caught here. A parallel track like a sauce made alongside the main pan stays its own column, the way it runs in the real kitchen.
The scaled math gets confirmed
The whole point of the table is that you can scale it, so the scaled amounts get tested, not assumed. We confirm the math at half and at double: the quantities recompute cleanly, the serving count moves with them, and nothing produces a nonsense fraction like a third of an egg.
Items that can't scale stay fixed. A pinch of salt is a pinch at every serving count, and the table marks it as unscalable rather than inventing a decimal for it. Checking the extremes is what proves the middle holds.
An automated gate blocks a broken table
Human review catches the meaning; an automated check catches the structure. Before any recipe publishes, that check runs against the table and blocks it if the rows fall out of range, if two stages claim the same ingredient, or if a field is malformed.
The automated gate can't judge whether a gram weight is right or a stage is grouped sensibly — that's the verification pass above. What it does is refuse to ship a table that's structurally broken, so a formatting fault can't slip through on a tired afternoon. Two independent checks, one for the numbers and one for the shape.
| What we verify | Why it matters |
|---|---|
| Amounts, units, and metric grams | A wrong quantity scales into every serving and both unit systems |
| Stage grouping vs. the written steps | A mis-ordered stage tells you to combine things too early |
| Scaled math at ½× and 2× | Scaling is the feature; broken fractions defeat it |
| Structural validity (automated) | A malformed table can't reach a reader in the first place |
Why this is a gate, not an afterthought
A recipe format that's usually right isn't a format you can cook from without second-guessing. The value of reading a dish as a table is that you stop holding the ingredient list in your head, and that only works if the table is right on the dish in front of you, every time. One bad quantity teaches a reader to distrust all of them.
That's why the check comes before publishing, not after a complaint. The same standard runs behind Copper Keto Companion and Nordic Diet Companion: cook from the table, then tell the app what you plated and it works out the macros on your real portion. You can see the format itself in a recipe you can read at a glance, and try a verified one on keto chicken piccata.
FAQ
Are the recipe quantities accurate? Every quantity in the table is re-derived from the source recipe and matched back to it — the amount, the unit, and the metric-gram weight. We confirm the grams against the specific ingredient rather than a generic density, so a cup of greens and a cup of cheese carry their real weights.
What happens if a table has a structural fault? An automated check runs before the recipe publishes and blocks any table whose rows fall out of range, whose stages overlap, or whose fields are malformed. A structurally broken table can't reach a reader.
Do you check the scaled amounts too? Yes. We confirm the math at half and double servings, so the quantities recompute cleanly and unscalable items like a pinch of salt stay fixed instead of turning into an odd fraction.
Can a step end up in the wrong order? The stage columns are read back against the numbered steps one at a time, so an ingredient in the wrong stage or two stages merged out of sequence gets caught before publishing.
Where can I see the format? Start with a recipe you can read at a glance, then cook from a live one like keto chicken piccata. The format is live across Copper Keto and Nordic.