Training and Onboarding Roadmap Template: A 90-Day Plan in 6 Phases

7 min read ยท 2026-10-09

A training and onboarding roadmap template is a plan that takes a new hire from signed offer to working on their own. It splits the first 90 days into phases, gives each phase concrete steps, and ends each one with a milestone the manager and the new hire can both check. The template below has six phases. It starts two weeks before day one and ends with a review in week 13.

Onboarding can go wrong without anyone noticing. The laptop arrives late, the training is a pile of documents, and nobody says what "good" looks like by the end of month two. A roadmap fixes this because it makes three things visible to everyone: what the new hire learns, when they learn it, and how you will know it worked. Use the phases as they are, then change durations and steps to fit the role.

The roadmap at a glance

Goal: A new hire who works on their own in their role, knows the team and tools, and has a written development plan for the next six months. Duration: About 15 weeks (2 weeks of preboarding plus a 13-week first quarter)

  1. Preboarding (2 weeks before day one)

    Remove every practical blocker before the first morning.

    • Order the laptop, accounts and access the role needs, and test the logins.
    • Send a welcome email with the start time, the address or video link, and the first-day schedule.
    • Name an onboarding buddy who is not the new hire's manager.
    • Prepare a short reading list: team page, product overview, and one recent project summary.
    • Block 30 minutes in the manager's calendar every day of week one.

    Milestone: On day one, the new hire logs into every core tool in the first hour without opening a support request.

  2. Orientation (Week 1)

    Help the new hire understand the company, the team and their own role.

    • Run a welcome meeting that explains the mission, the customers and how the team makes money.
    • Walk through the role description and agree on what success looks like at 30, 60 and 90 days.
    • Book short meetings with the five to eight people they will work with most.
    • Finish required training such as security, privacy and company policies.
    • End the week with a 30-minute check-in on questions and blockers.

    Milestone: The new hire can explain in their own words what their team does and who to ask for what.

  3. Core Role Training (Weeks 2-4)

    Teach the skills, tools and processes the role uses every day.

    • Follow a training schedule with one topic per day or half day, not everything at once.
    • Shadow a teammate on real work: calls, tickets, code reviews or client meetings.
    • Complete hands-on exercises in each main tool, using a test account or sample data.
    • Write a personal "how we do things here" note and have the buddy review it.
    • Hold a weekly one-to-one with the manager to review progress against the plan.

    Milestone: The new hire completes a short practical check, such as handling a sample task from start to finish, and the manager signs it off.

  4. Guided Practice (Weeks 5-8)

    Move from watching to doing, with support close by.

    • Assign a first real piece of work with a clear scope and deadline.
    • Pair on tasks first, then let the new hire lead while a teammate reviews.
    • Collect feedback after each task, not only at the end of the phase.
    • Add the new hire to the team's normal meetings and rotations.

    Milestone: The new hire delivers one complete piece of real work that meets the team's usual quality bar.

  5. Independent Work (Weeks 9-12)

    Let the new hire own their work, with less day-to-day review.

    • Hand over a recurring responsibility they now own fully.
    • Reduce reviews to spot checks and agreed key moments.
    • Ask them to suggest one improvement to a process, a document or the onboarding itself.
    • Move one-to-ones back to the team's normal rhythm.

    Milestone: The new hire runs their main tasks for two weeks in a row without needing step-by-step help.

  6. Review and Development Plan (Week 13)

    Close onboarding formally and plan the next stage of growth.

    • Hold a 90-day review against the success criteria set in week one.
    • Collect short written feedback from the buddy and two teammates.
    • Ask the new hire to rate the onboarding and list what was missing.
    • Write a development plan for the next six months with two or three skill goals.

    Milestone: A signed 90-day review and a written development plan are saved where both the manager and the new hire can find them.

How to Adapt the Template to the Role

The six phases work for almost any job. What changes is the content of core role training and the type of work in guided practice. A support agent learns the ticket tool and the tone of voice. An engineer learns the codebase, the deploy process and the review rules. A salesperson learns the product, the pitch and the CRM.

Change durations based on how complex the role is, not on seniority alone. A senior hire may need less skills training but more time to learn the context: past decisions, key relationships and current projects. A junior hire in a simple role may finish core training in two weeks.

  • Customer-facing roles: add listening to real customer calls in week 2 and a supervised first conversation in week 4.
  • Technical roles: add a local setup task in week 1 and a first small change shipped in weeks 3 to 5.
  • Managers: add one-to-ones with each direct report in week 1 and a team health review in week 6.
  • Remote hires: add a live video tour of the tools and more frequent short check-ins in the first two weeks.

