How-to guides

How to create a training manual for software and process tasks

To create a training manual for employees, write one page per task and keep every page in the same shape. This guide gives you a template to copy, a filled-in example, and the setup in Word or Google Docs.

Updated

How-to guides

Facts checked on 21 November 2026 against each vendor's own pages.

Short answerDecide whether the manual is for looking things up or for learning before day one. List the tasks each role does. Write one page per task from the same seven-part template, with numbered steps of one action each. Build it in Word or Google Docs with heading styles, give every page an owner and a date, and add practice alongside, because reading a step and doing it are different skills.

Decide what the manual is for

Most manuals that nobody opens were written to be two documents at once. A reference manual is opened in the middle of a task by someone who is stuck. A learning manual is read before someone starts the job. They need different shapes.

Reference manual, used while working
  • One page per task, found by the name of the task
  • Starts with the steps. Background goes at the bottom or is left out
  • Read in under two minutes
  • Lives where people already are: the intranet, a pinned link in Teams, the help menu
Learning manual, read before starting
  • Ordered by the working day or by the process from start to end
  • Explains why the process runs this way
  • Includes exercises with example data
  • Read once, usually in the first week

If you can only write one, write the reference. A first-week read fades, and the page will still be needed for the task someone does once a quarter. In Jakob Nielsen's 1997 reading study, 79% of test users scanned a new web page and 16% read it word by word, so write for the person scanning. There is more on help at the moment of need in just-in-time learning.

List the tasks by role

A manual organised by menu ("The Invoices screen") describes the software. A manual organised by task ("Post a supplier invoice") describes the job, and the job is what a new employee has to learn. Sit with one experienced person per role for an hour and list what they do, how often, and what happens when it goes wrong.

RoleTaskHow oftenIf it goes wrong
Accounts payable (AP) clerkPost a supplier invoice against a purchase orderDailySupplier is paid the wrong amount
AP clerkPark an invoice that is missing informationWeeklyInvoice sits unseen and is paid late
AP clerkReverse an invoice posted in errorMonthlySupplier is paid twice
AP supervisorRelease invoices blocked for paymentDailySupplier puts the account on stop
AP supervisorRun the payment proposalWeeklyThe whole payment run is late

The example is a finance team on SAP S/4HANA. Write the frequent and costly tasks first. A role usually needs 10 to 15 task pages. The same task list is the backbone of a software training plan.

A software training manual template: one page per task

Every task page has the same seven parts in the same order. A reader who has used one page then knows where to look on all the others. Copy this into your document and fill it in.

PartWhat to write
Task nameVerb first, in the words staff use. "Post a supplier invoice", not "Invoice processing".
1. PurposeOne sentence on what the task achieves and for whom.
2. When you do itThe trigger: an email arrives, a date passes, a status changes.
3. Before you startThe access, information and documents you need. Anything that must already be true.
4. StepsNumbered, one action per step, with the exact names of fields and buttons.
5. What you should seeThe message, status or number that proves it worked.
6. Common errorsThe two or three things that go wrong, the message shown, and what to do.
7. Who to askA role or a shared mailbox. A named person goes on holiday.
FooterPage owner, date last checked, and the software release it was checked against.

Here is the template filled in for the first task in the list.

Filled-in example

Post a supplier invoice against a purchase order (SAP S/4HANA, transaction MIRO)

Purpose: record what we owe a supplier so the invoice can be paid on its due date.

When you do it: a supplier invoice arrives in the accounts payable inbox and it quotes a purchase order number.

Before you start: the invoice open beside you, the purchase order number, and the goods receipt already posted by the warehouse.

  1. Open transaction MIRO.
  2. On the Basic data tab, enter the Invoice date printed on the supplier's invoice.
  3. In Reference, type the supplier's invoice number.
  4. In Amount, type the gross total from the invoice.
  5. Enter the tax amount and choose the tax code.
  6. On the PO Reference tab, type the purchase order number and press Enter.
  7. Check that each proposed line matches the invoice for quantity and amount.
  8. Check the Balance field. It must show 0.00 with a green light.
  9. Choose Post.

