Bad onboarding does not announce itself. It shows up as a new hire who quits in week three, a manager who stops trusting the process, and a hiring pipeline that never quite catches up. If your new hires are dropping off before their first review, the process itself is the problem — not the people you hired. Below are seven concrete signs your onboarding is pushing people out the door, what each one costs you, and what to fix first. The short version: manual, paper-heavy, disconnected onboarding creates the exact friction that makes new hires question their decision. Fix the plumbing with automated onboarding workflows before you add anything else on top.

1. Paperwork Chases the New Hire Instead of Waiting for Them

If a new hire is still filling out tax forms, benefits elections, or policy acknowledgments during their first week, the process started too late. Paperwork should be done before day one, not during it.

• Offer letters go out with no linked onboarding packet
• W-4, I-9, and direct deposit forms handled as separate email threads
• Signatures tracked in someone’s inbox instead of a system
• HR manually checks who has and hasn’t completed each form
• New hire’s first impression is administrative busywork, not welcome

Verdict: This is the easiest fix on the list and the one with the fastest payoff. Automated new-hire paperwork removes the chase entirely — see how to automate new hire paperwork for the build.

2. Day One Has No Plan Waiting for Them

A new hire’s first day sets the tone for the next two years. If they show up to a locked laptop, no login credentials, and a manager who forgot they were starting, you’ve told them exactly how much this company plans ahead.

• Equipment ordered after the start date, not before
• Account provisioning kicked off manually once someone remembers
• No welcome email, no schedule, no assigned buddy
• Manager finds out the new hire started from a hallway conversation
• First-day tasks live in someone’s memory, not a workflow

Verdict: A triggered sequence — start date hits, workflow fires, IT and facilities get notified automatically — solves this permanently. This is the exact gap covered in 9 employee onboarding tasks you should never do manually.

3. Data Gets Re-Typed at Every Handoff

Every time a human retypes new-hire data from one system to another, you introduce a chance for error. This isn’t hypothetical. Sarah, HR Director at a regional healthcare organization, watched her team burn hours every week re-entering the same candidate data across three systems before she automated the handoff and reclaimed 12 hours a week — while cutting total hiring time 60%.

• ATS data manually copied into the HRIS
• HRIS data manually copied into payroll
• Compensation figures re-typed instead of pulled from source
• No audit trail showing where a number came from
• Errors caught only after they’ve already caused damage

Verdict: This is the highest-cost sign on this list because the failure mode is expensive, not just annoying. David, an HR Manager at a mid-market manufacturer, had a new hire’s $103K salary mis-entered as $130K during a manual ATS-to-HRIS transfer. The company overpaid $27K before catching it — and the employee quit once the overpayment was corrected. That’s not a training problem. That’s a system with no single source of truth. Automate the handoff and the number only gets typed once. See manual vs. automated onboarding for a side-by-side breakdown of where these errors happen.

4. No One Actually Owns the Process

Ask five people at your company who owns onboarding and you’ll get five different answers, or a shrug. When ownership is unclear, gaps get discovered by the new hire, not by you.

• HR assumes IT is handling equipment and access
• IT assumes the hiring manager already requested accounts
• The hiring manager assumes HR sent a welcome packet
• No single system shows onboarding status end to end
• Fixes happen reactively, after something’s already been missed

Verdict: A workflow with clear triggers and named owners at each step replaces tribal assumption with a visible process. Nick, a recruiter at a small firm, reclaimed 15 hours a week personally — and his three-person team reclaimed 150+ hours a month combined — once ownership was built into the automation instead of left to memory.

5. Your Systems Don’t Talk to Each Other

If your ATS, HRIS, payroll, and IT provisioning tools operate as five separate islands, your new hire is the one stitching them together by proxy — showing up in some systems and not others, with access delays nobody notices until it blocks their work.

• ATS candidate record doesn’t sync to HRIS automatically
• Payroll setup waits on a manual email from HR to finance
• IT account creation isn’t triggered by any HR event
• Benefits enrollment deadlines tracked in a spreadsheet
• No connector, integration, or API link between core systems

Verdict: This is a plumbing problem, not a people problem, and it’s exactly where a properly connected HRIS paired with Make.com automation earns its keep. Connect the systems once and the sync runs itself from that point forward.

6. There’s No Feedback Loop Until They Quit

If the first real signal you get on a new hire’s experience is their resignation, you had no feedback loop — you had a countdown. Structured check-ins at 30, 60, and 90 days catch friction while it’s still fixable.

