An employee onboarding workflow: the steps, the approvals and who does what

SynaptaGrid7 min read

#workflow#onboarding

In short

An employee onboarding workflow is the set of steps between an accepted offer and a new person’s first day: confirming the start, approving what they get, setting it up, and checking it worked. Most onboarding problems are hand-off problems. IT does not know the start date, the laptop is ordered before anyone approves it, or nobody checks the first day. A good workflow names one owner per step, puts the approvals before the spending, and ends with a check that someone actually looks at. We built a small version in our own test workspace and ran it from start to finish, and we describe what it shows and what it does not.

What an onboarding workflow is

Onboarding is everything that has to happen so a new person can start work: the offer is confirmed, the manager says what equipment and access the role needs, IT creates the accounts and prepares the laptop, and someone checks the first day went well. A workflow writes those steps down, assigns each to a person or a team, and keeps track of where each new hire stands.

Without one, onboarding runs on email and memory. It works until two people start in the same week, or someone is on leave when their step comes up.

The version we built

Four decisions by people, one branch for an offer that is withdrawn, and a closing step that records the result.

The steps to include, and who owns each

Confirm the start
HR confirms the offer is accepted and the date is fixed. Everything after depends on this, and it is also where an offer that falls through should end the process.
Approve before you spend
The hiring manager approves the equipment and access for the role before IT orders or creates anything. Approving after the order means paying for the mistake.
Set up
IT creates accounts, prepares the laptop and gives the right access. One owner, with the approved list in front of them.
Welcome
Someone tells the new person where to be, when, and who to ask for. Add it as its own step if it is often forgotten.
Check day one
The manager confirms the person has what they need. This is the step most processes lack, and the one that catches the first-day failures.
Record the result
The workflow ends with a written result, so you can see how many onboardings finished and how many stalled.

Where approvals belong

Put an approval wherever a mistake is expensive or hard to undo. In onboarding that is the equipment and access list: hardware costs money, and access to systems is a security decision. Starting the process, setting things up and checking day one are tasks, not approvals, so a person marks them done rather than approving them.

Decide who approves by role, such as the hiring manager, rather than by name. People change jobs, and a process that names an individual stops working the day they move.

The old way and the new way

The table compares onboarding run on email with onboarding run as a workflow.

Who knows the start date
The old way: Whoever was copied on the email
The new way: Every step reads it from the same place
Approvals
The old way: A reply somewhere in a thread
The new way: A recorded decision at a named step
Where a new hire stands
The old way: Ask around
The new way: Open the run and see the current step
An offer that falls through
The old way: Someone remembers to cancel the laptop
The new way: The process ends at the first step
Judgement
The old way: Still the manager’s and IT’s
The new way: Still theirs: what the role needs, what is safe to grant

How we decided

We built the version in the diagram in our own test workspace in SynaptaGrid Automation and ran it from the first step to the last in November. It has four steps where a person decides, one branch that ends the process when the offer is withdrawn, and a closing step that records the result. The run finished with every step completed, and the run page shows the status and the time each step took. We also saved the workflow as a template in that workspace.

We chose approve-before-spend and a check on day one because those are the places the usual process fails. The choice of steps is ours and a judgement; it is not a standard.

Four limits, so this guide does not claim more than the run showed. All four steps were assigned to one test account, so the run shows the sequence and the branching, not hand-offs between different people. We did not connect the workflow to an HR or IT system, so nothing was created in a real account. We did not test reminders or notifications when a step waits too long. And the template carries that one test account as the assignee: to reuse it you would change each step to a role, which we did not do.

Standards and accepted practice behind this

These are the practices the guide rests on. We align with them. This page does not claim a certification.

Segregation of duties
The person who requests access is not the person who approves it, and the person who approves it is not the person who sets it up.
Source: NIST glossary: separation of duty (opens in a new tab)
Least privilege
Grant the access the role needs on day one, and add more when someone asks, not the other way round.
Source: NIST glossary: least privilege (opens in a new tab)
BPMN
The standard notation for drawing a process. The diagram above is a plain flowchart, and a BPMN diagram of the same steps would show the same decisions.
Source: OMG: BPMN 2.0 specification (opens in a new tab)
A recorded decision
An approval that is kept with who made it and when can be checked later; an approval in an email thread usually cannot.

Where SynaptaGrid fits

SynaptaGrid Automation lets you write the steps as a workflow, assign each decision to a person, and see where every run stands. You can start from the version above, change the steps to match how your company onboards, and keep the result as a template for the next hire.

Check the limits above before you rely on it: whether each step is assigned to a role rather than a person, whether anything needs to reach your HR or IT systems, and who should be reminded when a step waits.

Frequently asked questions

What steps should an employee onboarding workflow include?
Confirming the start date, approving equipment and access, setting up accounts and equipment, welcoming the new person, checking the first day, and recording the result.
Who should approve equipment and access for a new hire?
Usually the hiring manager, decided by role rather than by name, before IT orders or creates anything.
How do I handle an offer that is withdrawn?
End the process at the first step. Anything set up after that is wasted, and a branch at the start prevents it.
Can I reuse an onboarding workflow for every hire?
Yes, if you save it as a template and assign each step to a role. A template that names one person has to be edited first.
Share

SynaptaGrid

Build your onboarding steps

Start with the six steps above in a test workspace and run one hire through before you use it for real.