How should a team make working hours and availability visible?

Start with a shared convention, not a new monitoring process. Choose one place the team already checks, such as a shared team page or calendar, and give everyone the same small set of fields:

1. Usual working hours and time zone.
2. Preferred contact window, if different from those hours.
3. Planned absence dates or a simple out-of-office note.
4. Where to leave a message when a reply can wait.

Make clear that the information helps people plan; it is not a promise of immediate replies. Each person can describe a regular pattern rather than logging every daily change. For instance, a placeholder entry could read: “Usually works [days and hours], [time zone]. Best window for non-urgent questions: [time range]. Planned absence: [dates or location of calendar entry].”

Use “usual hours” for the broad pattern someone expects most weeks, and “contact window” for a time when they prefer to handle messages or conversations. They do not have to be identical. Someone might usually work a split day, for example, but prefer meetings during a narrower block.

For a flexible schedule, invite people to write “varies” and name the best way to check for a particular day—for example, their current calendar or status. Avoid asking anyone to justify their schedule or publish personal reasons for it. Agree that a current calendar entry or brief status update takes precedence when the usual pattern changes. That keeps the convention useful without suggesting that a schedule is fixed.

Separate absence information from expectations about coverage. Ask people to mark planned time away in the agreed calendar or shared location, with only the detail colleagues need to plan. A short “away [dates]” entry may be enough; personal explanations are not needed.

Then decide what the team means by “urgent.” Name an existing team-approved route for genuinely time-sensitive work, and identify who is responsible for checking it during a stated period. If there is no coverage, say so rather than implying that an absent teammate should respond. For ordinary questions, use the usual team channel and let the person reply during their working time. This convention can clarify coordination, but it cannot by itself create staffing coverage or settle every team’s work-time expectations.

You could share this draft and adjust the bracketed parts together:

“Team availability: Please add your usual working pattern and time zone to [shared location]. Include a preferred contact window if useful. Mark planned absences in [calendar or shared location], with details limited to what teammates need for planning. If your schedule varies, say so and note how colleagues can check your current availability. Messages outside someone’s stated hours can wait unless the team’s agreed urgent route and coverage plan apply. No one is expected to share personal reasons for a schedule or absence.”

Try the convention for a short, agreed review period. Ask whether people can find the information, whether handoffs or meeting planning got easier, and what felt intrusive or unclear. Change only the parts causing friction. Keep ownership simple: each person updates their own pattern, while the team agrees on the location and shared expectations.