# An attendance policy as a workflow: the three capabilities it needs

Process, read 8 Nov 2026

**The short answer.** An attendance policy flow needs the policy inside the flow so office days and working time rules are assigned as a step, date triggers so the policy starts on the start date or the move date, and task views so the employee sees what it asks of them. Shapes documents all three; Workday documents time and absence policies in processes.

Attendance in hybrid work is a policy per office and per role, and the flow that assigns it is the same one that assigns the holiday calendar. The map's policies-in-flows column is yes on Shapes, Rippling and Workday; on nine rows the policies exist and are not steps, which means a person assigns them after the flow has run.

The guide on attendance policies that survive hybrid work sets out the policy shape; the time off and attendance pages print each platform's cells.

## The capabilities this process needs

- [Time off and attendance policies inside flows](/workflows/policies_in_flows/): 3 of 14 document it
- [Date triggers (start date, anniversary, probation)](/workflows/date_triggers/): 7 of 14 document it
- [Task views for employees](/workflows/task_views/): 13 of 14 document it

## Who can run it

| Platform | Documented | Partial | Missing |
| --- | --- | --- | --- |
| [Rippling](/platforms/rippling/) | 3 of 3 | 0 | none |
| [Shapes](/platforms/shapes/) | 3 of 3 | 0 | none |
| [Workday](/platforms/workday/) | 3 of 3 | 0 | none |
| [Humaans](/platforms/humaans/) | 2 of 3 | 1 | none |
| [Personio](/platforms/personio/) | 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 |
| [Deel](/platforms/deel/) | 1 of 3 | 2 | none |
| [Factorial](/platforms/factorial/) | 1 of 3 | 2 | none |
| [Gusto](/platforms/gusto/) | 1 of 3 | 2 | none |
| [HiBob](/platforms/hibob/) | 1 of 3 | 2 | none |
| [Paylocity](/platforms/paylocity/) | 1 of 3 | 2 | none |
| [Sage](/platforms/sage/) | 1 of 3 | 2 | none |

Rippling, 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

- Rippling: www.rippling.com/platform/automations: https://www.rippling.com/platform/automations (read 8 Nov 2026)
- Rippling: www.rippling.com/platform/policies: https://www.rippling.com/platform/policies (read 8 Nov 2026)
- 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/attendance-policy/
