DirectoryTime off
Asked for, decided, counted. Employees request from a seat you don’t pay for, every decision carries who made it and why, and the balance is accrued minus used, with nothing clever happening in between.
They ask for it themselves. From a seat you don’t pay for.
They fill in the request themselves, from their own seat, not you typing it in after the fact.
- Four kinds: vacation, sick, personal and unpaid
- A date range, and the hours it actually costs
- A reason, if the person wants to give one
- Requested by the employee, from a seat you don’t pay for
- Visible on their own record, in their own tab
Every decision has a name on it. And room for a reason.
A decision can’t be saved without a name attached to it, which is what keeps the queue honestly answerable.
- Approved, rejected or cancelled, never just “handled”
- The decision records who made it, and when
- And a note, so “no” comes with a reason attached
- A decision cannot be saved without the name of the person who made it
- Which means the queue can always be answered honestly
Balances you can check by hand. Accrued, minus used.
Per person, per type, and nothing else in the arithmetic. It is a deliberately small model, and small is what makes it auditable.
- Accrued and used, per person, per type
- The balance is the subtraction: nothing hidden in it
- Simple on purpose, and simple in a way you can audit
What isn’t here. Better read now than found out later.
No team calendar yet
You can see the queue and each person’s record, but there is no team-wide calendar with conflict highlights. It is a known gap, waiting on enough approved volume to be worth building well.
No accrual engine
Balances are accrued hours minus used hours, entered by you. Accrual rules, fiscal-year boundaries, carryover and blackout dates are not in this version.
No leave of absence
The four types cover ordinary time off. A long-term leave has no flow of its own, and the status that would carry it is defined but not yet working.
The queue, answerable
Every request with its dates, its hours and its status, and the pending ones sitting where somebody will actually see them.
Time off is one tab. The rest of the file is next door.
No. Self-service is free: every employee gets their profile, their documents and their own time-off requests without a seat. Seats are for the people running HR.
Not yet, and we would rather say so here than have you discover it. Today you get the request queue, each person’s record and their balances; a team-wide calendar with conflict highlights is a known gap.
Accrued hours minus used hours, per person per type. That is the entire model. There is no accrual engine: no monthly rules, no fiscal-year boundary, no carryover, no blackout dates. It is deliberately simple in this version, and simple in a way you can check by hand.
A decision always records who made it. A note is where the reasoning goes, and it matters most on the ones you reject. Nothing can be marked decided without the name of the person who decided it, so the queue can always be answered honestly.
Yes. Cancelled is one of the four states, and it is told apart from rejected. Somebody changing their plans and a manager saying no are different things, and the record keeps them different.
No. The hours on a request are the hours you put on it. There is no statutory-holiday calendar doing arithmetic behind your back, which also means nothing to be wrong about across provinces.