How-to guides

Software training plan template, with a filled-in example

A training plan for a new system answers six things for each group of people: who they are, which tasks they will learn, in what format, who owns it, when it happens and how you will know it worked. The template below is filled in for one example rollout, so you can copy it and swap in your own roles and dates.

Updated

How-to guides
Short answerA software training plan has four working parts: a plan table with one row per role, a role and task matrix, a week-by-week timeline around go-live, and a checklist. All four are on this page, filled in for an ERP go-live with 310 users. Select any table, copy it and paste it into Excel or Google Sheets.

The example rollout

Say you are the training lead at a food distributor that is replacing its order and stock system with a new ERP at a head office and two warehouses. Go-live is Monday 1 March 2027. Every number below belongs to this made-up company.

310People to train

Everyone who will get an account on day one.

6Roles

Grouped by the job people do.

59Tasks to train

Between 4 and 14 per role.

12Super users

Two per role, trained seven weeks before go-live.

If you have not yet decided which tasks to train or which format suits each one, start with how to train employees on new software. This page shows how to write those choices down.

Part 1: the plan table

One row per role. This table is the plan, and the rest of the document supports it.

Audience and roleTasksFormatOwnerDatesHow you will check it worked
Order desk, 60 people12 tasks, including enter a sales order, amend an order, check stock and price, raise a credit note30-minute process briefing online, then a simulation for each task. Scored check on 4 tasks.Order desk team leader8 to 19 February90% pass the scored check by 24 February. Order lines needing correction in week 2 after go-live.
Warehouse, 130 people8 tasks on the handheld: receive goods, put away, pick, pack, dispatch, count stock90-minute hands-on session on training handhelds, in groups of 10. A laminated one-page guide at each station.Warehouse supervisors15 to 26 February, by shiftEach person completes a receipt and a pick unaided, signed off by a supervisor. Mis-picks per 1,000 lines in weeks 1 to 4.
Purchasing, 30 people10 tasks, including raise a purchase order, convert a requisition, add a supplierDemo and simulation for each task. One 60-minute live session on exceptions.Purchasing manager8 to 19 FebruaryScored check on raising a purchase order. Share of orders raised in the system instead of by email, in week 4.
Accounts payable, 20 people14 tasks, including post a supplier invoice, match it to the order and receipt, run a payment proposalSimulation for each task. Payment run rehearsed with a super user in the training environment.Finance systems lead8 to 24 February80% pass mark on invoice posting and the payment run before live access. Invoices posted without correction in week 2.
Finance: receivables and ledger, 25 people11 tasks, including allocate a customer payment, post a journal, close the monthSimulations for the daily tasks. Month-end close rehearsed as a group.Financial controller15 to 26 February. Rehearsal 22 to 26 March.Days taken to close March, against the target the project set.
Managers who approve, 45 people4 tasks: approve a purchase order, approve a credit note, find the team's open items, run one report15-minute recorded demo, a one-page guide and one drop-in session.Training lead22 to 26 FebruaryApprovals left waiting more than two days, in week 2.

Check the arithmetic before anyone else does. The headcounts add up to 310, the tasks to 59, and 13 sessions of 10 cover all 130 warehouse staff.

The column people leave blank

"How you will check it worked" is the hardest cell to fill. Fill it before the training is built, because the check decides the format. If the test for accounts payable is an unaided invoice posting with a pass mark, a slide deck cannot be the training.

Part 2: the role and task matrix

The matrix sits behind the plan table. Tasks go down the side, roles across the top, and each cell says how that role meets that task. This extract shows 8 of the 59 tasks.

TaskOrder deskWarehousePurchasingAccounts payableFinanceManagers
Enter a sales orderDaily
Raise a credit noteSometimesSometimesApproves
Receive goods against a purchase orderDaily
Pick and dispatch an orderDaily
Raise a purchase orderDailyApproves
Post a supplier invoiceDaily
Run a payment proposalSometimesApproves
Close the monthSometimesSometimes

Read down a column and you have that role's training list. Read across a row and you see who needs to understand each other's step: the credit note touches three roles. Microsoft's implementation guide for Dynamics 365 recommends the same device: a matrix of training roles against subject areas.

Part 3: the week-by-week timeline

