Correspondence Regarding Home Lunch Invisibility
A lunch break taken at home without announcement becomes, over time, a scheduling commitment.
Dear colleague,
This note concerns the matter of home lunch invisibility and its administrative consequences.
You are aware, presumably, that your lunch break on work-from-home days occupies a calendar gap and is not marked on the shared calendar. This is not a complaint. Most people do not mark lunch on a shared calendar. The difference, in your case, is that the lunch has become a coordination point.
Someone eats lunch during a quiet calendar gap at home without marking a break because no one can see it. This was initially unremarkable. It became remarkable around the fourth week when a Tuesday proposal arrived at 1 PM and you were, briefly, unreachable. The proposal was not urgent. However, in the interval before you replied, two colleagues made scheduling assumptions that required unwinding.
Home lunch invisibility adds one coordination step to the day. Coworkers start planning around that step. Flexibility hardens into an unwritten schedule.
The day is called flexible while requiring extra location planning. This is the structural issue, and it is not yours specifically. The hybrid policy assumes that a person at home on Tuesday is reachable in the same way as a person in the office on Tuesday. This assumption produces the coordination problem, which is then managed through informal personal adjustments, of which your unmarked lunch break is one example.
Under the governing rule, home lunch invisibility becomes procedure once repetition feels safer than reconsidering it. You have now eaten lunch at home during the same Tuesday gap for eight consecutive weeks. The step has become policy.
We are not asking you to change the lunch. We are noting that it has already been calendared, informally, by the people who plan around it. A formal entry would only make visible what is already functioning as a constraint.
With continued sympathy for the calendar situation,
The Correspondence File