Start a meal plan with the food you like, the cooking time you have, and the meals your week needs to cover. A plan for three office lunches requires different choices from one for evenings when you can cook.
ChatRPE can use meals you have logged as suggestions, then help adapt portions and preparation to your targets. Confirm what you want before treating a suggested menu as the week's plan.
From template plan to personal plan
| The generic meal plan | The ChatRPE plan |
|---|---|
| Recipes chosen by a stranger | Meals drawn from what you already log and like |
| Fixed seven-day grid | A structure that expects restaurants, travel, and leftovers |
| Breaks the first time you deviate | Replans the rest of the day in one message |
| Macros estimated by eyeball | Packaged foods scanned exactly, named foods looked up |
| A prep day you improvise | A batch-cooking list built from the plan you just approved |
| Lives in a PDF you lose | Lives in the same logbook as your targets and results |
“Dinner plans changed, we're getting pizza. Rework the rest of today so I still land near my protein target, and adjust tomorrow if needed.”
Plan the structure, not every bite
The highest-value planning is boring: repeatable breakfasts, a default lunch, two or three dinners you rotate, and a plan for the risky moments, meaning the 3 p.m. vending machine and the Friday takeout. Ask the coach to plan at that level first. Set the targets the plan serves with the macro calculator workflow, and keep precision honest rather than theatrical.
Because planning and logging live in one place, the loop closes by itself: the plan says chicken and rice, you log what actually happened, and next week's plan learns from the difference. A meal you ate five times this month is a better plan candidate than any recipe database result.
What to eat this week, decided from what you actually eat
The reason “what should I eat this week” is hard to answer in the abstract is that the good answer is already in your history and you cannot see it from there. ChatRPE can search your saved entries by keyword, data type, and time window, so the planning conversation can start from evidence:
- “Which lunches have I logged most often in the last month?” The three or four that come back are your real rotation, and they belong in the plan.
- The meal you logged once in April is not a habit, it is an experiment that did not take. Leave it out.
- Search your notes for the evenings that went sideways, then plan around that pattern rather than around your intentions.
Narrow the search by entry type or by month when you want a specific stretch of the year. For planning purposes recent is usually what you want anyway, since last month's habits predict next week far better than last year's do.
Meal prep without a cookbook
Batch cooking is the highest-leverage hour in the week for most people, and it fails for a boring reason: the plan and the prep list are written at different times by different logic. Ask for both in the same message and the prep day becomes a checklist instead of a Sunday afternoon of improvisation.
A useful prep brief answers four things: what to cook ahead, how many portions of each, what to buy, and which meals cover which days. Ask ChatRPE to write the shopping list in the same conversation and it comes out organized by the meals it belongs to, not as a wall of ingredients.
Then attach accountability to it. Ask for a reminder, “Sunday at 4, remind me to prep lunches,” and the coach schedules it and keeps it current, pruning it when it stops being relevant. Separately, if push notifications are enabled in the iOS app, ChatRPE also runs a periodic check of your recent logs and reaches out when there is a data-backed reason to; the accountability guide explains both mechanisms and how they differ. The daily coaching guide shows how those check-ins keep the plan alive midweek.
“Here's the plan for next week. Tell me what to batch cook on Sunday, how many portions of each, and write the shopping list grouped by which meals it covers.”
Macros the plan can actually hit
A plan is only as good as the numbers behind it, and this is where most meal planners quietly guess. ChatRPE has three levels of precision available and uses the one that fits:
| What you are planning | How the number is produced |
|---|---|
| A packaged staple you buy every week | Photograph the barcode and the exact label data is looked up |
| A named whole food or brand item | Searched against food databases and returned with real macros |
| A restaurant plate or something you improvised | An explicit estimate, labelled as one, or a published figure looked up |
The middle row is the one that matters most for planning, because a week of meals is mostly named foods rather than barcodes. When you say “200g chicken thigh, 150g jasmine rice,” those get looked up rather than invented. The food barcode scanner guide covers how the exact-data path works, and the calorie tracker guide covers the precision ladder in full.
The bottom row is where a plan usually meets reality, since a planned week almost always contains a meal somebody else cooks. The eating out guide covers getting a defensible number for it, including looking up a chain's published figures before you order so the meal can be budgeted into the day rather than reconstructed afterwards.
If you are planning for a specific outcome rather than maintenance, get the targets right before the meals: the protein calculator sets the protein floor a meal plan for muscle gain has to clear, and the calorie deficit calculator produces the number a fat-loss week is built around.
Did the plan actually work?
The point of planning is not the plan; it is the week that follows it. Because the plan and the log live in the same place, the review is one question.
Ask for your average daily protein and calories over the last month, with the high, the low, and which direction things are moving. Or ask for a chart of daily protein with a target line drawn across it, so the days you missed are visible rather than remembered. Both are drawn from entries you already logged, and the nutrition dashboard workflow covers pinning them so the review is waiting for you instead of re-requested weekly.
Two things worth knowing about those summaries: they read a bounded recent window rather than your whole history, and the “trend” they report compares the first half of the period against the second rather than running a statistical test. That is plenty to answer “is my protein drifting down,” and it is not a claim about causation.
When the answer is that adherence was fine but the results were not, the problem is usually the target rather than the plan. The weight loss plateau guide covers diagnosing that, and the AI nutrition coach guide covers what an ongoing coaching relationship does that a static plan cannot.
Frequently asked questions
Can ChatRPE create a meal plan for my macros?
Yes. Give it your targets, preferences, and schedule and it drafts the week, then adjusts the plan in conversation when your real week diverges from it, which is where standalone meal planners stop helping.
Is there a meal prep app that plans around my macros?
That is exactly this workflow. Ask for the week's plan and the prep brief in one message: what to batch cook, how many portions, what to buy, and which meals each batch covers. Because the plan is built from meals you have already logged, the prep list is food you already know you will eat rather than a recipe experiment you abandon on Wednesday.
What should I eat this week?
Start from your own history rather than a blank page. Ask which meals you have logged most often in the last month, keep the three or four that come back, and let the coach fill the gaps against your macro targets and the nights you know will be busy. A rotation you have already proven you will eat beats an optimized plan you will not.
Do I have to follow the plan exactly?
No, and you won't, which is the design assumption. Log what actually happened and ask the coach to rebalance the rest of the day or week. A plan that survives deviation is the only kind that works.
Can it write my grocery list?
Yes. Ask for it in the same conversation as the plan and it comes back grouped by the meals it covers, so you can drop anything you are not actually cooking. It is written from the plan you just approved rather than from a fixed recipe database, which is why it tends to match what is already in your kitchen.
How do I plan meals for muscle gain?
Set the protein floor first, then build the week's meals to clear it, and keep total calories slightly above maintenance. The protein calculator works out the band and the how to build muscle guide covers what has to be true in training for those calories to become muscle rather than just weight.
What about dietary restrictions and allergies?
State them once and the coach remembers them for every future plan and suggestion, so you are not restating the same exclusion every week. Where a diet is medically prescribed, or an allergy has real consequences, or a condition dictates what you can eat, your clinician or registered dietitian sets the rules of the plan. ChatRPE is then the thing that builds a followable week inside those rules and shows, in the log, whether you actually held to them.