Employee onboarding process: a step-by-step guide to onboarding new hires

You found the right person, signed the contract, and then the first two weeks went sideways. The laptop wasn’t ordered, payroll had the wrong details, and the first-day agenda changed at the last minute because someone was on vacation.

None of that is the new hire’s fault. It traces back to the employee onboarding process behind them, and how well each team hands off to the next.

Getting this right matters more when hiring is expensive, and roles stay open for a while. Finding and hiring a replacement costs real time and money. When a good hire slips away in the first month, you’re back at the start of that hard search.

This guide covers what the onboarding process is. You’ll also see who owns what, where it tends to break, how to measure whether it’s working, and how to make it repeatable as you grow.

Key takeaways

• Onboarding runs from offer acceptance until a new hire can work confidently on their own, well beyond day one.

• It’s a cross-functional process across People Ops, managers, IT, payroll, and finance, with one end-to-end owner who keeps the timing on track.

• Most onboarding fails at the handoffs between teams.

• Accurate employee data is the foundation because early errors ripple through payroll, benefits, IT, and legal documents.

• Settle ownership and your source of truth, document the workflow, and only then automate it.

• Measure both process completion and new-hire outcomes. Finishing every task on a checklist doesn’t necessarily mean someone is clear on their role or settling in well.

What is the employee onboarding process?

It starts before day one and often runs through the first year.

The most intensive ramp-up often happens during the first 90 days, while some companies continue structured onboarding check-ins for six months or through the first year.

People sometimes use onboarding and orientation to mean the same thing, but they’re different. Orientation is the day-one introduction: paperwork, a welcome, and first meetings. Onboarding is the longer process around it that gets someone genuinely up to speed.

A useful test of success comes from Joanna Augustyn, People Operations Specialist at Tellent

If a new hire spends week one correcting their own data or chasing a login, the process has already put work back on them.

Why a structured onboarding process matters

A structured onboarding process pays off in ways a small HR team feels quickly. It gives new hires the role clarity, confidence, relationships, and practical support they need to settle in and start contributing.

For the business, good onboarding also makes the experience more consistent from one new hire to the next, whoever is available that week. Managers know what they’re responsible for, HR can see whether tasks have happened, and new hires don’t have to discover missing steps themselves.

There’s a compliance angle too. Pre-boarding is often when you collect employment information and documents needed for payroll, employment administration, or local legal requirements.

For EU employees, collect only the personal data you need for a defined purpose, explain how you'll use it, and control who can access it. Getting those steps right before day one reduces last-minute gaps without collecting unnecessary information.

The cost of getting it wrong is real. The first weeks shape a new hire’s first experience of how the company actually operates. If basic promises, access, expectations, or responsibilities are unclear from the start, the problem goes beyond a bad first day.

The employee onboarding process steps: from offer to first year

There’s no single correct number of onboarding stages. A practical way to structure the process is around five periods: pre-boarding, day one, the first week, the first 90 days, and the transition into longer-term development.

What matters more than the number of stages is that each one has a clear owner, a trigger that starts it, and a definition of what “done” looks like.

1. Before day one: pre-boarding

Owner: People Ops (with IT and the manager on their own tasks).

Trigger: the candidate accepts the offer and is marked as joining.

Done when: the contract is signed and data and documents are collected. Payroll, benefits, and IT are then set up, and an agenda email goes out three days before the start date.

Pre-boarding covers everything between offer acceptance and the start date. That includes contract preparation, collecting the employee data and documents needed for the role and country, payroll and benefits setup, and IT provisioning. For EU employees, GDPR applies during pre-boarding too: collect only the data you need for a defined purpose and make it available only to the people who need access.

Even after a strong recruitment process, this gap is where things can quietly go wrong.

Having new hires enter their own information reduces guesswork and rekeying. It's also where you collect the details you'll want if day one doesn't go to plan.

A good pre-boarding step lets them enter the information you need and upload relevant documents before they have a company login, so they don’t have to enter the same data again later.

2. The first day: orientation

Owner: the manager (team side) with People Ops (logistics). Trigger: the new hire's start date.

Done when: logins, equipment, and access work, the team introductions are made, and a buddy or point of contact is assigned.