• No scheduled manager check-ins beyond day one
• No pulse survey triggered automatically at key milestones
• Exit interviews are the first time real feedback surfaces
• HR has no visibility into new-hire sentiment before churn
• Managers rely on memory to remember when to check in

Verdict: Automate the trigger, not the conversation — a workflow that reminds the manager and sends the survey at day 30/60/90 costs nothing to run and catches problems before they become resignations. Full breakdown of the “why” behind this in our onboarding automation FAQ.

7. Every New Hire Feels Custom-Built From Scratch

If onboarding a salesperson looks nothing like onboarding an engineer in terms of process (not content), you’re rebuilding the wheel every time instead of running a repeatable system with role-specific branches.

• No standard onboarding template per role or department
• HR reconstructs steps from memory or old email threads
• Consistency depends on who happens to be running it that week
• New hires in the same role get different experiences
• No way to measure or improve the process because it’s never the same twice

Verdict: Build the workflow once as a repeatable template with role-based branches, and every future hire runs the same reliable path. TalentEdge did exactly this and posted $312K in annual savings with a 207% ROI once onboarding stopped being reinvented per hire. Start with what onboarding automation actually is if you’re building the case internally.

Why This Costs You More Than It Looks Like

None of these seven signs feel urgent in isolation. That’s what makes them dangerous. A missing laptop on day one, a re-typed salary figure, a skipped 60-day check-in — each one looks like a one-off. Add them up across a year of hiring and you get turnover in the first 90 days, a recruiting team re-filling roles they already filled, and managers who’ve quietly stopped trusting HR to get people ready.

The 1-10-100 rule applies directly here: 10 minutes a day of avoidable onboarding admin adds up to a full week of lost productivity a year, per employee touching that process. Multiply that across HR, IT, and every hiring manager involved, and the “small” manual step is never actually small. Gartner’s research on employee experience backs this up directly: friction in the first 90 days is one of the strongest predictors of early turnover — see Gartner on employee experience.

Fix the Plumbing Before You Add AI

Every one of these seven signs is a workflow problem, not an intelligence problem. Automation first, then AI — in that order. Connect your ATS to your HRIS. Trigger IT provisioning off a start date instead of a memory. Automate the paperwork, the check-ins, and the handoffs. Once that plumbing runs itself, AI has clean, structured data to work with instead of trying to make sense of five disconnected spreadsheets. Skipping straight to an AI tool without fixing the underlying process just gets you a faster version of the same mess.

This is also where adoption-by-design matters. The best fix doesn’t ask your HR team or your new hires to learn a new tool — it works inside Gmail, Slack, your ATS, and your HRIS, the systems people already use every day. The automation absorbs the complexity. The person doing the work barely notices it’s there.

How We Evaluated These Warning Signs

Each sign on this list was scored against three criteria pulled from real client engagements and industry research: frequency (how frequently HR and operations leaders report this specific friction), cost of inaction (measured in hours, turnover risk, or direct error cost where documented), and fix complexity (whether solving it requires a full systems overhaul or a targeted workflow). Signs like data re-entry and disconnected systems ranked highest because they compound silently — the damage isn’t visible until a specific incident (like a payroll error) forces the issue into the open. SHRM’s research on the true cost of turnover and onboarding backs up the pattern we see directly in client audits: SHRM on the true cost of turnover.

Frequently Asked Questions

What’s the single biggest onboarding mistake companies make?

Treating onboarding as a checklist instead of a connected system. A checklist gets done manually and inconsistently. A connected system runs the same way every time, whether HR remembers or not.

How fast can we fix disconnected onboarding systems?

Connecting an ATS to an HRIS through Make.com takes days, not months, because you’re wiring existing tools together rather than replacing them. The Make.com integrations directory lists native connectors for most major ATS and HRIS platforms.

Do we need to buy new software to fix this?

No. Most of these seven signs get fixed by connecting the tools you already have. Adoption-by-design means building automation around your existing stack, not forcing a platform migration.

Related Reading

• Automating Employee Onboarding the Right Way
• 9 Employee Onboarding Tasks You Should Never Do Manually
• How to Automate New Hire Paperwork
• What Is Onboarding Automation?
• Manual vs. Automated Onboarding
• What Is an HRIS?
• Onboarding Automation: Frequently Asked Questions

Expert Take

I’ve watched this pattern play out with client after client: nobody notices onboarding is broken until a new hire quits and someone finally asks why. By then it’s not one fix, it’s five. Start with the systems that don’t talk to each other — that’s where the real damage compounds, quietly, every single week you leave it alone.