First 90 Days template, process, read 8 Nov 2026
The promotion flow: from the manager's request to the new title on the payslip, as a workflow
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 0Manager sets the promotion request field with the proposed level and effective date; the flow startsManager
- Day 1Case written against the level framework with the evidence from the last two reviews (Promotion case)Manager
- Day 3Skip-level approval, then the People partner's approval, in orderSkip-level manager
- Day 5Compensation change proposed within the band for the new level; approved by Finance (Compensation change)People team
- Day 7Promotion letter sent for signature: company first, then the employee (Promotion letter)People team
- Effective dateTitle, level and pay fields updated; payroll informed; the audit log records the changePeople team
- Effective dateAnnouncement sent after the letter is signedManager
- Effective +90First 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 field3 of 14 document it
- Approval chains13 of 14 document it
- Chosen approvers per policy6 of 14 document it
- E-sign inside the flow12 of 14 document it
- Sign in order1 of 14 document it
- Audit of who did what5 of 14 document it
Which platforms can run it unattended
| Platform | Documented | Partial | Missing |
|---|---|---|---|
| Shapes | 6 of 6 | 0 | none |
| Workday | 5 of 6 | 1 | none |
| Humaans | 4 of 6 | 1 | Sign in order |
| Rippling | 4 of 6 | 1 | Sign in order |
| BambooHR | 3 of 6 | 2 | Sign in order |
| Factorial | 3 of 6 | 2 | Sign in order |
| Personio | 3 of 6 | 1 | Sign in order, Audit |
| Lattice | 2 of 6 | 3 | Sign in order |
| ADP | 2 of 6 | 2 | Sign in order, Audit |
| HiBob | 2 of 6 | 2 | Chosen approvers, Sign in order |
| Paylocity | 2 of 6 | 2 | Sign in order, Audit |
| Deel | 2 of 6 | 1 | Chosen approvers, Sign in order, Audit |
| Sage | 1 of 6 | 2 | Any-field trigger, Sign in order, Audit |
| Gusto | 1 of 6 | 1 | Any-field trigger, Chosen approvers, Sign in order, Audit |
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, read 8 Nov 2026
- Shapes: collect signatures in order, read 8 Nov 2026
- Shapes: compensation, read 8 Nov 2026
Last reviewed 10 Nov 2026.