Day one is more about the experience than the information. Welcome the new hire, walk through the agenda, and confirm their logins, equipment, and access actually work.

Introduce them to their manager and team, give a workplace or digital tour, and cover the essentials of how things run.

The manager should own the team-side agenda from the start. Assign a buddy or named point of contact so questions have somewhere to go.

3. The first week

Owner: the manager, with the buddy supporting.

Trigger: the end of day one.

Done when: the new hire has met close colleagues and key stakeholders, has had regular check-ins, and knows the first-week priorities.

Use the first week for relationships, orientation, and a first introduction to the work. Schedule short meetings with close colleagues and key stakeholders, and hold regular manager check-ins to answer questions and set first-week priorities.

Give people time to learn the tools and workflows they’ll use daily, and invite them into the meetings and channels where the team actually operates.

4. The first 90 days

Owner: the manager.

Trigger: the end of the first week.

Done when: the new hire is working with increasing independence against real role goals, tracked through check-ins.

The first 90 days move a new hire from learning to contributing. A 30-60-90-day plan is a common way to structure it. The new hire learns the role and tools in the first month, takes on more in the second, and moves toward working independently by the third.

A plan alone only sets the shape. Progress becomes visible when the manager runs check-ins tied to real role goals, so support arrives before someone gets stuck.

5. The end of the first year

Owner: the manager, with People Ops supporting the transition.

Trigger: the end of the intensive ramp-up period.

Done when: role clarity and progress are reviewed, onboarding connects to development and performance, and the new hire’s feedback is captured.

By this point, onboarding should gradually give way to normal development and performance management. Companies that continue structured onboarding for six or twelve months can use a later check-in to review role clarity, progress, development needs, and whether any gaps from the onboarding period remain.

This is also when you ask the new hire what worked and what didn’t. That feedback is the raw material for improving onboarding for the next person.

Who owns the employee onboarding process?

Here’s the framing that changes how the whole thing runs: onboarding is a business process that HR coordinates, and several teams deliver it together.

People Ops will usually coordinate the overall onboarding process, but that doesn’t mean People Ops should complete every task. One person needs accountability for the end-to-end sequence and timing; each participating team then owns its part of the process.

That coordination needs a single point of accountability. Someone has to own the sequence and timing end to end, without personally doing every task.

That framing extends past the point of hire, too. As Marieke mentions, "We try to have the Talent Acquisition Specialist, the People Operations Specialist, and the HR Business Partner work together to keep the entire onboarding experience positive. The Talent Acquisition Specialist also remains connected after signing the contract, because in the end that person is going to have a whole career in the organization."

From there, each team owns its part. The table below shows a practical split.

With ownership set this way, People Ops keeps the workflow moving while everyone else knows exactly which tasks are theirs.

Where the onboarding process breaks down

When onboarding goes wrong, it usually traces to a handoff between teams that didn’t happen on time. Often every team did its own part well.

Delays are the usual culprit, and they trace back to a trigger that fired too late.

The exact lead time depends on your company and setup. In Joanna’s experience, for example, IT needs around two weeks to prepare equipment: ""Delays are quite common: that’s the main pain point. We have expected timeframes for things to happen. For example, IT needs to know at least two weeks before the start date that someone’s starting, so they can order equipment and prepare the laptop."

Two other failure modes show up often. The first is inconsistent information, like a first-day agenda that’s wrong because the person who set it is away.

The second is over-reliance on one individual, so the process stalls the moment they take leave. Document and share a workflow so it still runs when one person is unavailable.

How to build a repeatable onboarding workflow

Once you can see where onboarding breaks, the fix follows a set order: get the process and data right first, then standardize it, then automate. Rushing to a tool before the process is settled just makes a shaky process run faster.

A useful order is:

1. Fix ownership and your source of truth.

2. Document the workflow and handoffs.

3. Standardize the steps that should happen every time.

4. Automate the stable process.

Get the data and ownership right first

Employee data sits under everything else in onboarding, which is why early accuracy is worth the effort.

