The swap table, explained: why any-for-any works

The swap table in the playbook lets you exchange any item in a row for any other item in the same row, with no arithmetic. That sounds too loose to be accurate, and it would be if the rows were organised by food type.

They aren't. Each row is built around a variable held roughly constant, which is the only reason any-for-any swapping produces a day that still hits your targets.

What each row holds constant

The protein row controls protein grams per portion. Chicken breast, white fish, prawns, lean beef, a tub of Greek yogurt, a scoop of whey — the portion sizes differ visibly, and that's the point. They're set so that each one delivers a similar amount of protein, with the leaner and fattier options portioned to keep calories in the same neighbourhood too.

The carbohydrate row controls carbohydrate and calories at a stated cooked weight. Rice, potato, oats, pasta and bread land in a similar band per portion, which is what lets you take Tuesday's rice and put Thursday's potato in its place without touching anything else.

The fat row controls calories, because fat is the most energy-dense thing you'll eat and small errors here are large errors overall. That's why the fat portions look absurdly different from each other — a tablespoon of olive oil against half an avocado against a small handful of nuts. Those are similar in energy and nothing else.

The vegetable row controls volume rather than calories. It's effectively unrestricted, because the calorie cost of two more handfuls of greens is trivial and the fullness they buy is not.

Notice that the controlled variable is different in every row. That's the part people miss when they try to build their own table: a row of foods grouped by what they are — everything that counts as meat, everything that counts as a grain — swaps badly, because nothing about it is held constant. A row grouped by what it delivers swaps cleanly.

The one rule

Swap within a row, never across rows. That's it, and everything else in this article is a footnote to it.

Crossing rows breaks the calculation that made the plan hit two targets at once. Trade a protein portion for a carbohydrate portion and your calories may land fine while your protein falls thirty grams short — and protein is the macronutrient the whole plan is built to protect in a deficit. The day looks compliant on one target and quietly isn't on the other.

“Any item for any item, inside the row. Across rows there is no such thing as a fair trade.”

Four footnotes that catch people out

None of these are complicated, and all four of them show up in the first week.

• Cooked weight for cooked, dry for dry. Rice roughly triples in weight when cooked, so 200g of one is nothing like 200g of the other
• Cooking fat is not free. Oil in the pan comes out of the fat row, and a freehand pour is usually two portions
• Sauces, dressings and marinades carry real calories — read them or count them as a fat portion
• Skin, breading and visible fat change a protein portion's calories a lot without changing its protein much
• Liquid calories aren't in the table at all, which is deliberate — they're the cheapest thing to remove from a deficit

How accurate is any of this

Not perfectly, and it doesn't need to be. Food composition genuinely varies — cut to cut, brand to brand, and by how something was cooked. Look the same item up twice in a reference database and you'll find a spread.

But the variation inside a well-built row is small relative to a day's total, and it's random rather than systematic — some swaps land slightly high, some slightly low, and across a week they largely cancel. The alternative is weighing and logging every item for thirty days, which is more accurate on paper and dramatically less accurate in practice, because most people stop doing it around day nine.

The swap table is the version you'll still be using on day twenty-eight. That's the trade it's making, and for a 30-day program it's the right one.

When to stop swapping and start weighing

One situation. If your seven-day average has been flat for four or more days while your compliance sits high, portion drift is the first thing to audit — and the cleanest way to audit it is to weigh everything for three days, compare against your portions, then go back to the table.

Almost always the answer is in the fat row or the carbohydrate portions, and almost always it's a rounding habit rather than a plan problem. Fix the portion, keep the swap table, and get on with the month.