Book and cancel on behalf of your team
Sick calls, pre-agreed holidays, new joiners: pick the person on the form or drag on their row — instantly approved, clearly attributed.
Sometimes the right person to click isn't the person going away: a cook calls in sick, a teammate on a ladder asks you to "just book it", a new joiner hasn't logged in yet. Approvers can book and cancel on behalf of their people — same rules, clear attribution.
Who can do it
Admins for anyone; managers for the departments they approve. If you can decide someone's requests, you can book for them.
Book for someone
- Open the booking form (button, or drag on their row on the wall chart — the dates come pre-picked).
- Pick the person in the "For whom" selector at the top of the form.
- Proceed as usual: type, dates, note. The live math shows their allowance, not yours, and their conflicts.
A booking you make for someone is approved on the spot — you're the approver; asking yourself would be theatre. The person is notified, and the timeline records that you created it.
Cancel for someone
Open their booking and cancel it — the form asks for a note so the timeline says why ("storm closed the venue, moved everyone's week"). Days return to their allowance; their synced calendars clean up; they're notified.
Where it shines
- Sick calls — the person phones, you book their sick leave while the coffee brews.
- Pre-agreed holidays — the summer plan settled in a meeting goes onto the chart in five minutes, one drag per person.
- New joiners — leave agreed at hiring is booked before their first login.
Boundaries worth keeping
- Everything is attributed: the timeline separates "created by" and "for". No ghost bookings.
- The same limits bind you: date locks, absence caps, their remaining allowance. The form refuses for them exactly as it would for you.
- Use it for service, not surveillance — booking someone's holiday for them without asking is a conversation, not a feature.