First 90 Days template, role, read 8 Nov 2026
The first 90 days of a finance hire, as a workflow
Before day oneDay oneWeek oneDay 30Day 60Day 90
A finance hire's onboarding is governed by access: the bank portal, the ERP, the payroll file and the board pack, each with a limit and an approver. The template makes every access a task with an approval step, so the audit log shows who granted what and when, and the leaver flow can reverse it in the same order.
The work is the close. The hire shadows one month-end, runs the next with the previous owner watching, and owns the third. The 30, 60 and 90-day checks are those three closes.
Day by day
- Day -10Send the contract and the confidentiality agreement for signature before any system access is granted (Confidentiality agreement)People team
- Day -5Request ERP, expense tool and bank portal access with the approval limits; each request approved by the CFO (Access request)Manager
- Day 0Confirm access and limits; record the grant in the audit logIT
- Day 1Hand over the month-end calendar, the chart of accounts and the open reconciliations (Close calendar)Manager
- Week 1Meet payroll, the auditors' contact and the bank relationship managerNew starter
- Day 14Shadow the first month-end closeManager
- Day 30Thirty-day review: access complete, close calendar understood, reconciliations assignedManager
- Day 45Run the second close with the previous owner reviewing each journalNew starter
- Day 60Sixty-day review: the second close signed off; the board pack section draftedManager
- Day 90Own the third close; probation decision recorded (Probation review)Manager
The checks at 30, 60 and 90 days
- Day 30
- Confidentiality agreement signed before access. Every access grant approved and logged. First close shadowed.
- Day 60
- Second close run with review. Open reconciliations cleared or dated. Board pack section drafted.
- Day 90
- Third close owned. Probation decision recorded. Access limits reviewed once.
What the template needs from the platform
- New starter and leaver runs13 of 14 document it
- Approval chains13 of 14 document it
- E-sign inside the flow12 of 14 document it
- Audit of who did what5 of 14 document it
- Date triggers (start date, anniversary, probation)7 of 14 document it
- Task views for employees13 of 14 document it
Which platforms can run it unattended
| Platform | Documented | Partial | Missing |
|---|---|---|---|
| Humaans | 6 of 6 | 0 | none |
| Rippling | 6 of 6 | 0 | none |
| Shapes | 6 of 6 | 0 | none |
| Workday | 6 of 6 | 0 | none |
| BambooHR | 5 of 6 | 1 | none |
| Personio | 5 of 6 | 0 | Audit |
| Factorial | 4 of 6 | 2 | none |
| HiBob | 4 of 6 | 2 | none |
| ADP | 4 of 6 | 1 | Audit |
| Deel | 4 of 6 | 1 | Audit |
| Paylocity | 4 of 6 | 1 | Audit |
| Lattice | 3 of 6 | 3 | none |
| Gusto | 3 of 6 | 2 | Audit |
| Sage | 3 of 6 | 2 | 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: collect signatures in order, read 8 Nov 2026
- Shapes: see who did what in the audit log, read 8 Nov 2026
Last reviewed 10 Nov 2026.