Ownsteps

Ownsteps / Guides

Employee training manual template: write one new hires can follow without you

Reviewed .

A training manual is what a new hire opens when you are in a meeting. If it only lists policies and org charts, they will interrupt you anyway. A manual that works is organised around tasks: what the person will actually be asked to do in their first weeks, in the order they will meet it, with a way to tell whether they did it right.

This guide gives a template you can copy, a short worked example, and a review test. You can build it in any document editor.

Training manual, SOP or onboarding checklist?

An SOP describes one task. An onboarding checklist tracks whether things happened (laptop issued, accounts created). A training manual sits between them: it teaches a role by sequencing tasks, linking to the SOPs for each, and saying what "good" looks like at the end of each week. Keep the detailed steps in SOPs (see the free SOP template) and let the manual point to them, so one change updates one place. For the access and decision points a newcomer trips on, see how to document a process for new hires.

Training manual template

TRAINING MANUAL: [role name]
Owner: [role]    Last reviewed: [date]    Applies to: [team / tools / version]

1. WHAT YOU WILL BE ABLE TO DO
- 3 to 5 outcomes, each starting with a verb
  (e.g. "Process a standard refund without asking for help")

2. BEFORE DAY ONE
- Accounts and access to request (role names, not passwords)
- Who provides each, and how long it usually takes

3. FIRST WEEK PLAN
Day 1: [orientation tasks]
Day 2-3: [shadow + first supervised task]
Day 4-5: [first task done alone, reviewed]

4. TASK SECTIONS (repeat for each task)
Task: [name]
- When you do it (trigger, frequency)
- Link to the SOP
- What a correct result looks like
- Common mistakes and what to do
- Who to ask, and what to try first

5. WEEKS 2-4
- Which tasks are added, in what order
- What counts as ready for each

6. WHO TO ASK
- Question type -> person or channel

7. SIGN-OFF
- Table: task | demonstrated on [date] | checked by

Two parts carry most of the value. The outcomes let the new hire know what they are aiming at. The sign-off table turns "I think I've got it" into a short conversation with a checker, and tells you which tasks still need practice.

Example: a customer support agent, week one

A structure example. Replace the tools and names with your own.

  1. Outcomes: Answer a ticket using the saved replies; tag and route a ticket correctly; issue a standard refund under the approval limit; escalate a billing dispute.
  2. Before day one: Helpdesk seat, shared inbox access and refund tool access are requested through the team lead. Allow two working days for the refund tool.
  3. Day 1: Read the tone guide, shadow two live conversations, and tag five past tickets yourself against the answer key.
  4. Day 2-3: Answer tickets in draft mode; your lead reviews each reply before it is sent.
  5. Task section, standard refund: Do it when an order is under 30 days old and under the approval limit. Follow the refund SOP. Correct result: the refund shows as pending in the payments tool and the customer receives the confirmation email. Common mistake: refunding the wrong order line. If the amount is over the limit, stop and ask the lead.
  6. Day 4-5: Send replies directly; leads spot-check five a day.
  7. Sign-off: The lead and the new hire complete the table together on Friday.

Write it so the new hire does not need you

Test it with the next hire

The first person to use the manual is your test. Ask them to note every moment they got stuck or had to ask someone, and fix the manual that week while the question is fresh. After the first hire, record the date in "Last reviewed". A manual no newcomer has followed is a draft.

Adding screenshots for browser tasks

Many tasks are clicks in a web application, and a screenshot of the exact screen answers what words cannot. You can capture them manually. Ownsteps is a Chrome extension that records webpage clicks, takes a screenshot at each, and builds an editable step-by-step guide on your computer; you can edit titles, delete detours, black out private areas and export Word, PDF, HTML or Markdown. It does not capture desktop applications, terminals or remote sessions, so steps outside the browser need manual notes. Check each screenshot for customer names, tokens in the URL and notifications before sharing; see the redaction checklist.

Keep it current

Give the manual an owner and a review date, and tie updates to events: a tool change, a policy change, or a new hire's question the manual could not answer. For a procedure that is not a role but a situation, see the IT runbook template; for filled-in procedures, SOP examples; for when someone leaves, the employee handover document.

Review checklist