Time off requests
Person registerWho asked for what days, what was decided, and who is covering.
The dates and the decision
What an operator actually needs later is who asked for which days, what was said, and who picked the work up. That is what this holds — and it is deliberately all it holds.
No leave types, on purpose
A leave-type dropdown looks like tidy data and is a health-and-family database about named employees kept in a browser. There is not one here, and there is no field in which one could be configured.
Around it
Who is away and who is covering across a period is the away calendar. Who was actually in is the attendance log.
A record of requests and decisions. It holds no leave type, no medical or family reason, no balance and no accrual, and it decides no entitlement. Everything runs on your device.
Questions people ask
- Why is there no leave type?
- Because every list an honest one would contain — sick, medical, parental, pregnancy, bereavement, workers' compensation — is health data, family data or a protected characteristic about a named person. A dropdown is a collection instrument. This tool records the dates and the decision.
- Does it track balances or accruals?
- No. It counts no days, holds no balance, works out no accrual and decides no entitlement. What anybody is owed comes from your own policy and from the law where they work, and a figure invented here would be one somebody planned around.
- Can I record why somebody asked?
- There is an optional free-text box, with a line beside it saying what does not belong in it. If the reason is medical, or about somebody's family, leave it out — this tool is not built to hold it and you almost certainly do not need it recorded to approve some days off.
- Do two people with the same name get mixed up?
- No. Every request is stored against the person's stable id, not their name, so two people called the same thing keep two separate lists and renaming either changes nothing.