Builder mode
Nutrition coaching
Plan the week. Coach the pattern.
Build reusable meal-plan days, map the schedule, give clients practical ways to log, and bring what happened back into the next coaching decision.
AI can assist the draft. People review before save or publish.
One connected loop
Nutrition that survives the handoff.
The plan is only useful if the client can follow it and the coach can understand what happened. Keep authoring, daily execution, and review in the same operating line.
- 01
Plan
Build days worth reusing.
Author meals, targets, and notes once, then bring saved foods, meals, recipes, and reusable day templates forward.
- 02
Schedule
Map the pattern across the week.
Place day templates across the program calendar, review incomplete mappings, and publish an assignment-ready revision.
- 03
Follow
Give the day practical logging paths.
Clients can log planned meals, reuse personal meals, add food manually or by barcode, and review photo estimates before saving.
- 04
Review
Read the pattern before changing it.
Bring adherence, macro deltas, logged meals, photo-review cues, hydration, and supplement context into the next coaching decision.
The planning model
Build the day. Map the week. Publish on purpose.
Fitflux separates reusable meal authoring from schedule mapping and separates the working draft from the revision assigned to a client.
Calendar mode
The weekly pattern
Map reusable days across the schedule, copy or clear ranges, and keep one-level undo close to the active edit.Published revision
The client contract
Save the editable draft separately, then publish the immutable revision a client assignment will capture.Client execution
Give the plan more than one way to survive the day.
An assigned day stays visible, but logging can match the moment. The client can follow the plan, reuse a known meal, enter what changed, or review a photo estimate before saving it.
Hydration and active supplement protocols sit beside meals without turning Nutrition into a wellness sub-form.
Planned meal
Log the meal directly from the assigned day while retaining its plan provenance.My meals
Reuse a personal itemized or macro-only saved meal without changing the trainer library.Barcode or manual
Add what was actually eaten when the day moves beyond the planned prescription.Reviewed photo estimate
Inspect and correct the estimate before it becomes a confirmed nutrition entry.Weekly nutrition review
COACH OWNED- Effective plan and target for the selected date
- Logged meals, daily totals, and missing-log context
- Seven- and twenty-eight-day adherence patterns
- Low-confidence or heavily corrected photo estimates
- Hydration, supplement, and energy-balance context
Review the evidence
Look for a pattern before rewriting the plan.
Compare the effective prescription with confirmed logs and trend context. Missing days stay missing, uncertain estimates stay visible, and the review remains a coaching judgment.
Date-specific adjustments stay explicit. A one-day exception does not silently mutate the reusable base schedule.
Assistance with edges
Use AI where it shortens the work, not where it hides it.
Draft generation and meal-photo estimation are review workflows. They do not bypass provider checks, client confirmation, trainer review, or the explicit publish boundary.
Day-template drafts
Generate a starting point, then resolve the food.
AI can propose an editable day. Provider enrichment, validation, and at most one repair pass happen before trainer review.Meal-photo estimates
Estimate first. Confirm before save.
The client sees the estimated foods and totals, can correct them, and decides whether the entry becomes durable.Coaching review
Keep the decision with the coach.
A nutrition signal can prompt follow-up. It does not rewrite the meal plan, message the client, or publish a revision by itself.Close the nutrition loop
Coach the plan and what happened after it.
Choose the platform plan that fits your active-client roster and bring planning, client execution, and review into the same coaching system.
Join the waitlist