The absence number operations feels

May scheduled 7,371 worker-days and lost 231 of them to unplanned absence, a 3.1 percent rate. Vacation is not in that number, on purpose: planned time off is the benefit working, unplanned clusters are the cost, and blending them hides both.

RuleReport unplanned absence as days lost over days scheduled, by department and month. Planned time off is health; unplanned clusters are the operational signal.

Neverblend vacation into an absence rate. A team using its earned time well and a team calling in sick look identical in a blended number.

Vacation never enters the rate. Planned time is the benefit working; unplanned clusters are the operational cost.

◆ May 2026, the unplanned ratedays lost over days scheduled, the honest denominator.

Department	Scheduled worker-days	Unplanned days lost	Rate %
Sales	3,003	87	2.9
Technology Delivery	2,352	71	3.0
Support	2,016	73	3.6
All departments	7,371	231	3.1

The denominator is real: 351 workers times the 21 working days of May 2026, from the same calendar the payroll accrual counts. Support runs half a point above the company rate, and with 96 people that is the difference between absorbing absence and paying overtime to cover it. Sample values are illustrative, never client data.

◆ Planned and unplanned, kept apartthe split the blended number hides.

May 2026 absence days	Days
Vacation, planned	435
Personal days, planned	77
Sick, unplanned	198
Other unplanned	33
Absence days in May	743

Only the 231 unplanned days enter the rate above. The 512 planned days are the system working: time earned, scheduled, and covered in advance. A department where planned days trend down while unplanned trend up is burning out in plain arithmetic.

◆ The owned answertyped absence events over the working-day calendar.

Every absence day is an event row typed planned or unplanned by its absence type. The rate is a division over the shared calendar, and the same query trends it monthly, which is where the signal actually lives.

The typed event fact and the working-day calendar sit on the absence star; the rate is a division over them, trended monthly. The model page carries the schema this page quietly assumes.

Use case

Problem

Absence reporting blends vacation with sick days into one rate nobody can act on, and the operational cost of unplanned absence stays invisible.

What we build

Typed absence events split planned from unplanned, rated over headcount times the real working-day calendar, trended by department and month.

What you get

A rate operations can use: unplanned days against an honest denominator, the burnout crossover visible in the planned-versus-unplanned trend, and cover costs traceable.

Is your absence rate measuring health or hiding it?

We build the typed absence model that keeps planned and unplanned apart.

Talk to us

Terms on this page

unplanned absence: Sick and other unscheduled days; the operational signal.
planned absence: Vacation and personal days scheduled in advance; the system working.
scheduled worker-days: Headcount times working days; the honest denominator.
absence rate: Unplanned days lost over scheduled worker-days.
cover cost: Overtime and backfill caused by unplanned gaps.
burnout crossover: Planned days falling while unplanned days rise.