Take time off without losing your progress

You are travelling, ill, injured, or simply need a real break. Your plan should wait without turning those days into failures.

What the agent needs to hear

Behind your sentence, the agent works backwards to four pieces: when the break starts, when your goals should count again, whether you want to record a reason, and which local dates you mean. If travel makes the calendar ambiguous, name the place: « start August 7 in Madrid time ».

The start can be today, a future date, or up to two days ago. The return can be a date or deliberately open. A reason — travel, illness, injury, deload, or something else — is optional and never guessed. « Starting today, no return date yet » is enough when you do not know how long you need.

Start and return dates — what counts

The start date is the first protected day. The return date is different: it is the first day your goals count again. So « away August 7 through 16, back on the 17th » protects ten calendar days; August 17 belongs to your normal plan. Say « back on the 17th » rather than the ambiguous « until the 17th ».

Dates stay attached to the local time zone captured when you schedule the period. Flying across midnight does not move the boundaries. If the trip crosses zones, say: « use Madrid dates — back on August 17 ».

An open return is not a placeholder the system fills for you. It means the break continues until you choose a return. Use it for illness or recovery when an invented date would create pressure instead of clarity.

What Verxion freezes and what stays active

Time off pauses evaluation, not your plan. Daily obligations disappear for the protected dates; streaks, adherence, scoring, programs, and mesocycle timing wait for your return. Missed sessions or meals from the period do not reappear later as debt. Your routine, diet, program, and history remain intact throughout.

You can still train, walk, log food, or record a measurement if you want to. That activity stays in your history, and training volume or a genuine personal record remains yours. It simply does not turn a protected day back into an evaluated one or advance a streak during the break.

That makes time off different from nearby choices. One date that was meant to be rest is a planned rest day. A deload is lighter work that remains planned and evaluated. Pausing a routine stops that routine’s clock only. Time off protects every evaluated goal across the period without dismantling any of them.

When plans change

Read the confirmation as the checkpoint: the start date, return date, and stated reason should match what you meant. If the agent hears August 17 as another protected day, correct the boundary in plain language: « no — my goals count again on the 17th ». If it adds a reason you did not give, say « leave the reason blank ».

Later, keep talking instead of rebuilding the period. « Move my return to August 20 » extends it. « I don’t know when I’ll be back — leave it open » removes the return. If you recover sooner, « end my time off today » makes today count again. If a future trip disappears, « cancel that time off » removes the scheduled period. These are follow-ups, not variants of the original request.

What makes the break worth recording

Three things decide whether time off helps you later: the start date matches the first day you should not be evaluated, the return date names the first day goals count again rather than the last day away, and the reason is honest when you choose to include it. Verxion uses those boundaries to keep expectations, streaks, and adherence readable while preserving every plan and voluntary log; recording the break cleanly lets your history show rest as rest, not as failure.