The timeline runs from eight weeks before go-live to four weeks after. End users train in the last three weeks, so the tasks are still fresh on day one.

  1. Week -8, from 4 JanuaryAgree roles, tasks and headcounts

    Walk each process owner through the matrix and get it signed off. Name two super users per role.

  2. Week -7, from 11 JanuaryTrain the super users

    Two days on the system for all 12. From now on they review every lesson for their role.

  3. Week -6, from 18 JanuaryStart building materials

    Begin with the daily tasks of the largest roles. Book rooms, handhelds and people's time with their managers.

  4. Week -5, from 25 JanuaryPilot with super users

    Each super user works through two finished lessons and reports what is unclear. Fix the pattern before building the rest.

  5. Week -4, from 1 FebruaryFinish materials and publish the schedule

    The training environment is loaded with realistic customers, suppliers and stock. Managers tell their teams the dates in person.

  6. Week -3, from 8 FebruaryOffice roles begin

    Order desk, purchasing and accounts payable start, in sessions of an hour or less.

  7. Week -2, from 15 FebruaryWarehouse and finance begin

    Thirteen warehouse sessions run across the shifts over two weeks. Scored checks open for the office roles.

  8. Week -1, from 22 FebruaryManagers, catch-up and the readiness report

    Catch-up sessions run Monday to Wednesday. Scored checks close on Wednesday 24 February and the readiness figures go to the steering group on Thursday.

  9. Go-live week, from 1 MarchSupport on the floor

    A super user sits with every team and covers every warehouse shift. A 15-minute call at 4pm each day goes through the questions, tagged by task.

  10. Week +1, from 8 MarchFix the top five

    Rewrite the guides and rerun the lessons for the five tasks with the most questions. Floor support continues.

  11. Week +2, from 15 MarchTake the first measures

    Compare order corrections, mis-picks and invoice corrections with the plan table. Follow up anyone who has not yet done a key task live.

  12. Week +3, from 22 MarchRehearse month end

    Finance walks through the close in the training environment before doing it for real on 31 March.

  13. Week +4, from 29 MarchReview and hand over

    The first live month end. Write up the measures and name who owns the materials and new-starter training from here.

Two dates are worth defending when the project is under pressure. Super user training in week -7 gives you reviewers and floor support. The day the scored checks close gives the steering group a readiness number while there are still four days to act on it.

Part 4: the checklist

Run through this before you send the plan for sign-off.

  • Every role has a named owner, and for most rows it is someone other than the training lead
  • Headcounts add up to the number of accounts being created (310 here)
  • The last column holds a number or a named sign-off for every role
  • Rooms, devices and the training environment are booked, and the environment has realistic data
  • Line managers have agreed the hours in writing
  • A refresher is planned in case go-live moves by more than two weeks
  • Someone owns the materials after week +4

What else the document should say

A formal plan document wraps a few short sections around the four parts. Microsoft's guide lists the elements as objectives, scope, audience, schedule, delivery approach, validation of success, assumptions and dependencies, risks, training environment management, materials, ongoing training and resources. The tables already cover most of those. The rest need a sentence or two each, like these for the food distributor.

  • Objective. By Friday 26 February 2027, 90% of people in each role have completed their key tasks unaided.
  • Out of scope. System administration and report design. The implementation partner trains the IT team separately.
  • Dependency. A training environment with realistic customer, supplier and stock data, available from 1 February.
  • Risk. Testing overruns into the training weeks. Any cut to training time goes to the steering group as a go-live risk.
  • After go-live. New starters complete the same lessons and checks in their first week. The operations manager owns the materials.

Microsoft's guide also says to develop the plan at the start of the project. Written early, it gets rooms, people and the environment booked before testing claims them.

Adapting the template

For a CRM or an HR system the shape stays the same and the rows change. An HR system that every employee uses for leave and expenses has one very large row with three or four simple tasks, and a small HR team row that needs the full treatment.

For the formats you could put in the third column, see the methods table in end user training. If you are weighing a training environment against simulations, simulation vs sandbox compares them. The training plan is itself one section of a wider change management plan.

Once training starts, add two columns to the plan table: "trained so far" and "passed so far". Updated twice a week, that sheet is your readiness report. After go-live the last column feeds your user adoption figures.

Where Recourse fits

The rows that say "simulation"

In this example the order desk, purchasing and finance rows lean on simulations. Recourse builds those from a screen recording of each task: a Demo to watch, a Practice mode on a replica of the screen with hints that escalate, and an Evaluate mode that scores an unaided run against a pass mark, which is where the pass figures in the last column would come from. It would not replace the warehouse sessions on real handhelds or the month-end rehearsal, which needs a training environment that Recourse does not provide. Recourse is not an LMS, and it exports SCORM 1.2 only. See the buyer guide to end user training for an ERP go-live.

Start free

Questions people ask

What is a training plan template?
A reusable layout for planning training. For a software rollout it has one row per role and columns for the tasks to be learned, the format, the owner, the dates and how success will be checked.
How do you prepare a training plan for new software?
List the roles and count the people in each. List the tasks each role will do and pick the ones worth training. Choose a format for each task, name an owner per role, set dates in the three weeks before go-live and decide how you will check each role is ready. Write the first version at the start of the project.
Is there a software training plan template for Excel?
You can make one from this page. Select the plan table or the role and task matrix, copy it and paste it into Excel or Google Sheets, where it should land as rows and columns.
What should an ERP implementation training plan include?
The audience by role, the tasks for each role, the delivery format, a schedule tied to go-live, the training environment and its data, the materials, owners, how readiness will be checked, the risks and who looks after training once the project ends.
What does an ERP training schedule look like?
In the example here it spans 13 weeks. Super users train seven weeks before go-live, materials are built and piloted over the next three weeks, end users train in the last three, and support and measurement run for four weeks after.
What is the difference between a software rollout plan and a training plan?
The rollout plan covers the whole go-live: build, testing, data migration, cutover, communication, training and support. The training plan is the part that says who learns what, how and when.

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.