How to Calculate Time to Hire (Formula + Benchmarks)

March 10, 2026
Min Read time

We regularly meet HR teams confidently reporting a time to hire metric that turns out to measure something slightly different from what they think — or something different from what the team next to them is measuring. This article covers exactly how time to hire is calculated, how the formula differs from time to fill, what counts as a good time to hire metric, and the definition questions you need to answer before any of your numbers mean anything.

Table of Contents

Let's start with a confession.

Time to hire is one of the most widely tracked metrics in recruitment. It's on dashboards everywhere. Hiring managers ask about it. Leadership teams report it to boards. And a surprising number of the people tracking it are calculating it differently from the people sitting next to them.

Same metric. Different definitions. Different start dates. Different interpretations of what "hired" actually means. And therefore different numbers that are confidently presented as if they mean the same thing.

This matters more than it might seem. If you're benchmarking your time to hire against industry data, but your calculation starts from a different point than the benchmark does, you're not comparing like with like. If two teams in the same organisation are measuring differently, you can't compare their performance. And if your definition shifts — even slightly — between reporting periods, your trend data becomes meaningless.

So before we get into what a good time to hire metric looks like, let's get the formula right. All of it. Including the bits that seem obvious but turn out not to be.


The Time to Hire Formula

The basic formula is straightforward.

Time to Hire = Date of Offer Acceptance − Date Candidate Entered Pipeline

That's it. The number of calendar days between a candidate first appearing in your recruitment process and that candidate accepting an offer.

If a candidate applied on the 1st of March and accepted an offer on the 22nd of March, their time to hire is 21 days.

To calculate average time to hire across multiple roles, you add up the individual time to hire figures and divide by the number of hires.

Average Time to Hire = Sum of All Individual Times to Hire ÷ Number of Hires

So if three hires had time to hire figures of 21 days, 34 days, and 28 days, your average is 27.6 days.

Simple. And yet here's where it immediately gets complicated.


The Definitions You Need to Agree Before the Formula Means Anything

The formula has two variables. Both of them sound obvious. Neither of them is.

You may also want to click here to compare time to hire vs. time to fill.


What counts as "entering the pipeline"?

This is the one that trips up most teams, because there are at least four reasonable options — and the one you choose significantly affects your number.

Option 1: Application date. The candidate submits an application. The clock starts. Clean, simple, easy to pull from an ATS. The problem is that it includes time spent in the inbox before anyone looked at the application — which is real time, but it measures how quickly you reviewed applications rather than how quickly you processed a known candidate.

Option 2: Application reviewed / shortlisted. The clock starts when a recruiter actively engages with the application — either marking it for review or moving it to shortlist. This removes inbox waiting time, which some teams argue is a sourcing problem rather than a process problem. The counter-argument is that a candidate doesn't experience it that way. They submitted an application. Time started for them.

Option 3: First contact made. The clock starts when the recruiter first reaches out to the candidate — whether that's a screening call invite, an email, or a LinkedIn message to a sourced candidate. This is often used by teams doing proactive sourcing where "applying" isn't the entry point.

Option 4: Screening call or first interview completed. Some organisations start the clock at the first substantive interaction. This dramatically compresses the headline metric and also, frankly, flatters it. We'd suggest this is the least defensible option if you're trying to give candidates or leadership an honest picture of process speed.

There's no single correct answer. The right choice depends on your process and what you're actually trying to measure. But you have to pick one, write it down, and apply it consistently. Anything else produces numbers that can't be tracked over time or compared across teams.


What counts as "offer accepted"?

This one seems more obvious and is slightly less contentious — but still worth nailing down.

Is it the date the verbal offer was made? The date the candidate verbally accepted? The date the written offer was sent? The date the signed contract was returned?

Most teams use verbal offer acceptance, which represents the point at which the candidate has committed and the hiring decision is effectively made. Using signed contract returns adds days that are largely outside your control — depending on notice periods, candidate circumstances, and how long your HR team takes to generate paperwork.

Pick a definition, document it, stick to it.


How Is Time to Hire Measured in Practice?

In theory, it's pulled automatically from your ATS. Most modern applicant tracking systems log timestamps at every pipeline stage, which means the raw data for calculating time to hire and average time to hire should be sitting there already.