What you should see: a message at the bottom of the screen with the new invoice document number. Write that number on the invoice.

Common errors: Balance is not zero, which means the supplier's price or quantity differs from the order. Do not change the lines to force it. Park the invoice and email the buyer named on the order. A yellow light means the invoice will post but will be blocked for payment, so tell the supervisor.

Who to ask: accounts payable supervisor, ap.help@example.com.

Footer: owner, AP supervisor. Last checked 14 November 2026.

Your field names will differ. Take them from your own system with the screen open, never from memory or from a vendor's demo.

How to write steps people can follow

  • Start each step with a verb: Open, Choose, Type, Check.
  • Give each step one action. "Enter the date and the reference and press Enter" is three steps.
  • Use the exact label on the screen, capital letters included, so the reader can match the word to the button.
  • Say where before what. "On the Basic data tab, choose..." sends the eye to the right place first.
  • Put the result straight after the action that causes it: "Choose Save. The status changes to Released."
  • Keep a task to between 7 and 12 steps. Past 15, split it into two pages.
Weak stepBetter step
Fill in the header details as required.In Reference, type the supplier's invoice number.
Make sure everything is correct, then save.Check that Balance shows 0.00. Choose Post.
Navigate to the relevant purchase order.On the PO Reference tab, type the purchase order number and press Enter.

Short steps matter because the reader is holding the task, the screen and the page in mind together, and cognitive load theory describes how quickly that runs out. Then test the page. Hand it to someone who has never done the task, say nothing, and watch. Every place they hesitate is a step to rewrite.

Screenshots: use fewer than you think

Screenshots are the first part of a manual to go out of date. A manual of 60 task pages with 8 screenshots on each holds 480 images, and one release that moves a button can make dozens of them wrong. Once a picture does not match the screen, readers stop trusting the text beside it.

  • Use a screenshot only where the reader has to find something on a busy screen.
  • Crop to the part of the screen that matters and mark the one thing to click.
  • Capture with example data. No real customer, supplier or patient names.
  • Keep the image files in one folder, named by task and step, so replacing one takes minutes.

How to create a training manual in Word or Google Docs

Either works. What matters is using heading styles, because the contents list is built from them.

  1. Set up the template page once. Use Heading 1 for the role, Heading 2 for the task name, and bold labels for the seven parts.
  2. Add the contents list. In Word it is on the References tab under Table of Contents, and you right-click it and choose Update Field after adding pages. In Google Docs, set headings from Format, Paragraph styles, then use Insert, Page elements, Table of contents.
  3. Keep one live copy. PDFs saved to desktops are where old versions survive.
  4. In Google Docs, name a version in the version history after each review. Docs keeps up to 40 named versions of a document, and you can restore any of them.

Word suits a manual that has to be printed or signed off as a controlled document. Google Docs suits a manual that several people edit, because everyone is in the same copy. PowerPoint and Canva make handsome pages that are slow to update, so keep them for a one-page quick reference. If your LMS has to record who has opened the manual, the free PDF to SCORM converter wraps the PDF as a course the LMS can track.

How to create a training manual using AI or a capture tool

A chat assistant such as ChatGPT, Claude or Copilot will give you a first draft from words. Paste in your rough notes, or the transcript of an expert talking through the task, along with the template above, and ask for one action per step. It is good at structure and plain wording. It has not seen your screen, so some of the field names it writes will sound right and be wrong. Check every label against the system before anyone relies on the page.

A capture tool drafts from the screen instead, by watching you do the task. Scribe records your clicks through a Chrome or Edge extension and writes the guide as you go. Its free Basic plan allows up to 10 guides, and export to PDF, Word, HTML or Markdown is on the paid Pro plans. Tango does the same job, producing what it calls a "step-by-step guide with screenshots, highlights, and descriptions" that you can share by link, export to PDF or embed. For a written manual these are the right tools, because the document is what they make.

