The team leave calendar: who sees it and what it shows
Echipa HR 365 · reviewed 2026-09-05 · 5 min read
A leave calendar visible to the team prevents most clashes before they reach approval: people pick their own periods once they can see who else is away. The condition is that it shows the period and the name, not the leave type — the latter turns a planning tool into a source of comparisons.
What is displayed and what is not
| Information | The team | The manager | HR |
|---|---|---|---|
| Who is away and when | Yes | Yes | Yes |
| The state of the request (submitted / approved) | Yes | Yes | Yes |
| The leave type | No | Yes, where operationally relevant | Yes |
| Each person’s remaining balance | No | Yes | Yes |
| The reason, where one exists | No | No, unless it is operational | Yes |
The leave-type row is the one most often got wrong and with the most unpleasant consequences. A calendar showing “sick leave” next to a name communicates health information to the whole team, without anyone having decided that. For planning purposes, “unavailable” is enough.
Why the request state matters
A calendar showing only approved leave misses exactly the moment it could still help: the period when two requests overlap and neither has been decided. Showing submitted requests, with a different visual marking, lets the second person see the situation before submitting — and they usually move their own dates.
The effect is measurable: most clashes get resolved between colleagues, without reaching the manager, simply because the information was available in time.
Who you show: the team, the department or the whole company
The practical rule: the calendar shows exactly the group the person shares their work with. In a company of 200, a single shared calendar is illegible and useless — nobody needs to know when somebody from another department is away, except for functions that connect to each other.
- Their own team: in full, for every member.
- Neighbouring departments they work with daily: only the contact people, not the whole list.
- Leadership and single-holder functions (accounting, IT, a sole specialist): visible more widely, because their absence affects everyone.
- The rest of the company: no. It adds noise without solving anything.
Public holidays and non-working days, in the same calendar
A leave calendar that does not also show non-working days produces bad planning: people spending days on periods when nobody was working anyway. The two pieces of information are read together or not read correctly.
The same goes for shift teams: the calendar has to show the schedule too, or “away on Tuesday” means nothing for somebody who was off on Tuesday regardless.
Where to start
Open your calendar with a colleague’s eyes and check whether you can work out why somebody is away. If you can, you have a confidentiality problem nobody decided on.
Then check whether undecided requests appear. It is the change with the greatest effect: it moves clash resolution from the manager to the team, where it happens faster and with less frustration.
How it stays current
A manually maintained calendar is current in month one and wrong by month three. The difference is not discipline but how many times the same information has to be entered: if an approved request appears in the calendar automatically, it stays correct; if somebody has to copy it there, sooner or later they will not.
The test is simple: take three requests approved last month and check whether all three appear. If one is missing, the calendar is no longer a source, it is an approximation — and people will stop looking at it exactly when you need it most.
When you need another form as well
- A feed people can add to their usual calendar — the most used form, because it does not require opening another tool.
- A printable monthly view, for teams that work without a computer.
- A weekly view for managers, showing coverage by function rather than only names.
- A simple export for production planning or accounting, if they ask for one.
The third form is the one most often missing and the most useful to a manager: they do not care how many people are away, they care whether each kind of work still has somebody to do it. A list of names does not answer that; one grouped by function does.
Do I show leadership’s leave too?
Yes, and it is genuinely useful: a team that sees managers actually taking leave gets a stronger signal than any message about balance. The same content rules apply as for everybody else.
What about unavailability that is not leave?
It appears as “unavailable”, with no detail — training, travel, reduced hours. For planning, what matters is that the person is not available, not why.
How far ahead do I show?
Three months is enough for current planning. For summer, the calendar has to cover the whole planning period, which means from January.
A team calendar with clashes marked, and no leave type shown
Everyone sees who is away and when, including undecided requests, without learning why — so clashes get resolved before approval.
Free account, every module for 7 days, no card required.