In practice, the data is often a mess.

Here's what tends to go wrong.

Inconsistent stage entry.

Some recruiters update candidate stages in real time. Others do it in batches at the end of the week. Some forget until someone asks for a report. The timestamps in the ATS reflect when the system was updated, not when the event actually happened — and those two things are often days apart.

‍

Sourced candidates logged late.

When a recruiter sources a candidate proactively — via LinkedIn, a referral, an event — that candidate often gets added to the ATS at a later stage than they were actually first contacted. The clock starts later than it should, which flatters the metric.

‍

Withdrawn candidates excluded by default.

Most ATS reporting on time to hire only covers candidates who were hired. Candidates who withdrew during the process — often the most important signal about candidate experience — don't appear in the calculation at all. Your average looks better than it is because it's averaging only the outcomes that reached a conclusion.

‍

Multiple roles conflated.

If you're averaging time to hire across a graduate entry-level role and a Chief Technology Officer search in the same number, the average is technically correct and practically useless.

‍

None of this means the data isn't worth collecting. It means it needs auditing before it's trusted, and that someone needs to own data quality in the ATS rather than assuming the system is taking care of it.


What Is a Good Time to Hire Metric?

The honest answer: it depends on the role, the sector, and the labour market at the time you're hiring.

The slightly more useful answer: here's the context you need to interpret it.

LinkedIn's data consistently puts average time to hire across professional roles at somewhere between 28 and 42 days, with meaningful variation by sector and seniority. Technology, engineering, and senior leadership roles skew higher — 45 to 70 days is not unusual. High-volume, entry-level roles in retail or hospitality can move in under two weeks.

Industry benchmarks for time to hire are a starting point, not a standard. Here's what a good time to hire metric actually looks like in practice.

‍

It's consistent with your own historical average.

More useful than any external benchmark is knowing whether your own number is improving, static, or getting worse over time. Directional movement tells you whether your process changes are working.

‍

It varies sensibly by role type.

A single company-wide average that blends graduate hires with senior appointments tells you almost nothing. Segment by level, by function, by hiring manager. That's where the actionable insight lives.

‍

It's correlated with quality of hire.

This is the check that most teams skip. If your time to hire dropped by ten days last quarter, that's good. If your quality of hire also dropped, your speed improvement came at a cost. If quality held or improved, you've actually made progress.

‍

It reflects completed processes, not abandoned ones.

If a string of roles are taking 70+ days because candidates are dropping out and you're restarting from scratch, your average time to hire might still look reasonable while the process is quietly broken. Track restarts and withdrawals separately.

‍

A good time to hire metric is one that's consistently defined, segmented meaningfully, and read alongside quality indicators rather than in isolation. A single average figure, reported quarterly, without any of that context, is a number that makes the dashboard look tidy without telling you anything particularly useful.


Calculating Time to Hire Across Multiple Hires

If you want your average time to hire to be genuinely meaningful — the kind that surfaces real problems and tracks real improvement — here's a more robust approach than a simple mean average.

Segment before you average.

Calculate separate averages for different role types, seniority bands, business functions, and hiring managers. The differences between these segments are usually more informative than the overall number.

‍

Track median alongside mean.

A single slow hire — a six-month search for a rare specialist, say — can pull your mean average significantly higher without reflecting typical process performance. The median (the middle value in your dataset) is less sensitive to outliers and often gives a better picture of what's normal.

‍

Track time spent at each stage, not just end-to-end.

Most ATS tools can give you this breakdown. Stage-level data tells you whether delay is concentrated at a specific point in the process — offer stage, second interview scheduling, feedback loop — rather than spread evenly across everything. That's the data that enables targeted fixes rather than vague process reviews.

‍

Include withdrawals in your analysis, even if not in the headline metric.

Track at which stage candidates are withdrawing, and how long they'd been in the process when they did. Candidates who withdraw after 25 days of silence between stages are telling you something that your average time to hire won't.


How SquareLogik Handles Time to Hire Data

We think about time to hire as a diagnostic tool rather than a reporting metric.

