How to Reduce Onboarding Time Without Rushing New Hires

You reduce onboarding time by removing what slows people down, not by compressing what they need to learn. In practice that means three moves: finish the paperwork before day one, give every new hire goals they can observe and check, and get the unwritten judgment of your experienced people into a form a newcomer can search. Teams that only speed up the first of those usually find the ramp-up barely changes.

This guide walks through each move, shows where the hours really go, and gives you a way to measure whether the time is shrinking.

TL;DR

• Most of the delay is not training. It is paperwork, missing access and questions nobody has written down an answer to.
• Complete compliance and setup before the start date, so the first week is spent on the job itself.
• Replace vague goals like "learn the product" with observable outcomes, such as shipping one small task.
• Capture the exceptions and reasoning behind your procedures, because that is the part a new hire cannot find in a document.
• Measure time to a first real contribution, not completion of a checklist.

Table of Contents

• Where onboarding time actually goes
• Move compliance out of the first week
• Set goals a new hire can observe
• Capture the part documents miss
• Our perspective: the expert's judgment is the bottleneck
• Measure time to first contribution
• A four-to-eight-week plan
• Where Kept fits
• What to avoid
• FAQ
• Sources

Where onboarding time actually goes

Before you cut anything, find out what is in the time. When we look at slow onboarding, the hours tend to fall into four buckets:

1. Administrative work. Forms, benefits enrollment, policy acknowledgments, account requests.
2. Waiting. For a laptop, a login, a permission, a manager's calendar slot.
3. Formal training. Courses, shadowing, orientation sessions.
4. Asking around. Finding out how things are really done, usually by interrupting the same two or three people.

The first two are cheap to fix and the fourth is expensive to fix, which is why it gets ignored. The third gets the most attention and often the least improvement.

There is a reason onboarding keeps getting harder to do well. A survey report from APQC describes rising demand for onboarding, driven by shorter employee tenures and stiff competition for critical talent. If people stay for less time, every week of ramp-up costs a larger share of their tenure.

Onboarding is more than orientation

A Gallup perspective paper on creating an onboarding journey makes a point worth repeating to any manager who thinks a good first day is the goal. Preboarding, an orientation day, compliance training and team lunches are useful first steps, but on their own they are not enough. The ramp-up happens afterward, in the weeks of actual work.

Research on formal onboarding points the same way, with a caveat. A systematic review of formal onboarding and socialization covered five studies and 1,556 new professionals, mostly new nurses, and rated the methodological quality as low to moderate. Treat it as a direction, not a guarantee: onboarding that attends to role clarity and belonging, not just tasks, is what the researchers argue for.

Move compliance out of the first week

The fastest single change is also the least glamorous. Soteria's onboarding process guide argues that compliance should be finished before day one, and that role training needs dedicated time that is not eaten by administration. If a new hire is filling out tax forms on day two, you have spent their most engaged window on paperwork.

In the United States some of this has legal timing you cannot move. A DLA Piper employment guide for the US notes that employees must submit materials establishing work authorization within three days of starting employment. So the task is not to skip steps. It is to send everything you legitimately can ahead of time, and to schedule the rest into one short, protected block.

A workable split:

If you can only do one thing this quarter, make sure the laptop works and the logins are live on the first morning. Few things signal "nobody planned for you" like a new hire waiting on access.

Set goals a new hire can observe

Vague plans are a quiet source of lost time, because nobody can tell when the hire has arrived. Soteria's 90-day playbook names vagueness as the biggest pitfall of a 30-60-90 plan: goals such as "learn the product" or "meet the team" are not measurable. Its fix is to define observable outcomes, like shipping one small task or closing a first support ticket, which push the hire to apply what they know right away.

Here is how that rewrite looks for different roles:

• Support agent. Instead of "learn the ticketing system": resolve three tier-one tickets with a reviewer checking the answers by the end of week two.
• Operations coordinator. Instead of "understand the vendor process": process one vendor onboarding end to end, with the owner of the process watching.
• Engineer. Instead of "get familiar with the codebase": ship one small, reviewed change to production.
• Account manager. Instead of "meet the clients": run one renewal conversation with a colleague listening in.

Each outcome forces a question: what does this person need to know to do this? That question is the best prompt you will find for deciding what training to cut and what to write down.

For a fuller manager-side version of this, our 90-day onboarding checklist for managers lays out the weeks in order.

Capture the part documents miss

Here is where we think most onboarding programs stall. They are good at the official material: the policy, the SOP, the training deck. They are weak on what experienced people actually do when the procedure does not quite fit.

One HR guide for small businesses describes tacit knowledge as the unwritten rules of how things get done, and says high-performing teams set aside time in the first week for a knowledge transfer session. In that session a veteran maps out not just processes but the stakeholders, the decision-making nuances and the common traps of the department.

That is the right instinct. The trouble is that a single session depends on one person's memory on one afternoon. Anything they forget stays forgotten, and the next hire needs another session.

What the document holds and what the person holds

A new hire who gets only the left column will follow the procedure correctly and still make the mistakes the veteran learned to avoid. They will also ask the veteran, repeatedly, which is where the hidden time goes.

How to get the right column written down

The technique that works is closer to an investigative interview than to writing documentation. You ask about specific cases, not general rules.

1. Pick one recurring task a new hire will own within 30 days.
2. Ask the person who does it best to walk through the last time it went wrong.
3. Ask what they checked, what they ignored and why.
4. Ask what they would tell a stranger doing it for the first time.
5. Record the answer in their words, then have them review it.

