# Promotion as a workflow: the four capabilities a level change needs

Process, read 8 Nov 2026

**The short answer.** A promotion flow needs a trigger from the promotion request field, an approval chain that runs the skip-level and the People partner in order, chosen approvers so the policy names who approves which level, and the letter signed inside the flow before the announcement. Shapes, Workday and Humaans document all four; Rippling's per-policy approver choice is partial.

A promotion is a change to three fields and one document, in an order: approvals, letter, fields on the effective date, announcement. The engine has to start from the record, route to the people the policy names, and hold the announcement until the letter is signed. Platforms with approvals but no any-field trigger run the promotion as a request outside the record and update the fields by hand.

The promotion template on this site is the eight-task plan with the checks at 30, 60 and 90 days after the effective date.

## The capabilities this process needs

- [Triggers from any field](/workflows/trigger_any_field/): 3 of 14 document it
- [Approval chains](/workflows/approval_chains/): 13 of 14 document it
- [Chosen approvers per policy](/workflows/chosen_approvers/): 6 of 14 document it
- [E-sign inside the flow](/workflows/esign_in_flow/): 12 of 14 document it

## Who can run it

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

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

- [Template: Promotion](/templates/promotion/)

**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/promotion/