A number on a dashboard is only useful if it tells you something you can act on. Which means we're less interested in what the average is and more interested in where time is accumulating, whether candidates are having a smooth experience while it does, and whether the speed of the process is correlating with the quality of the outcomes.

In practice, that means we agree definitions upfront with clients — exactly when the clock starts, exactly what counts as an offer acceptance, exactly how we'll segment and review the data — before we start tracking anything. Because a metric built on inconsistent definitions is just decoration.

We also track alongside quality of hire, so that any improvement in time to hire can be evaluated for what it actually produced, not just how fast it happened.

If you're finding that your time to hire data is difficult to interpret, inconsistent across teams, or hard to connect to any meaningful outcome — that's a fairly common situation, and it's usually more fixable than it looks.

Connect with us to learn more.


Frequently Asked Questions

What is the formula for time to hire?

Time to hire equals the date of offer acceptance minus the date the candidate entered the recruitment pipeline, measured in calendar days. To calculate average time to hire, add up the individual time to hire figures for all hires in a given period and divide by the total number of hires. The formula itself is simple — the complexity lies in agreeing a consistent definition of when the pipeline starts, which affects your number significantly.

‍

How is time to hire different from time to fill?

Time to hire starts when a specific candidate enters your recruitment pipeline and ends when they accept an offer. Time to fill starts when the job requisition is opened — before any candidate exists — and ends at the same point. Time to fill is always longer because it includes the pre-pipeline period: job approval, writing and posting the role, and waiting for applications. Time to hire measures process efficiency. Time to fill measures total vacancy cost and workforce planning accuracy.

‍

What is a good time to hire metric?

For most professional roles, 28 to 42 days is broadly typical, though this varies significantly by sector, seniority, and current labour market conditions. Technical and senior roles routinely run longer. More important than hitting an industry benchmark is whether your own metric is improving over time, whether it varies sensibly across role types, and whether it correlates with quality of hire. A falling time to hire that's accompanied by falling quality of hire isn't progress — it's just faster mistakes.

‍

What should I include in the time to hire calculation?

Calendar days from when a candidate first enters your pipeline to when they accept an offer. The key decisions are: what counts as entering the pipeline (application date, first contact, first interview) and what counts as acceptance (verbal or signed contract). Both need a clear, documented definition applied consistently across every hire. If different teams are using different definitions, your company-wide average is an average of incomparable numbers, which is less useful than it sounds.

‍

Why does my time to hire data look inconsistent?

Usually one of three reasons. First, inconsistent stage updates in the ATS — recruiters logging events at different times creates timestamp errors. Second, sourced candidates being added to the system later than they were first contacted, which shortens the apparent pipeline time for those hires. Third, different teams using different definitions for when the clock starts. An ATS audit and a shared, written definition of the metric will fix most of this.

‍

Should I use mean or median to report average time to hire?

Both, ideally. The mean average is more commonly reported but sensitive to outliers — one unusually long search can inflate it significantly. The median (the middle value in your dataset) gives a better picture of what's typical for most hires. For meaningful benchmarking, report both and note when the gap between them is large, which usually signals that a small number of slow or unusual searches are distorting the overall picture.

‍

How does time to hire affect candidate experience?

Significantly. From a candidate's perspective, the clock starts the moment they apply or are contacted. Long gaps between stages — even if the total process is within a reasonable range — signal disorganisation, poor communication, or indifference. The best candidates, who typically have multiple options, are most sensitive to this. Tracking time to hire at the stage level, rather than just end-to-end, helps identify where the candidate experience is breaking down before it starts costing you the people you actually wanted.

Related Articles

September 2026
Read time

What Makes Candidates Choose One Employer Over Another

Salary gets candidates to the table. It rarely closes the deal. Here's what candidates are weighing when they have more than one offer.

Most employers think candidates choose on salary.

For many candidates — the employed, the experienced, the ones you most want to hire — salary is a threshold, not a differentiator. Once an offer clears the level the candidate needs, pay stops being the deciding factor and other things take over.

Those other things are where employers lose candidates they thought they had secured. Not to higher pay. To an employer who understood what the candidate was evaluating and gave them better answers.


The Process Sends a Signal Before the Offer Does

Candidates read the hiring process as a preview of the organisation.

