Why does onboarding slip?
Onboarding slips because it is a checklist with many owners and no single person watching it. Access is owed by IT, equipment by operations, paperwork by HR, and the first-week plan by the manager, and each of them has other work. The new hire arrives to find something missing.
The problem is coordination rather than intent. A Digital FTE whose job is to watch the checklist and chase the owners fixes the coordination without adding a person to do it.
What does the Digital FTE own?
The Digital FTE owns the onboarding checklist from offer acceptance to the end of the first month. It raises the account and access requests in your connected systems, tracks equipment and paperwork steps, drafts the first-week schedule for the manager to approve, and sends reminders to whoever owes an overdue step.
Reminders start as drafts for approval and can earn autonomy once the pattern is established, because a reminder to a colleague about an overdue checklist item is low-risk. Anything addressed to the new hire about their role or terms stays gated.
- Access and account requests raised in connected systems
- Equipment and paperwork tracked with owners and due dates
- First-week schedule drafted for manager approval
- Reminders to step owners, autonomy earned per pattern
What does the manager see?
The manager sees, in the morning brief, the state of every new hire's onboarding: steps completed, steps overdue and who owes them, and anything waiting on the manager's own approval such as the first-week schedule. Nothing is discovered on the new hire's first day.
The new hire's own view, if you choose to share one, shows what is ready and what is coming, which reduces the anxious first-morning email.
What stays with people?
The welcome stays with people. The first conversation with the manager, the introductions to the team, the explanation of how things really work here, and the check-ins in the first weeks are the parts of onboarding that build belonging, and a Digital FTE does not do them.
What the FTE does is make sure the manager is free to do them, rather than spending the new hire's first day chasing a laptop.
How do you measure it?
Measure onboarding by the share of checklist steps complete before day one, the number of overdue steps per new hire, and the time to the first productive week as the manager judges it. Record the baseline from recent hires before starting.
The diagnostic mission can answer why is onboarding slow with ranked hypotheses from the checklist data, such as one system whose access requests always lag, each with evidence, so the fix is targeted rather than general.
What does a new hire's onboarding look like in the manager's brief?
In the manager's morning brief a new hire's onboarding appears as a short status block: steps complete, steps due this week with their owners, steps overdue with who owes them and when the last reminder went, and anything waiting on the manager's own approval, such as the first-week schedule or a message to the new hire. The Digital FTE has already raised the access requests in connected systems and sent the approved reminders to colleagues who owe a step.
The block is the same for every new hire, so a manager onboarding three people sees three blocks in one brief rather than three spreadsheets. Reminders to colleagues about checklist items start gated and can earn autonomy once the approval record shows they are routinely approved unchanged; messages to the new hire about their role or terms stay gated. When a step is chronically late across many hires, the onboarding diagnostic mission names the system or owner involved with evidence, and the fix is made once rather than chased each time.
Record the baseline from the last few hires before the first checklist runs: steps complete before day one, overdue steps per hire, and the systems whose access requests lagged most. Two cycles later the same numbers, read from the FTE's Targets tab with the evidence per hire, are the honest comparison, and the lagging system is usually the first fix the diagnostic names.