How to create job aids and training for a new software rollout before go-live

A go-live date doesn't move, but the system you're training people on keeps changing right up to it. Configuration decisions land in the last weeks of user acceptance testing. A field gets renamed after a data-migration test, and an approval step appears because finance asked for one. Meanwhile, everyone who'll use the system on day one needs a job aid for each task that changed.

Anyone who builds training against software that's still moving runs into this. Zach Romash built the first customer education academy at Teamworks in 2021, and it held up for about a week. "I remember when I first launched it — a week later, they told me the whole course had to be redone," he said.

A rollout team lives through that week on a fixed deadline, often for thousands of users. Here's how to build the training before go-live and keep it right afterwards.

What should training for a new software rollout include?

Rollout training is the set of materials people use to do their jobs in a new system from the day it goes live. In most enterprise rollouts that means a job aid for each task and short task videos for the steps that are hard to follow in text. SOPs sit behind both and record the policy for each process.

Start from roles, not from the modules of the software. An accounts payable clerk and a regional finance manager both work in the new ERP, but they touch different screens and get stuck in different places. A role matrix lists each role and the tasks that change for them at go-live, which tells you how many job aids you need and who should review each one. Here's part of one for a purchase-to-pay rollout:

Keep the SOP and the job aid in separate documents. The SOP says who can approve an invoice above a given amount, and why. The job aid shows where the approve button is, and it will change many times before the policy changes once.

Starting from a process recording? The free SOP generator drafts a written SOP from a video.

When can you start building training if the system isn't live yet?

You can start as soon as a workflow is configured and passing its test scripts, usually weeks before go-live. Teams get caught when they treat that first recording as final. Configuration keeps moving through user acceptance testing, so an early recording can show screens that won't exist on launch day.

Plan for two passes. In the first, record each workflow once it passes testing and build the job aid and video drafts from that recording, so reviewers can sign off the steps while the screens settle. In the second, once configuration is frozen, re-record against the final build and regenerate both formats. If the job aid and the video come from one recording, that second pass is a fresh recording and a short edit rather than a rebuild of every screenshot and the narration.

Some teams won't record against staging at all, because it drifts from production. If that's yours, record in the environment that gets promoted to production, and run each job aid against production in the first days after cutover.

Clueso builds a step-by-step guide and a video from the same screen recording, with a screenshot captured for each step. Re-record a changed workflow and both formats come from the new capture.

How do you produce hundreds of job aids before go-live?

One change management lead preparing a Workday rollout across 30 countries told us they needed 300 job aids and 25 training videos, and should have started weeks earlier. A training team of a few people can't write 300 job aids by hand in PowerPoint and Snagit in that window.

Two things change the numbers: who records, and what each recording produces. The person who does the task every day knows which field trips people up, and a central training team can't be the expert on every workflow in an ERP. At Teamworks, product experts record a raw walkthrough with no pre-written script, and the education team turns it into the finished video. That one recording should produce both formats. If the job aid lives in Word and the video is a separate capture, every later fix has to be made twice.

Plenty of rollout programs also start with hour-long recorded demos or classroom sessions. Nobody opens a 60-minute recording to find the three minutes on approving a requisition, so enterprise teams cut those sessions into two-to-five-minute task videos, one per row of the role matrix.

For a multi-country rollout, translate the job aid and the video from the same source, and keep a list of the system's field names so "cost center" reads the same in every language.

Clueso Cuts splits a long recording into shorter topic-based videos on the Enterprise plan.

Auto-translate localizes the voiceover, subtitles, on-screen text, and written guide into 150+ languages on every plan. On Enterprise, the translation glossary keeps field names consistent.

What happens to the training when the system changes after go-live?

Go-live isn't the last configuration change. Hypercare brings fixes, and the first vendor release after launch can rename a menu across the whole system. Enterprise buyers describe this as the moment a UI change breaks the library "in one fell swoop."

How much that costs depends on how the training was built. If each job aid and video traces back to one recording of one workflow, you re-record the steps that moved. If the training was assembled across several tools, every change has to be made in each of them. Teamworks hit this during a rebrand, when every existing video had to be fixed four times, in four places.

Read each set of vendor release notes against your role matrix and you'll know which job aids show a screen that's about to change, before a user finds out. For a library that has grown past the rollout, see how to keep a training video library current.

When one step changes, you can update a training video without re-recording it by swapping the clip for that step. On the Enterprise plan, the Auto Updates add-on takes a new recording of an existing guide and rewrites the guide text and the video narration together. See Enterprise plan details.

How do you know if rollout training worked after go-live?

Completion numbers tell you people saw the training. Change leads are usually measured on a second number too, which is how many people use the system correctly afterwards, and that number shows up first in hypercare tickets.

Group the first weeks' tickets by task and lay them over your role matrix. Where a cluster of tickets sits on a task with no job aid, you've found a gap you can fill that week. Where it sits on a task that has one, the aid is either wrong or nobody can find it.

People need to reach the aid at the moment they're stuck. One head of training told us they needed to move from static job aids to mobile-friendly video "so workers can pull it up on the floor in the moment, not just when they're sitting at a desk." For the adoption side, see rolling out new software with video.

If completion has to be tracked in your LMS, SCORM export packages Clueso videos as SCORM 1.2, SCORM 2004, or xAPI courses on the Enterprise plan.

Frequently asked questions

What is the difference between a job aid and an SOP?

An SOP defines the official process: who does what, in what order, and why. A job aid helps one person carry out one task in the software, usually on a single page. During a rollout the job aid changes every time a screen does, while the SOP changes only when the policy does. Clueso generates the job aid as a step-by-step guide from the same recording as the video, and the SOP generator drafts the SOP.

Which tools help change management teams create training videos and job aids for enterprise software rollouts?

Most change teams start with PowerPoint and Snagit, which slows down at rollout volume because every format is built by hand. Look for a tool that produces the job aid and the video from one recording and can redact data on screen. Clueso, the agentic video platform for businesses, turns one screen recording into a video and a step-by-step guide and localizes both into 150+ languages, with Magic blur on the Enterprise plan. Here's how it fits digital adoption teams.

How quickly can you create job aids for a new tool rollout?

It depends on how many tasks sit on your role matrix and who records them. Teams that build job aids in PowerPoint and Snagit describe the effort as out of proportion to the output, because every step is written and every screenshot captured by hand. Clueso generates the job aid from the recording, with a screenshot for each step, so the edit pass is the only writing left.

What is the best way to structure a training video for a new software rollout?

Cover one task per video and keep it to a few minutes. Open on what the viewer will be able to do, follow the order of the screens, and name each label exactly as the system shows it. Clueso turns the recorder's rough narration into a clean script with an AI voiceover, so whoever records doesn't need a script or a quiet room.

How do you get your team to use new software after go-live?

Put help where the task happens, and fix the gaps hypercare tickets reveal. Clueso produces the job aid and a short video from the same recording, and when a process changes you swap the clip for the step that moved.