A slow process with poor communication between stages tells a candidate how decisions are made. A disorganised first interview tells them something about management quality. An offer that takes twelve days to generate after a verbal acceptance tells them how much operational weight their joining carries internally.

None of this is fair. A slow HR approval chain is not a reliable indicator of a bad employer. But candidates are making probabilistic judgements with limited information, and the hiring process is the primary data source available to them. They use it.

The employer whose process is fast, communicative, and clearly managed wins candidates at the margin repeatedly. Not because the work is better or the salary is higher, but because the experience of being recruited there felt different from everywhere else.


The Manager Is Often the Decision

Ask candidates who have turned down an offer why, and the answer frequently involves the person they would have reported to.

An impressive company with an uninspiring hiring manager loses candidates to a less impressive company with a manager who clearly knew what they were doing, communicated well, and made the candidate feel that working for them would be challenging in the right way.

Candidates assess the manager throughout the process.  

  • How prepared they are for the interview.  
  • Whether their questions are generic or specific.  
  • How they talk about the team and the work.  
  • Whether they listen or perform.  

By the final stage, a candidate has formed a view about whether this manager is someone whose feedback they would grow from or someone whose management style they would spend energy navigating around.

Employers who involve their best managers visibly in the hiring process win more offers than those who treat the manager as the final interview rather than the primary selling point.


Clarity About the Role and What Comes After It

Candidates accepting a new role are making a two-part decision.  

  • The job itself
  • What the job leads to

An employer who can answer the second question clearly (what does progression look like, what does success in this role make possible, what have people who held this role previously gone on to do) gives the candidate something the vague offer cannot match.

The inability to answer this question is not always a deal-breaker. But when two offers are otherwise comparable, the employer who has articulated a convincing forward picture wins consistently. The candidate does not want to feel that they are accepting a ceiling. They want to feel that they are stepping onto a path.


Honesty Compounds Over Time

The employer who is honest about the hard parts of the role during the recruitment process earns a disproportionate level of trust.

This sounds counterintuitive. Naming the challenges, the current state of the team, the parts of the role that are difficult should discourage candidates. In practice, it does the opposite. Candidates who encounter an employer willing to say "this is where we are struggling and this is what the role will involve in addressing it" are talking to someone they can trust. Every other employer is selling them something.

Trust is the currency candidates are operating in when they make a final decision. The employer who has spent the process building it, rather than managing the candidate's perception of the company, starts the offer conversation from a stronger position.

Candidates who joined on the back of an honest pitch stay longer too. The first month does not produce a credibility gap between what was promised and what is real. That gap, when it exists, is where early attrition starts.


Speed at the Offer Stage

The candidate's enthusiasm for a role is not static. It peaks somewhere around the final interview and declines from there.

An offer that arrives less than four days after a final interview meets a candidate at close to peak enthusiasm. An offer that arrives eighteen days later, after a sign-off chain the candidate was not told about, meets a candidate who has mentally moved on, accepted another role, or simply lost the momentum that made the decision feel exciting.

Speed at the offer stage is not the same as rushing the assessment. It is the natural conclusion of a process that has been well-managed throughout — where the decision-maker was in the process, where the approval was pre-agreed, where generating the offer letter took hours rather than a week.

Employers who consistently lose candidates at the offer stage almost always have an internal process problem, not a candidate problem.


Flexibility and How It Is Communicated

Flexible and hybrid working arrangements have moved from differentiator to expectation in most professional roles.

The employer who offers genuine flexibility and says so clearly wins over the employer who offers the same flexibility but communicates it vaguely or buries it in policy documents. Candidates who cannot get a clear answer about working arrangements during the recruitment process assume the worst.

This is not about the arrangement itself. It is about whether the employer communicates clearly enough that the candidate can make a confident decision. Ambiguity at the offer stage, on a question as significant as where and when the candidate will be expected to work, creates doubt that sometimes tips the decision toward the employer who was clearer.


The Moment That Tips It

When a candidate has two comparable offers, the decision often comes down to a feeling that is difficult to articulate but easy to trace back to specifics.

  • The employer who called after the final interview to check in before the offer arrived.
  • The hiring manager who sent a personal note rather than letting the process speak for itself.  
  • The recruiter who was honest about the timeline rather than managing the candidate's expectations with vague reassurances.

