How to Onboard Your First Employee: A 90-Day Plan

Why the first ninety days matter more than the interview

It is easy to treat the moment someone accepts an offer as the finish line of the hiring process, when in practice it is closer to the starting line of the part that actually determines whether the hire succeeds. A capable person can fail in a role purely because nobody planned their early weeks properly: no clear plan for the first day, no structure for the first week, and no defined path from 'learning the ropes' to 'genuinely contributing'. This is entirely within a founder's control to prevent, and it costs far less time to plan than it does to recover from a failed onboarding once someone is already unhappy or underperforming.

The plan below is deliberately built around three horizons: the first day and week, when the goal is orientation and confidence; the first month, when the goal is building genuine competence in the core of the role; and months two and three, when the goal is independence and a formal review against the standards you set when you designed the role.

Before they start

A surprising amount of onboarding success is determined before the person's first day at all. Make sure their contract, any policies they need to sign, and practical items like equipment, email accounts, system access and a workspace are ready in advance, so their first morning is not spent waiting for you to set things up that should already exist. Confirm PAYE registration and payroll arrangements are in place well ahead of their first pay date, since setting these up at the last minute risks a delayed or incorrect first payment, which is a poor start to any working relationship.

Prepare a simple written first-week plan and share it with them before or on their first day. Knowing roughly what to expect — who they will meet, what they will learn, what they will actually be doing by day three or four — reduces the natural anxiety of starting somewhere new, and signals that you have genuinely thought about their arrival rather than expecting them to find their own way.

• Contract, policies and any required forms ready to sign on or before day one.
• Equipment, system access, email and login details set up in advance.
• PAYE and payroll arrangements confirmed well ahead of the first pay date.
• A written first-week plan shared with the new hire before they arrive.
• Workspace, or remote-working setup, sorted and ready.

Day one and week one

Day one should cover the practical basics: a proper welcome, a tour of how the business actually operates day to day, introductions to anyone else involved, and a clear run-through of what the first week will look like. Resist the temptation to hand over real, unsupervised work immediately; the first day is for orientation, not output, and treating it that way sets a calmer, more confident tone than throwing someone into the deep end on day one.

Across the rest of the first week, focus on structured learning paired with small, low-risk tasks that let the person start applying what they are learning under light supervision. This is also the point to introduce the documentation of how core tasks are done, if you have any, or to start capturing it together if you do not. A short daily check-in, even five or ten minutes, at the end of each day in week one gives both of you a chance to catch small confusions before they compound.

1. Day one: welcome, orientation, introductions, systems set up, expectations for the week explained.
2. Days two to three: structured learning of core processes, paired with observation of real work.
3. Days three to five: first small, low-risk tasks completed with support nearby.
4. End of each day in week one: a brief check-in on what went well and what was unclear.
5. End of week one: a short review of how the week went against the plan you shared in advance.

The first month: building real competence

Through weeks two to four, responsibility should build steadily rather than jump straight from 'watching' to 'fully independent'. A useful structure is to move a new hire through a sequence: observing you do a task, then doing the task with you watching and available to help, then doing the task independently with a review afterwards, then finally doing the task independently with only periodic spot-checks. Skipping straight from observation to full independence is one of the most common causes of early mistakes, not because the person is not capable, but because they were never given a supported middle step.

Continue with scheduled check-ins through the first month, ideally weekly rather than only when something goes wrong. Use these to review specific pieces of work against the standards you wrote when you designed the role, give direct feedback, and ask what is unclear or unsupported. A new hire who has to seek you out to ask for feedback is far less likely to raise a small problem early than one who knows a scheduled moment for that conversation already exists.

Months two and three: independence and review

By the second month, the core of the role should be moving from supported to independent, with your check-ins shifting from close, task-level review towards a broader conversation about how things are going overall. This is also the point to start handing over more of the judgement calls within the role, not just the execution, assuming the earlier weeks have shown that the fundamentals are solid.

Around the end of the probation period, run a proper, structured review against the 30/90/180-day success measures you wrote when you designed the role. This should not be a vague conversation about vibes; it should look specifically at what was expected by this point and what has actually been achieved, discuss any gaps honestly, and agree what happens next, whether that is confirming the role, extending probation with a clear plan, or, in the minority of cases, concluding that the fit is not right.

A probation review with no written success measures to check against is not really a review; it is a guess dressed up as one.

What good onboarding actually prevents

The value of a proper onboarding plan is best understood by what it prevents: a new hire quietly struggling because they were never told what good looked like, small early mistakes compounding because nobody caught them in week one, and a founder concluding by month three that the hire 'is not working out' when the actual problem was an absence of structure in the first weeks rather than any real deficiency in the person. Most onboarding failures are recoverable if caught early, which is precisely what a written plan and regular scheduled check-ins are designed to achieve.