A macro diet for beginners comes down to five steps: get three numbers, measure for two weeks, reach protein first, accept that logging is approximate, and adjust from data rather than from feel. "Counting macros" means tracking grams of protein, fat and carbohydrate each day; the calorie total is implied by the three.

This is a method guide. It describes a procedure and what the calculator sets; it is not a meal plan and does not tell you what to eat.

Get three numbers first

Everything starts from a calorie target, and the three macro targets are derived from it in a fixed order. The macro calculator runs the sequence from a handful of inputs:

InputWhat it decidesExample (80 kg, 178 cm, 32, male, trains 4–6×/week, moderate daily movement)
Sex, age, height, weightBMR (Mifflin-St Jeor)10 × 80 + 6.25 × 178 − 5 × 32 + 5 = 1,757.5 kcal
Training frequency + daily movementactivity multiplier1.55 + 0 → TDEE 2,724 kcal
Goal and ratecalorie targetlose, moderate (0.5% of body weight a week = 0.4 kg, × 7,700 ÷ 7 = 440 kcal) → 2,284 kcal
Protein tierprotein gramsmoderate on a losing goal: 80 × 1.8 = 144 g (576 kcal)
Diet stylefat share of remainderbalanced: (2,284 − 576) × 0.35 ÷ 9 = 66 g (594 kcal)
carbohydrate remainder(2,284 − 576 − 594) ÷ 4 = 279 g

Write the three gram numbers down. They are the whole diet: 144 g protein, 66 g fat, 279 g carbohydrate for this example. Nothing else in this article changes them until step five.

BalancedP 150 gF 54 gC 229 gLow fatP 150 gF 45 gC 249 gfloor 3145 gLow carbP 150 gF 78 gC 175 gKetoP 150 gF 142 gC 30 gProteinFatCarbsBars are proportional to calories (4 · 9 · 4 kcal/g); labels are grams.
Fig. The four diet styles at 2,000 kcal for a 75 kg example with protein held at 150 g (2 g/kg). Fat takes a fixed share of the calories left after protein — 35% balanced, 20% low fat, 50% low carb — and carbohydrate fills the rest; keto fixes carbs at 30 g and lets fat balance. The fat floor (the higher of 0.6 g/kg and 20% of calories, here 45 g) lifts the low-fat split. Computed from the algorithm's constants; the split describes what the formula sets, not what anyone should eat.

Weigh, don't guess, for two weeks

The first two weeks are a measurement period. Two things are measured.

Food. Use a kitchen scale for anything that is not pre-portioned, and log the grams. Estimated portions are the largest source of error in a food log — a "tablespoon" of oil or a "medium" potato can be half or double the database entry — and the error is not consistent, so it cannot be priced in later. Log everything above roughly 50 kcal; a splash of milk in coffee matters less than being consistent about the things that matter.

Body weight. Weigh in most mornings under the same conditions. Single weigh-ins move by a kilogram or more with water and food in transit; only the trend across many weigh-ins says anything about the calorie target. Two weeks is the minimum for a trend to appear through the noise.

In plain terms: for fourteen days the job is to produce good data, not to react to it.

Hit protein first

Of the three targets, protein is the one to reach every day. The reasons are practical. It is set from body weight, so it does not change with how the day went. It is the hardest of the three to reach by accident, because most foods that carry it also carry fat or carbohydrate. And it is the number the algorithm protects on a deficit — the tier goes up by 0.2 g/kg on a losing goal, while carbohydrate absorbs the calorie cut.

A working habit: plan the protein sources for the day before anything else, then let fat and carbohydrate fill in around them. If the day ends with protein on target and fat or carbohydrate a little off, the day was fine.

The 80/20 of accuracy

Perfect logging is not possible and not needed. Labels and databases are approximations (see why macros don't add up to calories), and a few percent of error per item is built in. What an adaptive tracker needs is a log that is off by roughly the same amount in the same direction every day — that error becomes part of the expenditure estimate and stops mattering.

Worth the effortNot worth the effort
Weighing protein sources, oils, nuts, grains and anything denseWeighing lettuce, cucumber, herbs
Logging restaurant meals with a rough high estimateSkipping the entry because it cannot be exact
Choosing one database entry per food and reusing itHunting for the "most accurate" entry each time
Logging every day, including the untidy onesLogging only the good days

The last row is the important one. A missing day is worse than a rough day: an estimate carries information, a blank carries none.

When to adjust

After two weeks of consistent logging and weigh-ins, compare the weight trend with the goal. If the trend matches the intended rate, nothing changes. If it does not, adjust the calorie target — by a modest step — and let the formula redistribute the macros; do not edit protein, fat and carbohydrate separately, because the split would drift away from the rules it was built on. Then measure for another two weeks before deciding again.

Two guardrails stay in force through every adjustment: the calorie floor (1,500 kcal for a male profile, 1,200 kcal for a female profile on a losing goal) and the 35% cap on any deficit. A change that would cross either is a sign the goal rate is too aggressive, not a sign to override the floor.

In plain terms: adjust calories, not macros; adjust from a trend, not a weigh-in; and never past the floors.

The short version

Three numbers from the macro calculator; two weeks of weighed food and daily weigh-ins before any change; protein reached first every day; logging consistent rather than perfect; and adjustments made to the calorie target only, from the trend, inside the floors and the 35% cap. That is the whole method — the rest is habit.

Educational overview only — not medical advice. Zyra is a training and nutrition tracking tool; the numbers here are the algorithm's rules and published reference values, not an individual prescription.