Overview
A new hire starts Monday morning. The I-9 is legally due by Wednesday end of day, but the HR ops person who handles I-9 completion is managing two other urgent files and sends a reminder on Thursday. IT access was requested by the recruiter, not HR ops, and the ticket is sitting in a queue nobody is watching. The manager's week-one integration plan exists as a slide deck borrowed from someone else's last hire. None of this is visible as a problem from any single person's vantage point. The first clear signal that something went wrong arrives months later, in a workplace audit, a benefits dispute, or a compensation claim that asks you to reconstruct exactly what happened in the first two weeks.
The structural problem is that onboarding spans multiple teams, HR, IT, the hiring manager, payroll, and the new employee, with no shared execution layer. Each team completes their portion in isolation, with no visibility into what the others have done, what is blocking completion, or whether the overall process is on track for legal deadlines.
Building a single-run onboarding Flow across teams
The fix is a single onboarding run that spans every team. HR handles pre-boarding: document collection and contract approval. IT owns day-1 access and equipment setup. The manager is accountable for the integration plan, team introductions, and the 30-day checkpoint. All in one timeline, visible to everyone with a stake in the hire.
Every step has a named owner and a due date relative to the start date, not a fixed calendar entry. Relative dates ('due 3 business days after start date') make the same template reusable across every hire without manual rescheduling. High-risk tasks also carry mandatory evidence fields; the step doesn't close without proof.
Compliance evidence requirements by role and jurisdiction
Compliance exposure varies by role and jurisdiction, but the structure of the requirement is consistent: specific tasks must happen in specific sequences with specific proof attached. I-9 verification requires both sections completed within the legal window, not a scan dropped into a folder after the fact.
Harassment prevention and safety orientation carry completion deadlines in most jurisdictions, and a log entry isn't enough if it can't be tied to a specific session with that employee's name on it. Role-specific safety training, working at heights, electrical safety, confined spaces, typically requires documented hours and signed attendance. Each of these becomes a task with a mandatory evidence field and a deadline the system tracks, not a note in a spreadsheet someone updates when they remember.
The 30/60/90-day checkpoint structure
The 90-day period is where most onboarding processes collapse. After the logistics of day 1, there is no structured follow-up to confirm integration completeness, training coverage, or regulatory requirements met within the probationary window.
A structured 30/60/90-day checkpoint cadence, built as recurring subtasks in the same onboarding Flow, ensures continuity without depending on manager memory. Each checkpoint has a defined deliverable: role clarity and open blockers at 30 days, performance against early objectives at 60, and the probationary period decision at 90. The manager cannot mark the checkpoint complete without a recorded outcome.
What onboarding data reveals about your operation
The most useful thing structured onboarding data reveals is rarely what HR leadership expects. Most teams assume IT access provisioning is the slowest-running task. The data consistently shows a different answer: the manager's integration deliverables, the section HR has the least direct control over, accumulate the most delay, typically by a factor of two or three against every other stage.
That finding does not come from intuition or end-of-cycle retrospectives. It comes from timestamps on every phase, aggregated over dozens of runs, and compared across departments and roles. The insight is available from day one, but only if the onboarding has been structured enough to generate it.