Structure it as four horizons with a named owner for every item: before day one, day one, the first week, and the first months. IT provisions access, HR handles paperwork and policy, the manager owns ramp goals, a buddy answers the small questions. Add checkpoints early enough to catch a struggling hire while it is fixable.
The gap between offer and joining is where hires get lost, so treat it as part of the programme rather than dead time. Collect documents and complete background checks early, confirm the joining date in writing, and keep contact warm with something useful rather than a generic welcome mail. Order equipment against a lead time you have actually measured, raise the access requests, book the induction slots, and tell the team who is arriving and what they will be working on. Assign the buddy now, not on the morning. [Onboarding software](/employee-onboarding-software) helps here mainly by making the pre-joining checklist visible to everyone who owns a piece of it, instead of living in one person's head.
Day one should end with the person able to get into what they need, knowing who their manager and buddy are, and having met the immediate team. It should not be a policy marathon. Handbook reading, benefits enrolment and compliance modules can spread across the first weeks; front-loading them wastes the one day when somebody is most receptive to the human parts of the job. Have the desk, the laptop and the accounts ready before they arrive, because a first day spent waiting for access sends an unmistakable message about how organised the place is. Lunch with the team is not a nicety; it does more than the policy deck.
Orientation to the work rather than to the organisation: what the team is responsible for, what is currently in flight, who depends on whom, and where the documentation lives. Introduce the systems they will actually use, in the order they will use them, and get them to complete one real task, however small, before the week ends. Cover the administrative essentials they need in order to function, which mostly means recording time, requesting leave and updating their own details; walking them through an [employee self-service portal](/employee-self-service-portal) once, properly, saves months of small questions. Close the week with a manager conversation about what was confusing, while it is still fresh enough to name.
Write them before the person joins, in terms of outputs rather than activities, and pitch them at the first month, the first quarter and the end of probation. A support hire might be handling routine tickets unaided by the end of the first month; an engineer might have shipped a change to production; a salesperson might be running discovery calls alone. Vague goals such as understanding the product are unassessable and let both sides avoid the difficult conversation. Share the goals with the person on day one so ramp is a shared plan rather than a private assessment. Where a bar has to be cleared at the end of probation, say what that bar is at the start.
IT owns provisioning and access, HR owns paperwork, policy and the record, the manager owns the work and the ramp goals, the buddy owns the small questions people are embarrassed to ask a manager. Put a name against every item rather than a department, because a task owned by a department is owned by nobody and the failure always looks the same: the laptop that arrived a week late, the system access nobody requested, the policy sign-off that surfaced two months on. Give the manager a checklist that is theirs alone, since the manager's items are the ones most often assumed to be somebody else's.
Short, scheduled conversations at the end of the first week, the first month and before the probation decision, each with a specific question rather than a general enquiry about how it is going. Ask what they expected that has not turned out to be true, what they are still unclear about, and what is blocking them. Add a channel that is not the manager, usually the buddy or HR, because somebody struggling with their manager will not raise it with their manager. The probation decision should never be the first time concerns are voiced; if it is, the checkpoints were being held but nobody was listening.
Everything promised during interviews sets the expectation the first months get measured against, so a mismatch between the pitch and the job is an onboarding problem created upstream. Carrying the hiring context forward also saves work: the scorecard used to assess the candidate describes the strengths and gaps a ramp plan should address, and details already collected during hiring should not be requested again on day one. Pitch N Hire is an applicant tracking system with a free one-user plan, and like any [applicant tracking system](/ats) its value at this point is that the hiring record sits in one place when the manager finally sits down to write the plan.
Pitch N Hire is an applicant tracking system built for recruiters and hiring teams. If this answer described something you want to run properly, the ATS is where it lives.
Free for 1 user · No credit card · Talk to a real hiring expert
Get a personalized walkthrough of Pitch N Hire on your own roles and workflow. No slides, no obligation.
Prefer to talk? Book a demo · Talk to sales · View pricing
Free 1-user plan · No credit card · Talk to a real hiring expert
See your true cost-per-hire and how much Pitch N Hire could save you — our free Recruitment ROI Calculator gives you the numbers in under a minute. No signup required.
Open the free ROI calculatorPrefer a tailored walkthrough on your real roles? Drop your work email:
★ Free 1-user plan · No spam · Talk to a real hiring expert