Recourse starts from the same kind of recording and makes something different: a simulation the learner clicks through, and a course around it. It does not produce a Word or PDF manual. The comparisons of iorad vs Scribe and iorad vs Tango cover the document tools in detail, and from screen recording to simulation covers the other route.

Whichever you use, a captured draft is a list of clicks. It does not know why a step exists, when the task applies or what goes wrong. Purpose, trigger, errors and who to ask still come from a person who does the job.

Keeping the manual current

  1. One owner per pageA role, written in the footer. Choose whoever hears first when the process changes. That is usually a team lead and rarely the training team.
  2. A date and a releaseEach page shows when it was last checked and against which version of the software.
  3. Known triggersReview the affected pages when the vendor ships a release, when a field or approval rule changes, and when the same question reaches the help desk three times.
  4. A quarterly walk-throughThe owner does each task with the page open and corrects whatever no longer matches. Allow five minutes a page.
  5. A change logOne line per change at the back: date, page, what changed. Readers who know the old way can see what is different.

What a manual cannot do

A manual records what to do. It cannot tell you whether anyone is able to do it. Someone can read the invoice page twice, feel ready, and still freeze at the Balance field on their first real invoice.

Research on study methods points the same way. A 2013 review of ten learning techniques by Dunlosky and colleagues rated rereading as low in usefulness and practice testing as high. For software, that means trying the task: in a training client, in a simulation, or beside a colleague. Hands-on training sets out the options, of which a software simulation is one. Keep the manual for what it does well: the task someone does twice a year and the step nobody remembers.

Where Recourse fits

When people have read the page and still need to try it

Recourse turns a screen recording of a task into a replica that people click through in three modes: Demo to watch, Practice to try with hints, and Evaluate, unaided and scored against a pass mark. It does not write your manual, and there is no Word or PDF output. The replica follows the one path you recorded, and it is not the live system or a sandbox. Free for 15 days with one seat and a watermark. Pro is $299 a month for up to three seats.

Start free

Questions people ask

What should a training manual include?
A contents list by role, one page per task, and a short section on who to ask for help. Each task page needs a purpose, the trigger for doing it, what you need before you start, numbered steps, what you should see when it has worked, common errors and a contact. Add an owner and a last-checked date to every page.
How do I create a training manual in Word?
Set up one task page using heading styles, save it as a template, and copy it for each task. Insert an automatic table of contents from the References tab, which Word builds from the headings, and update it when you add pages. Keep one live copy in a shared location so old versions do not circulate.
How do I create a training manual in Google Docs?
Use Format, Paragraph styles to apply headings, then Insert, Page elements, Table of contents. Give editing rights to page owners and comment rights to everyone else. After each review, name the version in the version history so you can see what changed and restore an earlier copy.
Can I create a training manual using AI?
Yes, for the first draft. A chat assistant can turn rough notes or a transcript into numbered steps, and capture tools such as Scribe and Tango write steps from your clicks. Neither knows why the task exists or what goes wrong, and a chat assistant may invent field names, so a person who does the job must check every page.
What is the difference between a training manual and an SOP?
An SOP states the approved way to carry out a process, often for audit or compliance, and is controlled and signed off. A training manual teaches people to do the tasks and can include explanations, examples and exercises. A user guide comes from the software vendor and describes features, not your process. In a small team one set of task pages can serve as both manual and SOP.
Is there a template for a software training manual?
Yes. Use one page per task with seven parts: purpose, when you do it, before you start, numbered steps with one action each, what you should see, common errors, and who to ask. The template and a filled-in example for posting a supplier invoice are on this page.
How long should a training manual be?
As long as the task list. A role usually needs 10 to 15 task pages, each one or two sides long. If the manual for one role runs past 50 sides, it is probably describing screens instead of tasks, or covering rare tasks that could wait.

Sources

Keep reading

Last reviewed 21 November 2026. Recourse publishes these guides for learning, customer education and change teams. Details drawn from public sources can change.