Speaking is faster than writing for most people, and the reasoning survives better when nobody is trying to make it sound official. If you want a deeper walk-through of building this into a program, see our guides on what belongs in an onboarding playbook and on piloting onboarding documentation in four to eight weeks.

Our perspective: the expert's judgment is the bottleneck

We built Kept because we kept seeing the same pattern. A company invests in onboarding, polishes the checklist, buys a learning system, and the new hire still spends their first month tapping a colleague on the shoulder. The documentation exists. The knowledge that makes the documentation usable does not.

So we start from a different place. Instead of asking people to write procedures, Kept guides them through a conversation in their own words, and it asks the follow-up questions a good interviewer would: what do you do when this fails, why that threshold, what would you warn a newcomer about. The result is a structured process that carries the exceptions and the reasoning, not just the rules. New hires can then search it and get answers that cite where they came from.

We also think control matters more than most vendors admit. Capture should be opt-in, the person who contributed should be able to review what was recorded, and knowledge should be deletable. People share their judgment more freely when they know where it goes.

We will not claim a specific percentage for how much any of this shortens your ramp-up, because it depends on how much of your onboarding time is spent on questions that have written answers. That is why we suggest measuring first, as described below.

— Anthony

Measure time to first contribution

Completion of a checklist tells you the hire was processed. It does not tell you they are productive. A better measure is the time from start date to the first observable outcome you defined, such as the first resolved ticket or the first shipped change.

Track three numbers for each hire:

• Days to first observable outcome. The core measure.
• Questions that interrupted a colleague. Ask the hire to keep a simple tally in the first month, or have the team lead note them.
• Questions that had no written answer. This is your documentation backlog, sorted by how often each question repeats.

The third number is the most useful. It tells you which knowledge to capture first. We describe a similar approach for support teams in our piece on starting from the first 30 failed searches, and the logic carries over to any team that answers the same questions repeatedly.

Be careful about comparing across roles. A support agent and a field engineer will never ramp at the same pace, and averaging them hides more than it shows. Compare each role with its own earlier cohort.

A four-to-eight-week plan

You do not need to overhaul everything. A small pilot gives you evidence before you ask anyone for budget.

Weeks 1 and 2: baseline. Pick one role you hire for regularly. Record how the last two or three hires spent their first month, and list the questions they asked.

Weeks 3 and 4: fix the cheap things. Move paperwork before the start date. Make sure equipment and access are ready. Rewrite the 30-60-90 goals as observable outcomes.

Weeks 5 to 8: capture and test. Interview the two or three people the new hire will lean on most. Capture their exceptions and reasoning on the five or six tasks the hire will own first. Give the next hire access and compare against the baseline.

Our article on proving value with an AI pilot in onboarding goes through how HR can frame that pilot, and turning conversations into searchable docs covers the capture step in more detail. If you hire contractors as well, the five checks for contractor onboarding apply the same idea with a named owner for each.

Where Kept fits

If your slowest part is the fourth bucket, the asking around, that is the problem Kept is built for. Our onboarding use case shows how teams capture what their experienced people know through guided conversations, and how new hires search it. Kept has a plan for individuals and a plan for business workspaces; you can see both on the pricing page. Engineering managers can look at how we approach onboarding engineers from what the team already knows.

What to avoid

A few habits make onboarding slower while looking efficient:

• Front-loading everything. A hire cannot absorb six weeks of material in week one. Sequence it against the tasks they will actually do.
• Treating the checklist as the goal. A completed checklist and a capable hire are different things.
• Relying on one veteran. If the knowledge lives in one person's head, onboarding speed depends on their calendar.
• Skipping the human side. The review of formal onboarding cited earlier stresses socialization and role clarity. A hire who does not know whom to ask will be slow regardless of the materials.
• Documenting rules only. Procedures without exceptions produce confident mistakes.

FAQ

How long should it take to onboard a new employee?

There is no universal number, because it depends on the role. A common structure is a 90-day plan with goals at 30, 60 and 90 days, as described in Soteria's playbook. Rather than copy a benchmark, define what a productive first contribution looks like in your role and measure against your own earlier hires.

Can I quit a job during onboarding?

In most of the US, yes. Employment is generally at-will in 49 states, with Montana as the exception after a probationary period, so either side can usually end the relationship at any time. A contract or a public-policy exception can change that, so if you have signed an agreement with notice terms, read it or ask an employment attorney before you act.

What is the difference between offboarding and onboarding?

Onboarding is bringing a new hire into the organization and up to speed. Offboarding is the transition of someone who is leaving, including handing over their knowledge. The two connect: what you capture at offboarding is what the next person needs at onboarding.

How do I make the onboarding process better?

Start by finding where the time goes. Move compliance before day one, set observable goals, and capture the exceptions and reasoning your experienced people use. Then measure days to first contribution and compare each cohort with the last.

Sources

• APQC: The Onboarding Experience of Today's Workforce
• Gallup perspective: Creating an Exceptional Onboarding Journey
• Effectiveness of formal onboarding for facilitating organizational socialization: a systematic review
• Soteria: Employee Onboarding Process, 15-Step Guide
• Soteria: How to Onboard New Employees, 90-Day Playbook
• DLA Piper: Global Expansion Guide, Employment (US)
• FirstHR: New Manager Onboarding, Small Business Guide
• Recording Law: At-Will Employment by State

Recommended

• Make 90 Days Work: Employee Onboarding Checklist for Managers
• Pilot Onboarding Documentation in 4–8 Weeks with GenAI for HR
• Contractor Onboarding: Five Checks, Each With an Owner
• Onboarding Playbook: What to Put in It and How to Build One