These are not grand gestures. They are small signals that the organisation values the candidate as a person rather than a vacancy to fill. Candidates notice them. They do not always name them in the debrief. But they tip the scales at the margin more often than salary negotiations do.

At SquareLogik, we advise clients on candidate decisions, not just candidate pipelines.

The employers who retain the candidates they want share a set of characteristics: a clear and honest pitch, a well-managed process, and an offer that arrived when the candidate was still warm. None of those require a larger budget. All of them require deliberate attention.


Frequently Asked Questions

What do candidates prioritise when choosing between two job offers?  

Salary clears the threshold but rarely decides between comparable offers. Candidates weigh the quality of the hiring process as a signal of the organisation, their assessment of the manager they would work for, clarity about progression, and the honesty of how the role was presented. The employer who communicated well, moved at a pace that respected the candidate's time, and gave them confidence in the decision wins at the margin more often than the employer who simply paid more.

How does the recruitment process affect a candidate's decision?  

Significantly. Candidates treat the hiring process as a preview of the organisation — how decisions are made, how people are managed, how much operational weight the company places on incoming talent. A slow, poorly communicated process tells a story the employer may not intend to tell. A fast, respectful, well-managed one builds the kind of trust that makes an offer easier to accept and harder to decline.

‍

Does salary determine which employer a candidate chooses?  

For candidates under financial pressure, yes. For employed candidates with options, salary functions as a threshold — once it clears the level the candidate requires, it stops being the primary deciding factor. Candidates in this position are weighing career trajectory, manager quality, flexibility, culture signals from the process, and the honesty of how the role was presented. Employers who compete exclusively on pay against candidates who are not primarily motivated by it consistently lose to employers with better answers to the other questions.

‍

What role does the hiring manager play in a candidate's decision?  

A central one. Candidates assess the manager throughout the process and form a view about whether working for them would advance their career or complicate it. A strong, credible, well-prepared hiring manager is a selling point that no job ad communicates and no salary matches. Employers who involve their best managers visibly and early in the process win more offers than those who treat the manager as the final stage rather than a primary reason to join.

‍

How important is speed in the offer process?

Candidate enthusiasm peaks around the final interview and declines from there. An offer that arrives promptly meets the candidate at close to maximum motivation. One that takes two weeks to materialise meets a candidate who has mentally recalibrated. Employers who lose candidates at the offer stage almost always have an internal process problem — a sign-off chain, an approval bottleneck, a contract generation delay — rather than a candidate problem. Fixing the internal process converts more offers than improving the compensation package.

‍

September 2026
Read time

How to Find Candidates When You Have No Employer Brand

No employer brand doesn't mean no candidates. It means a different approach. Here's how to find and hire excellent people before anyone has heard of you.

Most employer brand advice assumes you have six months and a content budget.

If you are reading this, you probably have neither.  

You have an open role, a sparse LinkedIn page, and the faint hope that someone excellent will apply anyway.

They might. But waiting for inbound applications without brand recognition is a low-probability strategy. The candidates you want are almost certainly employed elsewhere, not browsing job boards for companies they have never heard of.

The good news: you do not need a famous brand to hire well. You need enough credibility for the specific candidate you are trying to reach.  


Build Trust Without an Employer Brand

Brand recognition and trust are different things.

A large employer with a recognisable name has recognition working in its favour. But a small or unknown employer needs to build trust during the process itself through:

  • The quality of the outreach
  • The specificity of the role
  • The honesty of what is on offer
  • The credibility of the people involved

This is achievable without a marketing department. It requires deliberate attention to how the company presents itself at every touchpoint a candidate encounters.

  1. Start With Your Network

The most direct route to candidates when you have no brand is the founder's network, the leadership team's connections, and the existing employees' professional relationships.

A direct message from a founder to someone they respect — explaining what they are building and why this person would be excellent for it — converts at an excellent rate because:

  • It arrives with implicit credibility
  • The sender is known to the recipient
  • The context is specific
  • The ask is personalised

This works at small scale, which is the scale most no-brand companies are operating at. You are not trying to reach ten thousand people. You are trying to reach ten or fifteen credible individuals and have a real conversation with five of them.