Who Owns Each Part of Onboarding

Onboarding stalls when everyone thinks someone else is doing it. Give every phase one owner. The others help, but one person makes sure the milestone happens.

A simple split works for most teams. HR or operations owns preboarding and required training. The manager owns the role plan, the one-to-ones and the 90-day review. The buddy owns the informal questions, the "how things really work" side, and checks the new hire's notes. The new hire owns their own learning log and the feedback at the end.

  • HR or operations: accounts, equipment, contracts, policy training.
  • Manager: success criteria, schedule, real work assignments, reviews.
  • Buddy: daily questions, introductions, shadowing sessions.
  • New hire: learning notes, questions, onboarding feedback.

How to Build the Training Content

You do not need a full course to train a new hire well. Start from what the person must be able to do by week 8, then work backwards. Each skill gets one short explanation, one example and one exercise. Keep the explanation short and spend most of the time on practice.

Reuse what already exists before writing anything new. Recorded demos, past project files, team wikis and checklists are often enough. Store everything in one place, such as a shared folder or a Notion page, and link it from the roadmap step where it is needed. Ask each new hire to flag outdated material, and update it after every onboarding.

  • Write one page per core process: what it is, when it happens, who is involved, and the steps.
  • Record short screen videos of the main tools instead of long written guides.
  • Create a sample task for the week 4 check with a clear answer.
  • Keep a list of the questions new hires ask most and add the answers to the docs.

How to Know If Your Onboarding Works

The milestones are your first measure. If a new hire reaches each one on time, the plan is working. If several people get stuck at the same phase, the problem is the plan, not the people. Look at that phase first.

Add two simple signals. First, ask each new hire a few fixed questions at day 30 and day 90, such as "Do you know what is expected of you?" and "What did you need that you did not get?" Second, ask the manager when the new hire first worked on their own. Compare these answers across hires over time and change the roadmap where the same gaps show up.

Turning the Template Into a Visual Roadmap

A list in a document works, but a visual roadmap is easier to share on day one. The new hire sees the whole quarter on one screen, the manager sees where each person is, and HR can copy the same plan for the next hire. Put the six phases on a timeline, add the steps under each one, and mark the milestones clearly.

Keep one master version and one copy per hire. Change the copy for the role and the start date, but do not edit the master every time. After every few hires, update the master with what you learned. You can also build it in a spreadsheet or in PowerPoint if your team already uses them.

Common mistakes to avoid

  • Starting the work on day one leaves the new hire waiting for access, so set up every account during preboarding and test it.
  • Giving all the training in week one overloads people, so spread core topics over weeks 2 to 4 with one topic at a time.
  • Leaving success vague makes reviews feel unfair, so write the 30, 60 and 90 day criteria in week one and share them.
  • Making the manager the only contact slows questions down, so name a buddy before day one.
  • Stopping support after the first month leaves people stuck in guided practice, so keep weekly one-to-ones until week 8.
  • Never updating the template repeats the same gaps, so review the master roadmap with feedback from each new hire.

Frequently asked questions

What is the difference between training and onboarding?

Onboarding is the full process of bringing a new person into the company, from paperwork to team culture. Training is the part that teaches the skills and tools of the role. A good roadmap combines both, so the new hire learns the job while they settle into the team.

How long should an onboarding roadmap be?

A first quarter of about 90 days fits most roles, plus one or two weeks of preboarding. Simple roles may reach independent work sooner. Complex or senior roles may need a longer guided practice phase.

What should a new hire do in the first week?

The first week is for orientation: tools access, meetings with key teammates, required training and a clear picture of the role. Avoid real deadlines in week one. End the week with a check-in to answer questions and fix blockers.

Can I use the same template for remote employees?

Yes. Keep the same six phases and add more structure for distance: a live video tour of the tools, short daily check-ins in the first two weeks, and scheduled virtual coffees with teammates. Make sure equipment ships early enough to arrive before day one.

Who should create the onboarding roadmap?

The hiring manager should build the role-specific parts, because they know the work and the success criteria. HR or operations usually provides the shared parts, such as preboarding and policy training. The buddy and recent hires are useful reviewers for what is missing.

Generate this roadmap with AI