The week after you get back

You went away for ten days and didn’t do the routine, which you’d more or less expected. What you didn’t expect is that three weeks after getting home you still aren’t doing it, and you can’t identify the day you decided not to resume, because there wasn’t one.

The trip is not what ended it. The trip is a bounded interruption with an obvious end date. What ended it is the return, where the routine had to be started again by intention and nothing in your day raised the subject.

Why the return is more dangerous than the absence

The cue didn’t come back with you. You attached the routine to an event — the kettle, the laptop closing, getting in from work. That event resumed the moment you were home. What didn’t resume is the link, because links are maintained by firing and this one has been idle for a week and a half. So the kettle goes on and nothing follows it, and the absence of a behaviour is not something you can notice happening.

There’s no signal that you’ve stopped. A routine ending doesn’t generate an event. During the trip you knew you weren’t doing it. After the trip, “not doing it today” is indistinguishable from every other ordinary day, and by the time it surfaces the honest description has quietly changed from “I’m away” to “I used to do this.”

Re-entry weeks are genuinely full. Washing, backlog, the fridge, the emails. Everything gets triaged, and a routine that produces nothing perceptible this week loses every triage it enters.

The routine is now a decision again. That’s the real damage. Before the trip it happened without being considered; now it’s a topic, and a topic can be resolved either way — the same mechanism as the morning after a missed day, running for a fortnight instead of thirty seconds.

Plan the return, not the trip

The intuitive move is to work out how to keep the routine going while away. Sometimes that’s possible and sometimes it isn’t, and this site has no view on what you’d do in a hotel room. What matters more, and costs nothing, is deciding in advance what happens when you’re back.

The design has one requirement: the first session home must not depend on you feeling like it.

THE RULE — write this before you leave

  1. Name the first day back. Not "when I'm sorted" —
     the actual date you return, or the morning after.
  2. On that day, the floor version happens. Not the full
     routine. The smallest thing that counts.
  3. It happens at the cue, even if the cue lands at a
     stupid hour that day. You are restarting the link,
     not getting a session in.
  4. Miss the named day → you are on day one of a restart,
     and treat it as one. Not as a continuation.

Rule 3 is the point of the whole rule. What you’re doing on the first day back isn’t exercise, it’s re-attaching a behaviour to an event, and that requires the pairing rather than the volume.

Rule 4 is there because the alternative is drift. If the first day back doesn’t happen, you want a named state — “restarting” — rather than a vague ongoing intention, because restarting has a procedure and drifting doesn’t.

Away as a deliberate pause, not an accident

If the routine isn’t going to happen while you’re away, decide that before you go rather than discovering it on the second night.

The difference is small and it’s the difference between a pause and a stop. A pause has an end date, is not a run of missed days, and generates no deficit. A stop has none of those properties and neither does an unexamined ten days.

Practically: no make-up on return. Ten sessions were not banked and are not owed. The temptation to come back with a bigger version to compensate is the same penance instinct that wrecks long restarts, and it lands here in the week you have least capacity for it.

This is the same structure as being ill, with one difference in your favour: a trip has a known end date in advance, so the pause can be defined before it starts.

The frequent-traveller version

If you’re away often enough that trips aren’t exceptional, the pause-and-return model stops working — you’d be restarting monthly, and each restart costs more than the sessions are worth.

Two structural options, neither of them about what you do while away:

Cue to something that travels with you. Not a place and not a schedule, but an event that occurs wherever you are: waking, the first coffee, the point where you take your shoes off at the end of the day. Weaker than a home-specific anchor and it survives movement, which for you is the property that matters.

Or run a weekly target instead of a daily one. Five out of seven, marked as you go makes a two-day trip a non-event rather than a break, and a seven-day trip becomes one bad week rather than the end of a streak. It absorbs disruption in a way a daily rule can’t.

What this costs

Committing to the floor version on the day you get home means doing something on a day you’re tired and behind, which is exactly when you’d rather not, and it will feel pointless because it’s small enough to be pointless in isolation. It isn’t the session that matters; it’s that the cue fires once. That’s a genuinely unsatisfying reason to do something.

Naming a return date also removes an excuse you were probably going to use. Some people would rather keep it.

What this doesn’t fix

It doesn’t help with the trip itself, and nothing here is about what movement is available in constrained places.

And if the routine was already fragile before you left — no cue, too long, weekends already blank — the return isn’t the problem. A trip just exposed a routine that was running on attention rather than structure, and would have ended at the next disruption of any kind.