Map your network before posting anywhere. The right candidate is more likely to be two connections away than browsing Indeed.

  1. Write a Highly Specific Job Ad

Without a known name on the listing, the job ad itself carries the full burden of communicating why this opportunity is worth a strong candidate’s attention.

Generic ads fail doubly for unknown companies. The candidate has no prior reason to trust the organisation and the ad gives them no new reason. A specific, honest, well-written ad compensates for the absence of reputation by giving the reader something concrete to assess.

  • Name the problem the role is solving.  
  • Describe the first three months of work in practical terms.  
  • Be direct about what the company is, how far along it is, what the challenges are.  
  • Include the salary.  

Yes, salary. An unknown employer that hides its compensation is asking candidates to take a leap of faith with almost no information, and many will not bother.

Specificity signals that a real person wrote this ad about a real job.  

  1. Use Referrals Early and Aggressively

Employee referrals work better for unknown companies than for well-known ones, for a counterintuitive reason.

When a candidate receives a referral from someone they trust, that trust transfers to the opportunity. The referring person becomes the employer brand proxy. The candidate is not evaluating a company they have never heard of — they are responding to a recommendation from someone whose judgement they respect.

A single strong referral from a credible person in your network is worth more than a week of sponsored job postings. Ask specifically and ask early.  

Not "do you know anyone looking?" but "we are hiring a senior data engineer with experience in X — who is the strongest person you have worked with in this space?"

  1. Build Micro-Credibility Fast

You cannot build a brand overnight. But you can build enough credibility for the candidate in front of you.

  • A careers page with one good paragraph about the company, the team, and the role beats a blank page.  
  • A LinkedIn profile for the founder with a few posts about what they are working on beats a dormant one.  
  • A short video from the hiring manager explaining why this role exists and what success in it looks like beats a templated job description.

None of this requires a grand marketing strategy. It requires spending 2-3 hours creating something specific that a curious candidate can find when they search the company name after seeing your outreach.

Because they will search.  

Every candidate who receives a direct approach and considers responding will look you up. Give them something to find that confirms the opportunity is real and the company is credible enough to invest their time in.


What Not to Do When Recruiting Without a Brand

Two approaches consistently backfire for no-brand employers.

  1. Overstating what the company is.  

Candidates research. A job ad describing a "leading innovator" in a space where the company is eighteen months old and has twelve employees puts your credibility at risk. Honesty about stage, size, and challenge attracts candidates who want exactly that context — and there are excellent people who prefer an early-stage environment to a corporate one.

  1. Posting everywhere simultaneously.  

Scattering the same job across every available platform without the brand to support it produces volume from the wrong pool and signals desperation to anyone paying attention. Two or three targeted, relevant channels performed well outperform ten mediocre ones.


How SquareLogik Finds Candidates for New Brands

We place candidates into companies that candidates have not heard of. The work is in our approach — how the opportunity is framed, who is approached, and what they are told about the role and the organisation.

For companies without established employer brand, the briefing process we run is different. We need to understand what makes the role genuinely compelling before we approach anyone, because we are carrying the credibility conversation the company cannot yet carry itself.

If you are hiring at a stage where your brand is not doing any of the work for you, we can help.


Frequently Asked Questions

Can you hire good candidates without an employer brand?  

Yes, through a combination of network-led sourcing, specific and honest job advertising, and referrals that transfer trust from someone the candidate already knows. Brand recognition accelerates hiring by doing credibility work before any conversation starts. Without it, that credibility must be built during the process itself — through specificity, honesty, and the quality of the outreach.

‍

What do candidates look for when researching an unknown company?  

Evidence that the company is real, that the role is genuine, and that the people behind it are credible. A functional website, a LinkedIn presence with some activity, a founder or hiring manager who has a professional footprint, and consistent information across platforms. Candidates who receive direct outreach and are considering responding will search the company name before replying. Give them something substantive to find.

‍

How do referrals help companies with no employer brand?  

A referral transfers the trust the candidate has in the person making the recommendation to the opportunity being recommended. For an unknown company, this shortcut is particularly valuable — the candidate is responding to a trusted person's judgement rather than evaluating an unfamiliar organisation from scratch. Referrals from credible sources within your network are the fastest route to candidates who will take an unknown employer seriously.

