Eat off-plan for today only

You're going to a wedding tonight. You're not going to track three courses and dessert against a cut plan target. Telling the agent that today is off-plan keeps your adherence percentage honest — the day still gets logged, it just doesn't get scored.

What the agent needs to hear

Behind your sentence, the agent works backwards to two pieces: the date to override — today by default — and the reason, optional but useful for the weekly review’s narrative. The active plan is the implicit context; the agent already knows which engagement is running and which day’s slot it’s about to flip.

« Override today » is enough most of the time. If the override is for another date, name it — « override Saturday — off-plan, wedding ». A reason isn’t required, but « wedding », « traveling », « sick » all show up in the weekly summary as context for the dip.

The agent confirms before flipping the day’s state. A single nod is the whole interaction — the day’s slot reads as off-plan from that moment forward.

What override actually does

The override is narrow on purpose. Today’s slot is flagged off-plan and nothing else moves. Meal logs still happen — water, supplements, every meal you eat — but they’re tagged off-plan rather than counted against the plan’s targets for the day. The macro totals still appear in your live progress card, so you still see what you ate.

The override is single-day by default. It doesn’t carry forward. Tomorrow’s slot reads as the plan again, with the day-1 queue back in place. If you’re going off-plan for a week, that’s a different conversation — a plan-pause, not an override.

How override reads in adherence

An overridden day is excluded from the adherence percentage for the week. The weekly review still shows what you logged on Saturday, but it doesn’t score those meals against plan targets — they sit in the day with an « off-plan » tag.

The streak counter pauses but doesn’t reset. An override is « expected absence », not a streak break. This is the whole point: planned deviations — weddings, travel, sick days — shouldn’t punish your adherence trail the way a hidden off-plan day would. Honesty about today protects the signal across the week.

When the agent gets it wrong

A forward-dated override is the easy place to miswire. If the agent flipped today when you meant Saturday, correct it in the same breath: « no, Saturday, not today ». The day rolls back and the right one flips.

If the agent treated the override as a permanent plan change — « plan is paused until you reactivate » — push back: « today only, the plan is back tomorrow ». The state narrows to the single day. And if the agent skipped the confirmation step on a multi-day or forward-dated override, ask for it: « show me what days you’re touching before flipping ».

What makes the override worth using

Three things decide whether overriding today helps the week’s signal: the right date is the one overridden — a wedding-Saturday override accidentally hitting Friday breaks both days, the override is single-day, not a permanent plan change — if you’re going off-plan for a week, that’s a plan-pause, and logs still happen on the overridden day — silent zero is not the same signal as « tagged off-plan », the day still tells a story. The system uses overrides to keep adherence percentages honest across weeks where planned deviations would otherwise punish the signal. Name the day, name the reason if it matters, and log the food the way you ate it.