Back to Workforce OS Workforce OS · Calendar

Define How Your Company Works.
Down to the Day.

Every time-based HR process — leave accrual, time tracking, shift scheduling — depends on one thing: an accurate definition of your working calendar. The Calendar module is where you set those rules once, correctly, so every other module can apply them automatically.

🏖️

Public Holiday Management

Configure public holidays for every country and region where your team operates. Assign the correct holiday calendar to each employee based on their work location. When Leave Management calculates a leave request, it already knows which days count and which don't — without manual adjustment.

🎉

Company-Specific Off Days

Beyond statutory holidays, most companies have their own calendar events — a company-wide shutdown between Christmas and New Year, a local office closure, an annual company day. Define these once and they flow through to everyone's leave balances and attendance records automatically.

🏠

WFH / WFO Schedules

Define hybrid working patterns at the team or individual level — which days are office days, which are remote days, which are flexible. These configurations provide the structure that Time Management and Attendance tracking need to interpret presence correctly across a distributed workforce.

⏱️

Working Time Configurations

Specify exactly what a standard working day looks like for each group of employees — start and end times, break durations, daily hour targets. These configurations underpin overtime calculations, leave deductions, and time tracking across every module that touches time.

The Hidden Dependency in Every HR System

Most HR software treats the working calendar as an afterthought — something you configure once in setup and then forget is there. That works fine until an employee in a second country has to request leave on a day that is only a holiday for their location. Or until a shift schedule collision happens because the system didn't know that a particular day was a company shutdown.

We built Calendar as a first-class module because it is a first-class dependency. It is the reference that Leave Management checks before approving a request. It is the baseline that Time Management uses to calculate whether someone worked overtime. It is the foundation that Shift Scheduling builds on when planning coverage.

Get the calendar right, and every time-based process downstream becomes straightforward. Configure it with care, and you will stop manually correcting edge cases that should never have arisen.

"Every HR calculation involving time starts with a calendar. Ours makes sure that calendar reflects the real world — every team, every location, every edge case."

— ZenSkayl Product Team

Set your working rules once. Let every module follow.