‍

How should an unknown employer write a job ad?  

With more specificity than a known employer needs. Name the problem the role will solve, describe the first three months concretely, be direct about the company's stage and size, and include the salary. An unknown employer asking candidates to apply without this information is asking for trust it has not earned. A specific, honest ad does the credibility work that a recognisable brand would otherwise do automatically.

‍

When should a no-brand company use a recruitment agency?  

When the role requires reaching candidates who will not find the company through its own channels — passive candidates in specialist fields, senior hires who need a credible third-party introduction, or roles where the candidate pool is too small for job board advertising to produce results. A recruiter with relevant sector relationships can carry the credibility conversation on behalf of a company that cannot yet carry it itself.

‍

September 2026
Read time

Employee Onboarding Best Practices That Reduce Early Attrition

Early attrition is expensive and largely preventable. Here are the onboarding practices that keep new hires from becoming costly short-tenure regrets.

The average employee decides whether a job was the right move within the first two weeks.

Not officially. Not consciously. But the doubt that turns into a resignation in a few months often gets planted earlier — during a chaotic first week, an absent manager, or the creeping realisation that the role was described more attractively than it operates.

Early attrition is the most expensive form of turnover because it generates the full replacement cost with none of the productivity return. An employee who leaves at month three has cost the organisation recruitment fees, onboarding time, and lost team output, and delivered almost nothing in exchange.

Most of it is preventable. Here is how.


1. Set Expectations Immediately

Onboarding begins before the contract is signed, not on the morning of the first day.

New hires who arrive with a clear picture of the role, the team, and the first month's priorities outperform those dropped into ambiguity. It is good practice to send a pre-start communication covering:  

  • Who they will meet in the first week
  • What their first project or focus area will be
  • What the practical logistics look like.  
  • Any small details like parking, dress code, where to go, who to ask for


2. Structure the First 30 Days

The first thirty days are not an orientation period. They are a retention window.

A new hire left to navigate the organisation without structure — working out the informal rules, the real reporting relationships, the unwritten norms — is spending cognitive energy on problems that have nothing to do with the job they were hired for. That energy is finite. When the job eventually feels hard on top of everything else, the decision about whether to stay comes up.

Structured onboarding in the first thirty days covers three things:

  • A scheduled introduction to every team or person the new hire will work closely with.
  • A defined first project with clear scope and a clear owner to report progress to.  
  • A named point of contact for the questions too small to escalate but too persistent to ignore.


3. Plan Check-Ins Every 30, 60, and 90 Days

Schedule conversations with specific questions:  

  • Is the role what you expected?  
  • What is harder than anticipated?  
  • What do you need that you do not currently have?  
  • What would make the next thirty days more effective?

These conversations catch problems before they become resignations. A new hire who is struggling, asked directly whether the role matches expectations, will tell you.  


4. Hold Managers Accountable

Onboarding documentation, induction programmes, and structured check-in schedules all fail the same way: the manager does not run them.

The manager is the onboarding. Not HR, not the buddy system, not the welcome pack.  

The direct manager's behaviour in the first 90 days determines whether a new hire feels set up to succeed or left to muddle through. Their availability, the quality of feedback they provide, and whether they proactively clear blockers or expect the new hire to figure it out independently shapes the experience more than any formal programme.

Holding managers accountable for onboarding outcomes, including monitoring early attrition within their teams, converts onboarding from a process that exists on paper into one that functions in practice. When managers know that early departures are tracked and attributed, behaviour changes.


5. Surface the Unwritten Rules Early

Every organisation has rules that are not in the handbook.

  • How decisions are really made.  
  • Who has informal influence.  
  • What escalation looks like in practice versus how it is supposed to work.  
  • Which meetings are for show and which ones matter.  

New hires who discover these slowly — by making avoidable mistakes — find the process demoralising. Those told early arrive faster and feel less like outsiders.

This does not require a formal session. A candid conversation with the manager in the first week, covering how the team actually operates, does the job. A buddy who is not the manager helps too — someone the new hire can ask questions too small to escalate but important enough to require assistance.


