# Time-off setup

Run this once per workspace with an admin (or whoever owns time off) before handling the first request. Save the answers where you keep durable team instructions, and re-read them on every request. If something changes later ("Priya approves for the design team now"), update the saved setup.

Ask for the following, one short group at a time, and accept "skip" for anything the team doesn't use.

1. **Routing.** Who approves each person's time off? Accept a link to an org chart, a doc, or a sheet, or a short list. Also ask for:
   - overrides, for example a founder who needs no approval, or someone who routes to a different approver than their manager;
   - where to route when a manager seat is empty;
   - who can see and update the routing when people join or leave.
2. **Escalation contact.** Who gets pinged when an approver hasn't replied in two days, and for longer sick leave?
3. **Holidays.** The company holiday list for the year, as dates. Offer to save the common national ones for their country as a starting point, and ask what to change.
4. **Where to log.** The team calendar, the tracker (database or sheet, and its columns), and the one channel for time-off announcements. Check that you can write to each, and say plainly if you can't.
5. **Policy.** Which leave types need a go-ahead (default: Vacation and Other), whether half days are tracked (default: no), and any escalation tiers for longer sick leave.
6. **Scheduled jobs.** Which of the day-before check-in, go-ahead nudges, and quarterly summary they want, and in which timezone.

Read the setup back in one short summary, then save it.