In this guide 6 sections
Split onboarding into three windows: before day one, day one and the first month. Give every task an owner, such as HR, the hiring manager or IT. Cover documents, system access, equipment, a training plan and a probation goal review, and tick each item off in writing.
Before day one: paper, access and a desk
The moment the offer is signed, HR collects the joining form, identity proof, address proof, education certificates, previous employer letters and bank details. Missing papers are chased now, not in week three.
IT creates the email account, the laptop image and the logins for the tools the role needs. The hiring manager books a desk or a locker. Facilities issues an access card. A laptop ordered on the joining day arrives a week later, so raise the equipment request when the offer is countersigned and confirm the delivery date.
Send the new person a short note with the start time, the dress code, the reporting contact and what to bring.
- Joining form and identity documents
- Email account and tool logins
- Laptop, phone or workstation
- Desk, access card and parking
- Welcome note with day one plan
Day one: welcome, setup and one real task
Someone meets the new hire at reception. A buddy, not the manager, shows the floor, the canteen, the printer and the way to book a meeting room.
HR runs a short session on leave rules, attendance, working hours, the code of conduct and the safety rules. Policies are signed for. Emergency contacts are filled in. Keep the policy session practical, with the safety drill, the leave application route and the complaint channel shown on screen, instead of reading the handbook aloud for two hours.
IT checks that every login works while the person is sitting there. End the day with one small real task. A role with no task on day one feels unwanted by Friday.
- Buddy assigned
- Policy acknowledgements signed
- Logins tested in person
- First small task given
Week one to four: training and early feedback
The hiring manager writes a thirty day plan. It lists the people to meet, the systems to learn, the documents to read and the first deliverable. Share it on day one. A good plan names the colleagues from sales, accounts and the warehouse whom the new person must meet in the first fortnight, with a line on why.
Training sessions are booked, not left to chance. Product knowledge, process walkthroughs and tool training each get a date and a trainer.
Hold a short one to one at the end of each week. Ask what was unclear, what is missing and who has helped most. Write down the answers.
Set probation goals people can actually measure
Agree three to five goals before the end of week two. Each should name an output, a standard and a date. Learn the billing module is vague. Raise ten invoices unaided by the third week is clear.
Review progress at the midpoint of probation, in writing. Both sides sign. If something is off track, there is still time to fix it. Write the midpoint review on a single page with the goal, the evidence and a rating, so the final probation decision surprises nobody.
Gaps in the review often trace back to onboarding. A missing login or a late laptop is the company’s miss, not the employee’s.
- Goals with output and date
- Midpoint review form
- Manager and employee signatures
- Training gaps noted
Close the loop at thirty days
At the end of the first month, HR holds a feedback talk with the new hire. Ask what the company did well and what it missed. Use the answers to edit this checklist.
Confirm that the file is complete: documents, policy signatures, access list and training log. Ask IT to remove any access the role does not need. Remove temporary access granted during setup, such as shared mailboxes or test accounts, because forgotten permissions are how a new joiner ends up seeing salary files in week two.
Pick one task that slipped this time and name the owner who will fix it before the next joiner arrives.
Onboarding tracker sheet
Three column groups cover before day one, day one and first month, all on one printed page. Rows hold tasks such as documents, email, laptop, access card, policy signing, buddy, training sessions and probation goals. Each row has an owner, a due date and a done tick. A footer carries the thirty day feedback notes.
Open a blank worksheet to printQuestions owners ask
Who owns onboarding, HR or the manager?
Both, with split tasks. HR owns documents, policies and records. The manager owns the work plan, training and probation goals. IT owns equipment and access. Name each owner on the checklist. When nobody is named for a task, it is usually the task that gets skipped, and the new hire pays for it in week one.
When should system access be created?
Before day one, as soon as the offer is accepted. Test every login on the first morning. Waiting for the person to arrive wastes their first days. Where the role touches finance or customer data, ask the approver to confirm the exact permissions in writing.
How long should onboarding last?
Plan for the first month at minimum, with a review at the end of probation. Some roles, such as technical or field jobs, need a longer ramp with staged targets.
What should we do if a joiner does not turn up?
Keep a contact log, then close the file and revoke the accounts created. Tell IT and facilities so equipment and cards are returned to stock.