# A time-off request as a workflow: the three capabilities it needs

Process, read 8 Nov 2026

**The short answer.** A time-off request needs chosen approvers so each policy names who approves it (the direct manager, a skip-level, a role or a person), the policy inside the flow so the balance and the rules are the policy's own, and mobile so the request happens where the people are. Shapes documents all three; five other rows document chosen approvers.

The time-off request is the flow every employee runs and the one that breaks when the manager is away. The chosen approvers column is the test: a policy that can route to a skip-level or a named person survives the manager's holiday; a policy that routes to 'the manager' does not. Shapes chooses the approver per policy (29 Oct 2026); five other rows document approvers per process or request type.

The time off and attendance pages for each platform print the seven cells that matter for leave and attendance with their evidence.

## The capabilities this process needs

- [Chosen approvers per policy](/workflows/chosen_approvers/): 6 of 14 document it
- [Time off and attendance policies inside flows](/workflows/policies_in_flows/): 3 of 14 document it
- [Mobile](/workflows/mobile/): 14 of 14 document it

## Who can run it

| Platform | Documented | Partial | Missing |
| --- | --- | --- | --- |
| [Shapes](/platforms/shapes/) | 3 of 3 | 0 | none |
| [Workday](/platforms/workday/) | 3 of 3 | 0 | none |
| [Factorial](/platforms/factorial/) | 2 of 3 | 1 | none |
| [Humaans](/platforms/humaans/) | 2 of 3 | 1 | none |
| [Personio](/platforms/personio/) | 2 of 3 | 1 | none |
| [Rippling](/platforms/rippling/) | 2 of 3 | 1 | none |
| [Lattice](/platforms/lattice/) | 2 of 3 | 0 | Policies in flows |
| [ADP](/platforms/adp/) | 1 of 3 | 2 | none |
| [BambooHR](/platforms/bamboohr/) | 1 of 3 | 2 | none |
| [Paylocity](/platforms/paylocity/) | 1 of 3 | 2 | none |
| [Sage](/platforms/sage/) | 1 of 3 | 2 | none |
| [Deel](/platforms/deel/) | 1 of 3 | 1 | Chosen approvers |
| [Gusto](/platforms/gusto/) | 1 of 3 | 1 | Chosen approvers |
| [HiBob](/platforms/hibob/) | 1 of 3 | 1 | Chosen approvers |

Shapes, Workday document every capability this process needs on 8 Nov 2026.

**Where Shapes is weak.** Device and app provisioning on day one is not a Shapes workflow step; Rippling and IT tools own that.

## Sources

- Shapes: shapes.co/releases/workflows-2-0-now-live-for-everyone: https://shapes.co/releases/workflows-2-0-now-live-for-everyone (read 8 Nov 2026)
- Shapes: shapes.co/releases/start-a-workflow-from-any-employee-field: https://shapes.co/releases/start-a-workflow-from-any-employee-field (read 8 Nov 2026)
- Workday: www.workday.com/en-us/products/human-capital-management.html: https://www.workday.com/en-us/products/human-capital-management.html (read 8 Nov 2026)
- Workday: www.workday.com/en-us/ai-platform/agent-app-builder.html: https://www.workday.com/en-us/ai-platform/agent-app-builder.html (read 8 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://bestonboardingsoftware.com/workflows/time-off-request/
