Fixed nutrition replaces the dated week with a short list of named days — Training day, Rest day, High carb. Each one carries its own targets and its own menu, and they apply until you change them.
Fixed nutrition only appears for clients whose nutrition is set to Fixed delivery. Read about delivery modes
The client's Nutrition tab opens on a strip of days you define yourself. Add a day, name it, and give it targets. Most trainers use two, but a single Every day, or four seasonal variants, are equally valid.
Training day and Rest day are just the starting pair. High carb, Low carb, Cardio day, Comp day — the names are yours, and they're set per client.
Each day holds one set of macro targets and, optionally, one meal plan. The client picks the day, and both follow from that single choice.
Drag the tabs to reorder them. Mark one as the default: it's what applies when nothing has been picked for that date.
If a client has only one day type, it simply applies every day and no picker is ever shown — to you or to them.
Open a day and set its calories and macros. These are standing values, not a target for one date.
Calories
Protein (g)
Carbs (g)
Fat (g)
The same numbers apply every day of that type until you edit them. There's nothing to roll forward each week and nothing that quietly expires.
A meal plan built in the Fixed layout is one menu rather than a week of them. In the meal plan builder, set the layout to Fixed and the day selector disappears: you build a single day's meals, and that's what the client eats on every day of its type.
No Monday-to-Sunday strip, no weeks to fill. One set of meals with its own macro totals.
Each nutrition day holds at most one meal plan. Attaching a plan to a day moves it off whichever day it was on before.
A fixed meal plan stays in the client's library indefinitely. It carries no dates, so it never runs out and never needs assigning again.
For any given date the day type resolves in one order, and the same rule drives both the macro targets and which menu opens:
The client has exactly one day type — it applies, unconditionally.
Someone picked a day for that date, you or the client. That pick wins.
Otherwise the day you marked as the default applies.
The day type is never guessed from logged workouts. Clients eat breakfast before they train, so inferring it would change the day's targets retroactively halfway through the morning. Only an explicit pick and the default are ever used.
The client app shows the day’s calories and macros as rings at the top, then a row naming the day that applies — and under it the menu attached to that day.
Tapping that row lets them switch the day themselves — the honest answer to "I was supposed to rest but I trained". Their pick applies to that date only, and Back to default undoes it.
Under the days sits a chronological log of what the client actually ate, newest first.
Days with nothing logged still get a row. The gaps are the point — a missed week is obvious in a way a compliance percentage never is.
Change a row's day type retroactively when a client forgot to switch, so they aren't measured against the wrong target forever.
Click any row to open that date in the food diary, with every entry the client logged.
Nutrition that doesn't need rewriting every week
Set the days once, and let your client tell you which one it is.
Get Started Free