BuzbyTimeRead the requirements guide

Remote and hybrid · 6.5

Where the working day ends

Where the working day ends. What decides it, what it costs, and what usually goes wrong. For a practical comparison point, see Monitask's time tracking and invoicing.

The commute was doing somethingWhat was lost

Not the travelling. The transition: a period between work and not-work in which one state ended and another began, imposed by circumstance and requiring no discipline from anybody.

Removing it removed the boundary, and the replacement has to be constructed deliberately because nothing supplies it. For related guidance and industry context, see PwC.

What the record shows

  • Entries drifting later month by month.
  • Weekend entries appearing where there were none.
  • The gap between first and last entry of the day growing while total hours stay flat, which is the signal of a day spread thin rather than a long one.
  • No consistent stop time.

The third is the most informative and the least noticed. A person working seven hours spread across thirteen has not had an evening.

What actually helps

A stop ritual. Anything that marks the end: a walk, closing the laptop and putting it away, writing tomorrow's first task. Trivial and effective, because the boundary was always a ritual rather than a rule.

A blocked end of day in the calendar. Which prevents the meeting at five thirty rather than requiring somebody to decline it.

A separate space, or at least a separate arrangement of the same space. Not available to everybody and worth doing where it is.

What managers do that undoes all of it

Send messages in the evening. Whatever the policy says, a message from a manager at eleven at night establishes the norm, and the more senior the sender the stronger the effect.

Scheduled sending exists in every tool and costs one click. A manager who works odd hours and does not impose them is doing the single most useful thing available here.

Team norms, written

  • The hours we expect to be reachable.
  • What is urgent, and how it arrives.
  • That messages outside hours carry no expectation of a reply.
  • That anybody may say a request has arrived at a bad time.

Four lines, agreed by the team rather than issued to it, and revisited when they stop being true.

Where the record helps and where it does not

It shows the pattern, which is what makes the conversation possible. It does not show whether somebody minds, and some people genuinely prefer a fragmented day around other commitments.

Which means the record identifies who to ask rather than what to conclude. The entry on what no record will tell you applies again.

The legal dimension

Covered separately in the entry on overtime and the right to disconnect. This entry is about the practice; that one is about the obligations, and in several jurisdictions the second now constrains the first.

Holidays

Remote workers take less leave and work more of it. A record showing entries during somebody's booked holiday is one of the clearest signals available and one nobody looks for.

Look quarterly. A manager who notices and says something is doing more for retention than most engagement initiatives.

The always-on team member

Usually the most committed person, frequently the one who leaves in eighteen months. The pattern is visible in the record months before the resignation, and the intervention is a conversation rather than a policy.

Have it as a resourcing question. Somebody working constantly is usually covering for something structural, and treating it as a personal habit misses the cause.

Different people, different shapes

Someone with school runs works a split day, and their record looks like erosion when it is an arrangement that suits them. The pattern alone cannot distinguish the two.

Which is the recurring lesson: the record tells you who to talk to, and the conversation tells you what it means.

What to do this week

Look at your own last month of entries. Most managers reading this have a boundary problem of their own, and it is the one their team is copying.

Onboarding somebody remotely

New people set their boundaries by watching, and they cannot watch. Tell them explicitly in the first week what the hours are, that evening messages need no reply, and that finishing on time is expected rather than tolerated.

Otherwise they infer from whatever they can see, which is usually the timestamps on their manager's messages.

A short summary

The commute was doing the work of a boundary. Watch for drifting entries, weekend work and a day spread thin. Build a stop ritual and block the end of the day. Managers should schedule their evening messages. Write the team norms. And check whether anybody is working through their holidays.

One line to carry

The boundary was always a ritual rather than a rule, and removing the commute removed the ritual without replacing it.

The four-day question

Where an organisation compresses hours, the record shows whether the compression happened or whether five days of work is being done in four. It is one of the few interventions in this area with a clean measurement available, and it is worth measuring before declaring success.

Where to start

Turn on scheduled sending for your own messages. One setting, and it changes what your team believes the hours are.

A last note

Every remedy here is available to a team without permission from anybody, which is unusual in this subject and worth noticing.

Reviewing the norms

Twice a year, read them aloud in a team meeting and ask whether they are still true. Norms that have quietly stopped being observed are worse than none, because everybody knows they are decorative and draws a conclusion about the rest.

Also in remote and hybrid