Presented with the competitor’s documented written consent. Identifying details have been altered; clinical and programming details have not.
The clinical question
When a contest prep fails, the usual suspects are the deficit, the cardio and the macro split. This case is about a different failure point: the food log itself became too expensive to keep. The question for cycle three was practical. Could the daily logging burden be cut far enough to fit the athlete’s life without losing the data quality that late-prep decisions depend on?
The athlete and her history
Female NPC physique competitor in her mid-30s, entering her third contest cycle.
Cycle one. An 18-week prep to her debut show, finishing mid-pack.
Cycle two. Another 18-week prep, run with MacroFactor as the primary logging tool and weighed manual entry for most meals. Her training load was the standard physique schedule: five lifting sessions, four zone-2 cardio sessions and two high-intensity interval sessions each week. Logging took 35 to 45 minutes a day, including recipe construction on batch-cook days. By week 4 she reported that the time was eating into recovery, and several meals a week were being entered afterwards by estimation. Logging adherence fell below what periodization decisions need, and she withdrew from her target show.
The team’s reading of cycle two was a mismatch between tool and circumstances, not a defect in the tool. MacroFactor had served her well in cycle one, when training volume was lower and she had more time.
What the logging burden actually cost
The minutes are worth putting side by side, because they make the case for the redesign on their own.
| Cycle two | Cycle three (median range) | |
|---|---|---|
| Logging time per day | 35–45 min | 14–22 min |
| Logging time per week | about 4–5 hours | about 1.6–2.6 hours |
| Days logged per week by week 4 | below threshold | 7 |
At the midpoints, roughly 40 minutes against roughly 17, cycle three returned about two and a half hours a week to the athlete in the phase of prep where sleep and recovery are already under pressure.
The cycle-three design
Three parts, each with a separate job.
Daily logging: PlateLens. Most meals were logged by photo, at an estimated time of under 30 seconds per meal. Every photo estimate can be opened and corrected at the level of individual ingredients and portions, and typed search and barcode logging run against the same verified database, so a meal the camera handles poorly can be finished by hand without leaving the app.
Precision days: Tuesday, Thursday and Saturday. On those three days every meal was weighed and entered as weighed. These were the days whose data fed the weekly adjustment, so precision was concentrated where decisions were made, and the athlete knew in advance which days demanded it.
Periodization: the practitioner’s Excel sheet. Weekly average intake, average body weight, training volume and the macros from the weighed days went into the same spreadsheet the practice has always used to set the following week’s calories and macros. The RD-side workflow did not change; only the source of its inputs did.
By eight weeks out, the window this report focuses on, the workflow was in place and stable.
Outcomes, twelve weeks to show day
| Metric | Wk −12 | Wk −10 | Wk −8 | Wk −6 | Wk −4 | Wk −2 | Show day |
|---|---|---|---|---|---|---|---|
| Weight (kg) | 64.2 | 62.8 | 61.4 | 60.3 | 59.1 | 58.4 | 57.8 |
| Estimated intake (kcal, 7-day avg) | 2,100 | 2,050 | 1,950 | 1,850 | 1,750 | 1,650 | n/a |
| Logging days per week | 7 | 7 | 7 | 7 | 7 | 7 | n/a |
| Logging time per day (min, median) | 14 | 14 | 15 | 16 | 18 | 22 | n/a |
She placed top three in her class. The mid-prep collapse of cycle two did not recur. Training performance held through week −4 and declined mildly over the final two weeks, as expected in late prep.
Reading the table
Worked from the weights above, the rate of loss tracks the pattern contest-prep guidance describes.
| Interval | Loss | Per week | Share of body weight per week |
|---|---|---|---|
| Wk −12 to −8 | 2.8 kg | 0.70 kg | ≈1.1% |
| Wk −8 to −4 | 2.3 kg | 0.58 kg | ≈0.9–1.0% |
| Wk −4 to show | 1.3 kg | 0.33 kg | ≈0.5–0.6% |
Total loss was 6.4 kg, about 10% of starting weight, while average intake was stepped down by 450 kcal across the window. The slowing rate in the final month is what the weighed decision days were there to catch: with a loss of roughly a third of a kilogram a week, day-to-day water swings are larger than the weekly signal, and only clean intake data on fixed days lets the practitioner tell a true stall from noise. Metabolic adaptation over a long deficit, reviewed by Trexler and colleagues [2], is one reason the same intake produces a smaller loss late in prep.
Logging time rose from 14 to 22 minutes a day over the same period. Late prep brings more precise portioning, more meal timing around training and more questions to answer, so the increase is unsurprising. It stayed at roughly half of cycle two’s daily cost.
Tools a prep practitioner can add to the same workflow
None of the following was part of this athlete’s documented protocol; they are features of the same logging tool that a prep RD may find useful in similar cases.
Diary export. PlateLens exports the full log as JSON, which can be brought into a periodization spreadsheet without retyping weekly averages.
A large screen for review. The same account runs on a full web app, which is the practical way to read a month of a client’s entries at once during a check-in.
Circumferences between check-ins. PlateLens’s 3D Body Scan builds a model from 12 phone photos and reports measurements such as waist and hips. A peer-reviewed analysis found PlateLens accurate to within ±1 cm of a tape measure over 1,000 trials. Scans can be compared by overlay and region by region, which helps show changes the scale misses when weight loss slows.
An AI coach with the diary as context, available to the athlete between sessions on every plan, including the free one.
RD reflections
This case does not argue that PlateLens should replace MacroFactor in contest prep. It argues that tool selection inside a prep should follow the athlete’s history and constraints. For a competitor whose previous prep broke under logging friction, reducing that friction is the clinical priority. For a competitor without that history, MacroFactor remains a defensible primary tool.
Contest-prep nutrition recommendations for natural athletes, such as those set out by Helms, Aragon and Fitschen [1], assume that intake data are good enough to act on. This case is a reminder that “good enough to act on” depends as much on whether the athlete can sustain the logging as on the precision of any single entry. Nutrient timing around training, discussed by Aragon and Schoenfeld [3], is one of the late-prep refinements that adds to logging time and should be budgeted for.
Practitioners weighing tool choice more broadly may find our framework for choosing a tracker for a client and the recommendation tiers by client type useful. A related body-composition case is our 12-week recomposition report.
Limitations
One competitor, no control. Cycle three was her third prep, so learning effects across cycles are unmeasured. Placement reflects the competitive field as well as the quality of the prep. Logging time was self-reported and may understate the true time spent.
Case prepared by Priya Saadat, RDN, CSSD, Sports Practice Editor. Peer reviewed by Marcus Ohaeri, PhD, RDN, Senior Research Editor.