A remote workday that survives caregiving interrupts

Care does not ring once and leave

I should say up front that I am not a full-time carer. For a few weeks last year, though, my working days included driving a family member to a run of appointments, waiting, and driving back, and it taught me how badly my normal way of planning a day handled it.

A delivery takes ninety seconds. An appointment lift took anywhere from fifty minutes to two and a half hours, depending on how far behind the clinic was running, and I never knew which until I was sitting in the waiting room. I would plan the morning as if the gap were an hour, then spend the second hour in a plastic chair answering emails badly on my phone and feeling guilty in two directions at once.

I have also worked on remote teams alongside people who carry far more than that, every week, quietly. Watching how the ones who coped well actually organised their days taught me more than any article about productivity. They did not try harder. They planned smaller, and they said so out loud.

They planned smaller, and they said so out loud.

That is the core of it. The sixty-second park still helps when a doorbell rings. Care is a different kind of interruption: often predictable in when it happens, rarely predictable in how long it lasts, and you come back carrying more than you left with. A day planned for quiet will make perfectly ordinary care feel like failure.

Plan the shrink the night before, not mid-morning

What I saw working, and what eventually worked for me, was deciding the night before what a smaller day looks like. Five steps, ten minutes, done while you are calm rather than while someone needs you.

1. Mark the care windows you already know. A lift to an appointment, a school run, a regular visit, helping with a meal, a phone call with a pharmacy or a school office. Put them on the calendar as busy, not "maybe". A window that is maybe on the calendar is a window you will try to work through.

2. Choose one main outcome for a smaller day. One thing that matters if nothing else finishes. It has to be startable in under two minutes and finishable in about ninety interrupted minutes in total.

3. Slice it into parkable pieces. Each piece ends at a natural save point: a paragraph done, a test passing, an email sitting in drafts, a form submitted. If a piece needs forty quiet minutes and you will not have forty quiet minutes, cut it smaller tonight. Cutting it at 11:00 tomorrow, with your car keys in your hand, is much harder.

4. Write the cut list. If care expands, which two tasks get dropped without guilt? Write them down now. Making that decision while someone needs your attention is expensive, and you will usually choose badly.

5. Set up the desk so you can leave fast. Notebook open, chat closed, the file for the first piece already open. You will leave mid-sentence more often than on a normal day, so make leaving cheap.

Photograph

How this differs from a normal interrupt

Use both. Park when you stand up. Shrink when you plan the day.

An appointment morning, done both ways

Here is the version I did first. I had a proposal to finish for a client, a pricing section and a timeline. There was a lift at 10:00, and I assumed I would be back by 11:15. I planned to write the whole proposal that morning, with the lift as a short break in the middle.

The appointment ran late. I was back at 12:40, hungry, a bit rattled from the waiting room, and with the full proposal still in front of me. I opened chat "to see what I had missed", spent half an hour on it, ate lunch at my desk, and at 15:00 I had a proposal with one half-written section. I worked until eight that evening to finish it, and it was not good work.

Here is the version I did a couple of weeks later, for a similar job:

• Main outcome: pricing and timeline sections only, not the whole document.
• Pieces: (1) put the numbers into the pricing table, (2) write three bullets for the timeline, (3) read both sections through and send the draft link to myself.
• Cut list: the optional case study rewrite, any chat beyond direct mentions.
• Blocks: 25 minutes before leaving, 25 after getting back, 15 more if the afternoon allowed.

Pieces one and two got done, one on each side of the appointment. Piece three slipped to the next morning. At shutdown I wrote "Tomorrow: open the proposal, read pricing and timeline aloud, then send." The day was not what a quiet day would have been. It produced finished work and a clean place to start from, and I did not work that evening. On a care day, that is success, and it should be counted as success.

Label the days before the week starts

One habit I borrowed from a colleague, a developer who was looking after a parent at the time, was labelling each day of the week on Sunday evening. She used three labels and put them in her own calendar:

• Quiet day. A normal deep block is allowed.
• Contact day. The shrink plan is the default.
• Duty day. Meetings plus care. Deep or billable creative work is a bonus only. The honest plan is triage, admin and replies.

The point of writing the label down is that it stops you opening a hard debugging session on a duty day and then feeling awful about it at four in the afternoon. You would not plan a long walk in the rain without a coat. Matching the kind of work to the kind of day is the same idea.

Coming back from care is not like coming back from the door

When you return from a care interruption, there are two checks worth adding before you pick up the park line.

1. A body check, about thirty seconds. Hungry, thirsty, tense, still running on adrenaline? If you are wound up, take three minutes before touching the keyboard. Starting work mid-stress tends to produce work you redo later.
2. A scope check, about thirty seconds. Read the park line, then ask whether the time you have left fits the next piece. If it does not, use the cut list now. Do not start a forty-minute piece with twelve minutes until you have to leave again.

Then the usual: close whatever tabs the interruption opened, restore anything volatile, and touch the work before you touch chat. Chat after a care stretch is a particular trap. It feels like getting back into the adult working world, and it quietly eats the only piece of work you had time for.

Tiredness is part of the capacity

Care days often leave a fog in the afternoon even once the calendar clears. I treat that the same way as any low-energy afternoon: review, light edits, tidying notes, preparing tomorrow's first piece. I would not put the hardest analysis of the week in the hour after a long care stretch unless I know from experience that I bounce back quickly.

A rough rule I use: if care took more than about forty-five minutes of real attention, the next work piece is fifteen minutes of low-stakes progress, not a fresh attempt at something hard.

Tell people your capacity, not your story

Clients and managers do not need to hear the details of anyone's care. They need an honest signal about what you can deliver today. The colleague I mentioned would post one line in the team channel on contact days, roughly: "Contact day today. Main task is the export fix, progress note by 16:00, the bigger refactor moves to Thursday morning." That was it. No apology, no explanation, no running commentary through the day.

It worked better than anything else I have seen. Everyone knew what to expect. Nobody chased her. When Thursday came, the refactor happened. Compare that with going quiet and apologising late, or saying everything is fine and then missing a deadline. A short, factual capacity note is kinder to everyone, including you. If you want a format, the advice in writing async status people read applies here too.

At home, the same plain agreements help: what always interrupts (safety, illness, the agreed care tasks), what waits until your next break, and visible end times on your focus pieces so that waiting has a finish line. If care regularly collides with real deadlines, a backup person or paid help on duty days is capacity planning, not a failure.

Close the day even when the evening is more care

A short shutdown matters more on care days, not less, because the evening may not give you a moment to think about work at all.

1. Park line for tomorrow's first piece.
2. One sentence about what finished.
3. One sentence about what care changed today.
4. Close the laptop on purpose.

Skipping it is how the next morning starts with archaeology and a vague sense of guilt. Two minutes is enough.

Once a week, look at three things: how many days were quiet, contact or duty; how often you finished the main outcome; and how often you worked late to make up for care. If late catch-up evenings happen often, the plan is still lying about how much time you have. Shrink earlier in the week, move deep work to a reliably quiet day, or renegotiate a deadline before it becomes a crisis.

I used to think of those evening catch-ups as being responsible. They are not. They teach everyone, you included, that a care day is a failed day that has to be paid back. Plan for it as a normal kind of day with a smaller shape, finish the one thing you said you would, and stop. The work gets done, the people who need you get you, and nobody has to pretend either one was something it was not.