# The promotion flow: from the manager's request to the new title on the payslip, as a workflow

First 90 Days template, process, read 8 Nov 2026

**The short answer.** Eight tasks from request to effective date: the manager's case written against the level framework, approval by the skip-level and the People partner in order, the compensation change approved within the band, the letter signed, the title, level and pay fields updated on the effective date, and the announcement after the letter. Three owners, three checks.

Before day one / Day one / Week one / Day 30 / Day 60 / Day 90

A promotion is a change to three fields and one document, and the order matters: the approvals first, the letter second, the fields on the effective date, the announcement last. The template runs from a promotion request field on the profile, so the manager's request starts the flow and the approvals route to the people the policy names.

The 30, 60 and 90-day checks after the effective date are the ones that show whether the promotion changed the work: the new responsibilities written down, the first review at the new level, the pay change visible on the payslip.

## Day by day

- Day 0: Manager sets the promotion request field with the proposed level and effective date; the flow starts [Manager]
- Day 1: Case written against the level framework with the evidence from the last two reviews (Promotion case) [Manager]
- Day 3: Skip-level approval, then the People partner's approval, in order [Skip-level manager]
- Day 5: Compensation change proposed within the band for the new level; approved by Finance (Compensation change) [People team]
- Day 7: Promotion letter sent for signature: company first, then the employee (Promotion letter) [People team]
- Effective date: Title, level and pay fields updated; payroll informed; the audit log records the change [People team]
- Effective date: Announcement sent after the letter is signed [Manager]
- Effective +90: First review at the new level recorded (Review) [Manager]

## The checks at 30, 60 and 90 days

- **Day 30:** Approvals recorded in order. Letter signed before the announcement. Fields updated on the effective date.
- **Day 60:** Pay change visible on the first payslip. New responsibilities written down. Audit log shows who changed each field.
- **Day 90:** First review at the new level recorded. Every task closed by its owner. Band check passed.

## What the template needs from the platform

- [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
- [Sign in order](/workflows/sign_in_order/): 1 of 14 document it
- [Audit of who did what](/workflows/audit_who_did_what/): 5 of 14 document it

## Which platforms can run it unattended

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

Shapes can run every step without a person building around a gap, on the map read 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: start a workflow from any employee field: https://shapes.co/releases/start-a-workflow-from-any-employee-field (read 8 Nov 2026)
- Shapes: collect signatures in order: https://shapes.co/releases/collect-signatures-in-order (read 8 Nov 2026)
- Shapes: compensation: https://shapes.co/product/compensation (read 8 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://bestonboardingsoftware.com/templates/promotion/
