Leave & Remote
This is the working policy, not a legal document. Two ideas: request leave early enough to cover your work, and be reachable during core hours.
flowchart LR
A["Plan time off"] --> B["Request to team lead<br/>+ calendar, in advance"]
B --> C{"Impacts a<br/>commitment?"}
C -->|Yes| D["Arrange cover<br/>hand off work items"]
C -->|No| E["Approved"]
D --> E
E --> F["Mark calendar<br/>+ set chat status"]
- Request through your team lead with enough notice to arrange cover — more notice for longer leave.
- Hand off open work items before you go: reassign or note status on the board so nothing stalls silently.
- Sick / same-day: message your team lead and set your chat status; sort the formal request when you’re back.
- The company calendar is the source of truth for who’s out.
Remote
Section titled “Remote”- Remote-friendly. Be reachable during core hours and keep your chat status honest (available / focus / away).
- Keep work in the tracked channels — work items and wiki — so remote and in-office see the same picture.
- Meetings are camera-optional; being present and responsive matters more.
Core hours
Section titled “Core hours”- A daily core overlap window is when synchronous work — meetings, live review, pairing — happens. Outside it, default to async.
- Support coverage is business-hours SLA, not a 24/7 pager (see Run & Support).
- Rotations and time-zone-sensitive coverage are arranged per project by the team lead.