Food Swaps and Substitutions: Flexibility Without Breaking the Plan
How to build swap lists by macro role with portion equivalents for protein, carbs and fat, how to present them, and where swapping should stop.
The plan says salmon. The shop is out of salmon, or it's expensive this week, or the client's partner won't eat fish. What happens next decides whether the plan survives the month: either the client knows that 150 g of cod or chicken does the same job, or they order a pizza because "the plan didn't work today".
Swaps are the difference between a plan that is rigid and a plan that is structured. This guide covers how to build swap lists that keep the macros intact, how to present them, and where swapping stops.
Why swaps matter more than variety
Coaches often try to prevent boredom with variety: 21 different meals in a week. It backfires: long shopping lists, more cooking, and a plan that's impossible to repeat. The client doesn't want 21 meals. They want to be able to eat what's in the fridge, go out on Saturday, and still be on the plan.
Swaps solve that. A plan with seven meals and three swap options per meal gives the client flexibility without changing the numbers, and without you rebuilding anything. It's one of the fixes in why clients don't follow meal plans that costs nothing.
Swap by role, not by food
The rule that makes swaps work: a food is swapped for another food that plays the same role in the meal. There are three roles.
Protein sources supply most of the meal's protein with little carbohydrate: meat, poultry, fish, seafood, eggs, Greek yogurt, cottage cheese, tofu, tempeh, whey.
Carb sources supply most of the carbohydrate: rice, pasta, potatoes, bread, oats, couscous, quinoa, fruit, legumes (which also bring protein, so they sit between the two groups).
Fat sources supply most of the fat: oils, butter, nuts and nut butters, seeds, avocado, cheese, fattier cuts of meat and fish.
A protein swaps for a protein, a carb for a carb, a fat for a fat. Chicken for salmon is a protein swap, but salmon carries more fat, so the portion or the fat elsewhere in the meal needs to move. Rice for potatoes is a carb swap. Olive oil for avocado is a fat swap. Chicken for pasta is not a swap at all.
Portion equivalents
Swaps only work if the portions are equivalent, and equivalence means matching the main macro, not the weight. Approximate equivalents, cooked weights unless stated:
Protein swaps (each about 30 g protein):
| Food | Portion |
|---|---|
| Chicken or turkey breast | 100 g |
| Lean beef or pork | 115 g |
| White fish (cod, haddock, tilapia) | 130 g |
| Salmon | 140 g (adds about 15 g fat) |
| Shrimp | 125 g |
| Canned tuna, drained | 120 g |
| Eggs | 4–5 large (adds about 20 g fat) |
| Greek yogurt, 0% | 300 g |
| Cottage cheese, low fat | 270 g |
| Firm tofu | 200 g |
| Tempeh | 160 g |
Carb swaps (each about 40 g carbs):
| Food | Portion |
|---|---|
| Rice, cooked | 140 g (about 50 g dry) |
| Pasta, cooked | 130 g (about 55 g dry) |
| Potato | 220 g |
| Sweet potato | 200 g |
| Bread | 2 medium slices |
| Oats, dry | 60 g |
| Quinoa, cooked | 190 g |
| Couscous, cooked | 170 g |
| Banana | 1 large plus a small apple |
Fat swaps (each about 10 g fat):
| Food | Portion |
|---|---|
| Olive oil or any oil | 10 g (2 tsp) |
| Butter | 12 g |
| Peanut or almond butter | 20 g (adds some protein and carbs) |
| Nuts | 15 g |
| Avocado | 65 g |
| Cheddar or similar cheese | 30 g (adds about 7 g protein) |
Give the client the table for their plan, or better, print the alternatives next to each meal.
Build the swaps into the plan
A few ways to present swaps so they get used:
- Inline options. "150 g chicken breast (or 190 g cod, or 110 g 5% beef)" next to the meal. The client doesn't need to understand macro roles; they just pick.
- A swap table at the end of the plan, grouped by role, with portions. Good for clients who like to understand the system.
- A "pick one from each column" meal. Protein column, carb column, vegetable column, fat column, with portions. One template gives dozens of meals. This is how meal plan templates stay flexible.
- Sauce and seasoning are always free. Say so explicitly; clients assume they aren't.
Keep the number of options to two or three per item. Twelve options is a nutrition database, not a plan.
When swapping goes wrong
Swaps fail in predictable ways:
- Swapping across roles. "I swapped the rice for extra chicken" leaves the client low on carbs and tired in training. The role rule fixes it.
- Swapping by weight. 100 g of salmon is not 100 g of cod. Portions must be matched by macro, which is what the tables above do.
- Swapping the vegetables for nothing. Vegetables are the one thing that can be swapped for any other vegetable at any portion; dropping them entirely leaves the client hungry and short on fiber.
- Hidden fat. Salmon, eggs, cheese, nut butter and fattier meats bring fat along with protein. Over a day of such swaps, fat can climb by 30 g. Note it in the table and keep the rest of the day's fat in check.
- Stacking swaps. Swapping the protein, the carb and the fat in the same meal, every meal, is a different plan. Suggest one swap per meal where possible.
Where swapping stops
Some things shouldn't be swapped without the coach's input:
- The protein target. The client can swap chicken for fish; they can't swap it for a smaller portion or for a carb.
- Whole meals for snacks. Replacing lunch with two protein bars changes the day's structure and usually the fiber and micronutrient content.
- Plan-level changes. Different meal count, different training-day structure, a new goal: these are conversations, not swaps.
Tell the client what's open and what's fixed. "Swap anything in the same group, keep the portions, ask me for anything else" is a clear rule.
Swaps in a fat-loss phase
Swaps get more important as calories go down, because the client has less margin for a food they don't like. Lean toward swaps that keep volume up (white fish, shrimp, egg whites, potatoes, oats) and watch the fat-heavy ones (salmon, nuts, cheese), which are easy to over-portion. The rest of the method is in how to build a weight loss meal plan.
Make it part of the recipe, not the explanation
The easiest way to handle swaps is to have recipes that already exist in two or three versions with the macros worked out: the chicken version, the fish version, the tofu version. Then swapping is picking a different recipe for the meal, and the day's totals update by themselves.
That's how SendFit handles it: recipes in the vault with macros calculated from the ingredients, so you add the version that fits and the day's protein, carbs and fat show against the targets as you go. The plan the client sees always matches what you built, with no mental arithmetic on either side.