Enterprise employee onboarding: offer to fully ramped

Interviewer: So I want to understand onboarding end to end. Somebody just accepted an offer — take me from there.

HRLead: Yeah, so the real trigger isn't the verbal yes, it's the signed offer landing back in our system. That's the moment everything fires. Recruiting hands it to us, the signature hits, and that kicks off the whole machine. People think onboarding starts on day one — it actually starts the second that PDF comes back signed, sometimes weeks out.

Interviewer: Okay, and what's the first thing that happens?

HRLead: Background check and screening. Criminal, employment history, education verification, and for some roles a drug screen — depends on the role and honestly the jurisdiction, the rules vary. That all goes out to a vendor and we wait on results before we get too far.

Interviewer: And if something comes back bad?

HRLead: Then we branch off into adjudication, basically. An adverse result doesn't auto-rescind — we do an individualized review, loop in Legal, give the candidate a chance to respond. Sometimes it's a records mismatch and it clears. Sometimes it doesn't and we rescind. But the key thing is the moment a result is adverse, I pause everything downstream. You do not want to be provisioning a laptop for someone you're about to rescind.

Interviewer: Got it. Say it clears.

HRLead: It clears, and then there's the right-to-work piece — I-9, employment eligibility, E-Verify where it applies. Document collection. That has to be buttoned up before day one, it's a hard requirement, not a nice-to-have.

Interviewer: And then?

HRLead: And then the big one. We create the employee record in the HRIS — Workday, in our case, some shops run SAP. And I cannot overstate this: that record is the system of record. It's the spine. The instant it exists, it fans out and triggers everything else. IT, payroll, facilities — they're all watching for that record to appear. Nothing real starts until it's live.

Interviewer: So walk me through the "everything else." What fires off that record?

HRLead: So this is where it stops being a line and becomes, like, three things happening at once. The biggest mental shift for people is that provisioning is parallel, not sequential. So track one is IT — they spin up the email account, SSO, the identity in the directory, all keyed off that HRIS record.

Interviewer: And access to systems?

HRLead: Right, that's part of the same track but it's its own beast. Role-based access provisioning — and we run least privilege, so you only get what the role needs. And here's a handoff that matters: the manager has to approve the entitlements before they go live. IT doesn't just grant everything. So if the manager's slow to approve, access stalls, and the new person shows up to a half-working account.

Interviewer: What about the actual laptop?

HRLead: Hardware. Procured and shipped. And this forks on remote versus onsite — remote folks get the laptop shipped to their home with a day-one kit, onsite we stage it at their desk. And honestly? This is the step that breaks most often. The classic disaster is day one, the person logs on, and there's no laptop, or the laptop's there but access isn't provisioned. We've got an escalation path to expedite, but when it slips it's the most visible failure in the whole process. Nothing says "we don't have it together" like a new hire on day one with nothing that works.

Interviewer: You mentioned facilities too.

HRLead: Yeah, that's the parallel track for onsite folks. Facilities assigns the desk, and security handles the badge — physical building access, the right zones. For a fully remote hire that whole lane basically goes quiet, but for onsite it has to land in lockstep with everything else. Desk, badge, access — all converging on the same day.

Interviewer: And money — payroll, benefits?

HRLead: That's its own parallel lane. Payroll gets set up — tax forms, banking — and benefits enrollment opens. There's an elections window, the new hire picks medical, retirement, all of it. That one's on the employee to actually complete, so we nudge, but it runs alongside the IT and facilities stuff, not after it.

Interviewer: So all three of these are happening at the same time. How do you keep them from drifting apart?

HRLead: Honestly that's the whole job, and I'll come back to it because it's where things go wrong. But before day one we do pre-boarding comms — welcome note, logistics, here's your paperwork portal, here's what day one looks like. And by that point all three tracks need to be converging, because if IT or facilities is behind, the welcome email is writing a check the first day can't cash.

Interviewer: Then day one itself.

HRLead: Day-one orientation. Company intro, policies, and crucially we confirm the handoffs actually worked — can they log in, did the badge work. This is the merge point. All those parallel lanes join back up here. If they all landed, day one feels magic. If one didn't, day one feels like chaos.

Interviewer: And after orientation, who takes over?

HRLead: The manager, largely. They get the 30-60-90 plan — what ramp looks like over the first three months — and we assign a buddy or mentor, someone outside the reporting line for the new person to ask the dumb questions. Then role-specific training kicks in: the actual tools, the systems, how the job really gets done on that team.

Interviewer: Is that the same as compliance training?

HRLead: No, and people conflate them. Functional training is "how to do your job." Compliance training is the mandatory stuff — security awareness, code of conduct, anti-harassment, and in regulated industries a whole stack of industry-specific modules. That all lives in the LMS and it's tracked to completion. It's not optional and it's not vibes — there's a record.

Interviewer: What happens if someone just... doesn't do it?

HRLead: Then we're into the escalation loop. Reminders first, then it goes to the manager, and ultimately overdue compliance training can actually block system access. It keeps looping back until it's done. We can't just let it slide — if there's ever an audit, "we assigned it" isn't enough, it has to be completed.

Interviewer: You mentioned certifications earlier?

HRLead: For some roles, yeah. Where the role requires a certification or an attestation — regulated roles, certain technical or safety roles — they have to certify. And if they don't pass, that's a remediation and retake loop. And same as compliance, failing or not certifying can block or even revoke their access until they pass. So it's a real gate, not a formality.

Interviewer: And then you're basically done?

HRLead: Almost. We run 30, 60, 90-day check-ins — manager and HR — partly to confirm ramp, but honestly partly to catch the broken handoffs from earlier. That's often where we find out access was never quite right, or some training fell through. Then there's the probation or end-of-onboarding review, confirm they're performing and fully set up, and then they're fully ramped. Onboarding closed.

Interviewer: So if you had to name the one thing people get wrong about all this — what is it?

HRLead: It's that there's no single owner end to end. Everybody assumes someone else is holding the thread. HR thinks IT's got the laptop, IT thinks the manager approved access, the manager thinks HR sent the welcome packet — and because it's all running in parallel across four or five teams, the failures don't show up until they collide on day one. People think onboarding fails because of one big dropped ball. It almost never does. It fails because of a dozen tiny handoffs between functions that each assumed someone else owned them. The work isn't the steps — every team can do their step. The work is the seams between the steps, and almost nobody actually owns the seams.

Interviewer: That's a great place to end. Thank you.

HRLead: Anytime. Make the seams somebody's job — that's the whole secret.