Request and manage time off

Open Team → Time off on web or mobile. Staff see their own requests and time off affecting their calendar. Owners and managers see requests awaiting review, upcoming approved and directly added time off, and history.

Request time off

Staff can request an all-day date range or part of one day. Choose a scheduling reason and add an optional private note, then preview and submit.

A Pending request does not change availability. Keep the request open until the app confirms submission. If preview or submission fails, the draft remains saved so you can retry without re-entering it. Reusing the same saved draft does not create a second request.

Review a request

Owners and managers open Pending, select a request, and review the current booking conflicts. To approve, choose one current action for every affected booking:

• Keep leaves the booking on the calendar.
• Reassign is available only when one eligible replacement can deliver the booking.
• Cancel and notify uses the business-caused cancellation flow, including the applicable full refund and customer notification.

Approval checks the request and conflicts again. If either changed, refresh the detail and review the new conflict list. Obsolete choices are cleared rather than applied to a different booking set. Declining requires an explanation that the requester can see.

Recover an approved request

Approval creates the time-off calendar closure even if a later booking action fails. The request remains Approved and the failed action appears as needing attention.

An owner or manager can open the request and choose Retry. Retry checks authority, the booking, replacement eligibility, and current scheduling again. It does not create another closure or repeat an action that already succeeded.

To remove approved time off, use Cancel approved time off from the request. Do not delete its calendar block directly. Selecting a request-owned block on a compatible app shows Manage time off; older app versions fail closed and direct you to Time off.

Notifications and privacy

New requests, decisions, cancellations, and unresolved booking actions appear in Activity and may send a native push according to schedule-notification preferences and quiet hours. Activity links open the durable request.

The requester and authorised owners or managers can see the request type, note, decision explanation, and relevant booking-conflict detail. Other staff and customers see only generic unavailability. Telemetry does not include notes, leave reasons, customer identifiers, or request identifiers.

If Time off is unavailable

Update to a compatible app or use the web Time off route. Disabling a client entry does not delete request history or approved closures. After requests exist, recovery uses a compatible forward fix and the request’s retry actions; it does not roll back or remove the durable records.