Holidays
Holidays are a dated list of days the company is shut. Small module, and the one that stops three other screens from lying to you.
Add an entry with a date, a name and a short note explaining it. That is the whole record. The list is the source other modules read.
Attendance reads it, so a national holiday does not appear as a wall of absences on Monday morning. Nobody has to explain the dip in the monthly report.
The capacity grid reads it too, marking those days so planned hours land on days people are actually working. Without the calendar, a month with three closures looks like a month with three days of missing effort.
Set it once at the start of the year and the calendar quietly does its job. Most admins touch it twice: in January, and again when a date moves.
The description field earns its place. A closure named only by its date tells a new joiner nothing, and six months later nobody remembers whether the office was shut for a public holiday or for an anniversary the founders declared.
Order of setup matters. Enter the year before anyone runs a monthly attendance report, because a report built while the calendar was empty will show absences that were never absences, and somebody will have already acted on it.
Nothing about a closure touches a leave balance. A shut office is not a day anyone spends from their quota, and keeping the two separate is what makes both numbers defensible at the end of the year.
Days that only some people take are a different animal. A restricted or optional holiday is closer to a leave type, because it is chosen rather than imposed, and treating it as a closure would mark the whole company shut when it was not.
Announcements that move at short notice are the normal case in plenty of countries, not the exception. Editing an entry takes a moment, and every screen reading the calendar picks the change up, so a late change is a small task rather than a set of reports to redo.
A calendar is boring to maintain and expensive to neglect. Twenty minutes in January, and three other modules stop producing numbers somebody has to explain.
What it does
- Dated entries
- A date, a name and a description. Nothing else to fill in.
- Attendance reads it
- Closed days stop counting as absence, so the monthly figures stay honest.
- Capacity reads it
- Closures show in the planning grid, so planned hours land on working days.
- One list to maintain
- Edit in a single place and every screen that depends on it updates.
What it needs before it works
- Your dates for the year, confirmed. Some move at short notice and the calendar has to move with them.
- Somebody who owns the update, because a stale entry corrupts two other reports at once.
Questions people ask
Does a holiday consume anyone's leave balance?
No. A closure is a company-wide day off. Leave balances are separate, and a holiday does not draw against a quota.
What if a date is announced late?
Edit the entry. The screens that read the calendar pick up the change, so a late announcement is a one-minute fix rather than a report to re-run.
Are optional or restricted holidays supported?
Set them up as a leave type. A closure shuts the whole company, while an optional day is chosen by each person, so a leave type with its own quota fits it better.
Should the calendar be filled in before the first report?
Yes, and it is worth doing early. A monthly attendance report run against an empty calendar shows closures as absences, and somebody usually reacts before anyone notices why.