General information, not medical or dietary advice. Protein floors and sodium ceilings should come from your own clinician or dietitian — especially with kidney disease, where protein guidance is individual and sometimes counter-intuitive. Full disclaimer.
Most people meet a nutrition target the hard way: eat first, add it up afterwards, feel bad, try harder tomorrow. That is a scoring system, not a plan, and it is why the same target gets missed in the same way every week.
A target is a planning constraint. If a week is designed to land inside it, you hit it by cooking what you already decided to cook — and the counting afterwards stops being a verdict and becomes a receipt.
The three behave completely differently and confusing them is why targets feel impossible. Protein is usually a floor — more is fine, less is the failure. Sodium is a ceiling — under is fine, over is the failure. Calories are a window, where both directions count as missing.
A floor is met by anchoring: pick the protein first and build the plate around it. A ceiling is met by budgeting: spend it deliberately across the day rather than discovering at dinner that breakfast took most of it.
Trying to raise a floor and hold a ceiling at the same time is where it gets genuinely hard, because the obvious high-protein convenience foods — deli meat, cheese, tinned fish, ready-marinated everything — are also the salty ones. That combination has to be planned; it will not happen by accident.
Chasing a target meal by meal makes every plate a small exam and produces a boring, anxious way of eating. Days vary, and a week has enough slack to absorb one heavy dinner if the days around it are built to.
Plan the week to land, then let individual meals be interesting. The exception is a hard clinical ceiling for a single day, such as a renal potassium limit — that one is a day-level rule, not a weekly average.
Plate Planner shows the totals per day and rolls them up across the week and the month, so you can see which days carry a problem rather than only that a problem exists.
A dashboard that counts every dish on the calendar is lying to you the moment you cook for more than yourself. A family lasagne is not your dinner — one portion of it is, and if you are cooking for four, three-quarters of that pan belongs to somebody else’s numbers.
This is why per-serving figures matter more than recipe totals, and why the number of people at the table has to be part of the calculation rather than an afterthought.
Plate Planner totals only the servings eaten by the people whose numbers are being shown, so cooking for a household does not inflate your own day.
Every dashboard has a scope, and reading one without knowing its scope is how people end up cheerfully wrong. A planner counts the meals in the plan — which is to say, what you intended to cook and, hopefully, did.
It does not know about the biscuits, the takeaway, or the second coffee. That is a genuine limit, and an honest tool should say so on the dashboard rather than implying it has the whole picture.
Plate Planner labels its dashboards as covering planned meals only, on purpose. It is a planner, not a food diary, and a number that pretends otherwise would be worse than no number.
When a week misses, the instinct is to start over. Almost always one or two dishes are carrying the entire miss — a single salty dinner can put a whole day over a 1,500 mg ceiling on its own.
Find the offender and replace only that. It is faster, it keeps the meals you were looking forward to, and it teaches you which dishes are expensive in the currency you happen to be spending.
Plate Planner’s Fix my week does exactly this: it names the specific meals responsible for a miss, shows what a swap would change, and waits for you to approve it.
A tidy dashboard built on invented figures is worse than no dashboard, because it converts a guess into confidence. This matters most for exactly the numbers people are given targets for — sodium, potassium, phosphorus — which are also the ones AI-written recipes state most confidently and least accurately.
Before relying on any trend line, trace one figure back to a food. Plate Planner grounds ingredients against a bundled USDA-derived dataset and marks what it verified, and it says plainly where it could not — see the guide on reading recipe nutrition below.
Plan weekly, check daily. A week has enough slack to absorb one heavy meal, so aiming at the week keeps eating pleasant. The exception is a hard clinical limit for a single day — a renal potassium cap, for instance — which has to be respected day by day rather than averaged.
Plan the protein first and choose unprocessed sources — fresh meat, fish, eggs, pulses, plain dairy — because the convenient high-protein foods are usually the salty ones. Then spend the sodium ceiling deliberately across the day instead of discovering at dinner that breakfast took most of it.
A planner counts what is in the plan, not what went in your mouth. That is fine as long as the tool says so. Plate Planner labels its dashboards as covering planned meals only, so the number is honest about its own scope rather than implying a complete food diary.
Because a recipe total is not a person’s intake. If you cook for four, one portion is yours and three belong to other people. Any dashboard that counts whole dishes will overstate your day badly — the figure has to be per serving, and it has to know who ate.