Give each piece of employee information a single source of truth, so downstream teams can trust it. The HRIS usually holds core employee data, while payroll keeps its own calculations and records. Letting new hires enter their own details during pre-boarding also reduces assumptions. As Marieke says, "You can also see the employee is truly in control. So there’s no way for us to make mistakes or make assumptions."

Document it, then standardize and automate

Write the workflow down so it becomes common knowledge across the team. Turn that into a checklist or template. Only then add automation: reminders, task assignment, and integrations between your ATS, HRIS, and payroll that stop the same data being typed in twice.

The order matters, and it’s worth being honest about why.

When the workflow is defined, automation can send the right tasks to the right people at the right time. That takes the process off any one person’s memory.

Build it to scale with you

The right time to add structure is before you feel the pain. As headcount climbs, manual onboarding turns into a real drag on a small team.

Marieke sees the administrative squeeze becoming particularly noticeable around 20 to 50 employees, when HR may still be a one-person function. That isn’t a universal headcount threshold, but it illustrates the pattern: as hiring volume and complexity rise, automating routine administration becomes more valuable.

Later, as more managers join the company, self-service and clearer ownership help HR avoid becoming the bottleneck for every onboarding decision or task.

How to measure whether your onboarding process works

A completed onboarding checklist tells you that tasks happened. It doesn’t necessarily tell you whether the new hire is actually settling into the role. A useful measurement approach looks at both process execution and employee outcomes.

Useful signals include:

• Process completion: Were equipment, accounts, payroll setup, documents, introductions, and other required tasks completed on time?

• New-hire feedback: Did the employee have the information, tools, context, and support they needed at each stage?

• Role clarity: Does the new hire understand what they are responsible for and how success in the role will be judged?

• Progress against early goals: Is the employee making the expected progress against their first 30-, 60-, or 90-day objectives?

• Time to independent contribution: How long does it take before someone can handle the core responsibilities of the role with normal levels of support?

• Early retention: Are patterns in early departures pointing to problems in hiring, expectations, management, or onboarding?

Look for patterns rather than treating one metric as proof that onboarding is working or failing. A late laptop is a process problem. Repeatedly low role clarity may point to a manager, job-design, or training problem. New-hire feedback helps you tell the difference.

How Tellent supports the employee onboarding process

Onboarding depends on collecting sensitive data — contracts, personal details, documents — before day one and handling it correctly across every team involved. Tellent HR is built with that in mind: it centralizes employee data as a single source of truth and connects the steps around a new joiner, so the same information doesn't get re-entered or mishandled as it moves between people ops, IT, and payroll.

Its Journeys feature turns pre-boarding and onboarding into reusable workflows, with tasks assigned to owners and deadlines, so nothing waits on one person's memory.

Because hiring and HR data connect, a new hire enters their details once, and those details flow where they're needed—instead of being retyped into a separate system for performance, payroll, or reporting.

Next steps

Before you change any tools, map your current process and mark every point where one team hands off to another. Those handoffs are the best places to inspect first for process improvements.

Then run a short self-check. Who owns each stage from offer through the end of onboarding? How much lead time does IT actually get? Is the whole thing written down somewhere a colleague could pick up if you were away?

Then check the new hire’s side of the process. Do they know what happens next, who to ask for help, what is expected in their first weeks, and how their progress will be reviewed? A workflow can run perfectly on paper and still leave the employee confused.

To close the gaps you find, start from a free onboarding checklist and adapt it to your teams.

Building an onboarding process that lasts

A dependable onboarding process comes down to a few decisions made in the right order, and then it mostly runs itself. Once you have ownership, a single source of truth, and a written workflow in place, the payoff shows up when you test it. That’s during busy hiring weeks, when the process owner is on leave, and as headcount grows past what one person can carry by hand.

But repeatability is only half the test. The other half is whether the new hire gets working tools, clear expectations, useful relationships, and enough context to contribute confidently. The best onboarding process delivers both: a workflow the business can run reliably and an experience that helps the employee settle into the role.

That’s the real goal: a process a colleague could pick up cold and still get a new hire off to a good start.

If you want one place to hold employee data and run these workflows, see how Tellent HR supports onboarding from pre-boarding through the transition into normal people processes. You can also book a demo to walk through it with your own process in mind.