HR Time Management defines holidays, breaks, schedules, absence types, quotas and assignments used by time-related operations.
Before presence can be recorded, the structure has to exist: what the holidays are, what a working day looks like, how much leave each person carries. This module is that definition layer — the time structure your working time runs on.
What you define
The holidays
The holiday calendars and their entries: when the operation is closed, per year, per region. The definitions your presence records are measured against and your calendar respects.
The breaks
The break definitions and schedules: when the working day rests. Break structure is data — the shift with two breaks and the shift with one are different governed shapes, not free-text variations.
The three schedule kinds
Daily work schedules — the shape of one working day: start, end, the hours. Period work schedules — the shape of a stretch: the rotation, the week pattern, with the day-level detail. Work schedules — the assembled pattern: what this person's or team's working time actually is.
Three kinds because reality has three granularities — the day, the stretch, the pattern — and each is defined as its own governed record.
The absence types, with quotas
The off-time categories your operation runs with — vacation, sick, personal, unpaid — each a typed definition. And the quota allocations: how much of each absence type each person carries — governed per-employee records, not a policy PDF with a spreadsheet beside it.
The attendance types
The categories that classify presence: on-site, remote, field, training — defined once, applied consistently to every presence record.
The schedule assignments
Which schedule applies to whom, with effective windows: the assignment that makes the structure real — hours, holidays, quotas, and types resolving to each person.
What you can do
- Define the calendar structure — holidays, breaks, the three schedule kinds, through the standard screens
- Configure absences and quotas — the types and the per-person allocations
- Assign schedules — who runs on which pattern, from when
- Manage everything in one place — one administrative surface, one set of patterns, the same list/form/detail experience as every module
Where it connects
| Target | Examples |
|---|---|
| Employees | The schedule and quota assignments per person |
| Presence records | What attendance is measured against |
| Calendar events | What the holiday definitions close |
| The readings | The time structure the wellbeing and tempo readings draw on |
Where it feeds
This is the bridge module's definition layer: the conventional HR era's time machinery — carried, governed, and feeding the new era's readings (the bridge story). Presence patterns mean something against these definitions; leave clusters read against the quotas; the tempo of the work reads against the schedules. The buyer page is the platform page; this manual is the configuration surface.
The pattern note: same four-part structure — record (define, here), do, connect, feed. The HR time manual is where the definition-layer pattern completes: a module whose entire job is governed structure — the definitions the operational modules run on.
Implementers load your operation's real time structure at adoption — holidays, schedules, quotas, as they actually run; consultants align the definitions with your employment practices.
No record is an island
Every definition here relates to the people it assigns, the presence it shapes, the calendar it closes, the readings it grounds. The time structure is the bridge between eras — held as records, governed as data.
Review the record and its context before deciding what to do next.
Presence → · Calendar → · All manuals → · The HR Bridge platform page →
Check your work
Check the applicable region, schedule and effective dates before assigning a work pattern. Review quota allocations and absence types with the responsible HR team. These definitions supply context for presence; an unusual time pattern needs investigation before it is interpreted as a cultural signal.
Available screens and actions depend on your deployment and permissions. Use this manual alongside the configured workflow and the capability demonstration for your installation.