6. Do Not Onboard in a Vacuum

New hires need context, not just content.

An induction that covers the company history, the product roadmap, the organisational values, and the benefits package tells a new hire a great deal of information and almost nothing about what the next six months of their working life will feel like.  

Context means something different:

  • Why the company exists and where it is trying to go, explained by someone who believes it rather than read from a slide
  • Where the team sits in the organisation and why that matters to the work
  • What the industry landscape looks like and how the company competes within it
  • What the biggest challenges on the horizon are (and not the sanitised version)

New hires who understand the broader picture invest in it. Those given information without context do their job and nothing more.


7. Extend Onboarding for Senior Hires

A 90-day onboarding programme is appropriate for most roles. For senior and leadership hires, it is the minimum.

A new Director or VP walking into a complex organisation, with existing team dynamics, historical decisions to understand, and strategic priorities to shape, cannot be effectively integrated in three months. The risks of a senior hire feeling unsupported, overloaded, or isolated in the first quarter are higher than at any other level — and the cost of losing them is proportionally larger.

For senior hires specifically:

  • Extend the formal onboarding structure to six months
  • Include a stakeholder mapping exercise in the first month — who the new hire needs to build relationships with, in what order, and why
  • Schedule structured conversations with the CEO or relevant executive not just in week one but monthly through the first quarter
  • Create explicit space for the new hire to share observations about the organisation without those observations being treated as criticism — a senior hire's external perspective is an asset in the first months before it is socialised away


Boost Retention by Improving the Recruitment Process

In case early attrition persists despite strong onboarding points to a hiring problem, not an onboarding one.

A new hire who was given an inaccurate picture of the role during recruitment, or whose values and working style were not assessed alongside their technical capability, will struggle regardless of how well the first ninety days are managed. Onboarding cannot compensate for a placement that was wrong from the start.  

When SquareLogik provides recruitment services, we set expectations at placement, not after. Before a candidate starts, we ensure they have a true picture of the role, the team, and the first month.

We also track placements at three, six, and twelve months. Patterns of early attrition in a specific role are almost always correctable at the brief and hiring stage, not the onboarding stage. The earlier that conversation happens, the cheaper the fix.

If you’d like to learn more about our recruitment process and how we manage high employee retention rates for our clients, connect with us today.


Frequently Asked Questions

What is the most effective onboarding practice for reducing early attrition?  

Structured check-ins at thirty, sixty, and ninety days. A direct conversation asking whether the role matches expectations, what is proving difficult, and what the new hire needs, catches problems before they become departures. New hires who are asked these questions directly are significantly more likely to raise concerns rather than quietly disengage. The conversations cost an hour per check-in and prevent the full cost of replacement.

‍

How long does onboarding take to complete?  

Effective onboarding runs for ninety days minimum, not one week. The first week covers logistics and introductions. The first month builds the working relationships and context a new hire needs to be effective. Days thirty to ninety are where performance expectations sharpen and the psychological contract between employer and employee solidifies. Organisations that treat onboarding as complete after the induction week see disproportionately high early attrition in months two through four.

‍

What causes early attrition in new employees?  

The most consistent causes are a gap between how the role was described during recruitment and how it operates in practice, insufficient structure in the first thirty days, an absent or disengaged manager, and unmet expectations about pace, culture, or progression. Early attrition is rarely caused by capability. It is caused by misalignment — between what the new hire expected and what they found — that structured onboarding surfaces and addresses before it tips into departure.

‍

How does pre-boarding reduce attrition?  

Pre-boarding converts the gap between offer acceptance and start date from a period of growing uncertainty into one of increasing confidence. A new hire who receives clear information about their first week, their initial priorities, and the people they will meet arrives settled rather than apprehensive. That difference in psychological state compounds: a confident start produces faster integration, faster productivity, and lower early attrition.

‍

Who is responsible for onboarding — HR or the line manager?  

The line manager. HR designs the process and provides the structure. The manager executes it and owns the outcome. The most common failure in onboarding is a well-documented programme that the manager does not follow because there is no accountability for early attrition outcomes within their team. Linking manager performance metrics to ninety-day retention rates of new hires changes the incentive structure and, with it, the behaviour.

‍