Software simulations

How to create a software simulation

To create a software simulation you do the task once while a tool captures it, then turn that capture into something learners can practise. Here are the three common ways, and what to get right before you press record.

Updated

Software simulations
Short answerPick one task. Prepare clean example data. Capture the task with Storyline's recorder, Captivate's recorder, or a tool that reads a recording you already have. Check every step, add hints and a pass mark, and publish it as SCORM for your LMS. Most of the effort goes into preparation and into keeping it up to date afterwards.

Before you record: five things to prepare

  1. One taskWrite it as something a person does: "Raise a purchase order for a stock item". If it takes more than about 15 clicks, split it in two.
  2. The right pathAsk the person who knows the process to walk through it once. Agree the correct route before you capture, so you are not recording a habit that the project wants to retire.
  3. Clean dataUse example suppliers, customers or patients. Check that nothing confidential is on screen, including in side panels and notifications.
  4. A tidy screenSet the browser or window to a standard size, close other tabs, and turn off pop-ups.
  5. A scriptNote what each step is for. "Choose the plant, because this decides where the goods are delivered." You will need these words for captions and hints.

Way 1: Articulate Storyline

Best for: teams that already build courses in Storyline on Windows.

  1. In Storyline 360, choose Record Screen, set the recording area, and pick a microphone if you want a voiceover.
  2. Do the task. Storyline tracks each click and keystroke.
  3. Insert the recording as step-by-step slides and choose a mode: View (the steps play like a tour), Try (the learner does each step, not graded) or Test (each step is a graded question with a passing score).
  4. Insert it again for each other mode you want.
  5. Go through the slides. Fix hotspot positions, rewrite captions, and add hints.
  6. Publish to SCORM and upload it to the LMS.

Good to know: the steps come from Storyline's own recorder. A video made somewhere else cannot be turned into step-by-step slides. Storyline runs on Windows. When the software changes, the usual fix is to record again, publish again and upload again. More in Recourse vs Storyline for software simulations.

Way 2: Adobe Captivate

Best for: building scored simulations by hand at a low price per seat, on Windows or Mac.

  1. In Captivate, choose New simulation.
  2. Tick the modes you want: Demo, Training, Assessment, or all three at once.
  3. Do the task while the recorder runs. Captivate records clicks and typing and turns them into slides.
  4. Review the slides. Demo has captions taken from the labels of what you clicked. Training adds click boxes and hint and failure captions. Assessment removes the hints and scores each correct click.
  5. Tick "Include in quiz" on the click boxes that should count towards the score.
  6. Publish to SCORM and upload it to the LMS.

Good to know: like Storyline, Captivate builds a simulation only from its own recorder. Changes mean editing or re-recording, then publishing again. More in Recourse vs Captivate.

Way 3: from a recording you already have

Best for: when the expert has no time to sit with you, when a recording of the task already exists, or when the software changes often.

This is what Recourse does. It starts from a screen recording, and there are three ways to give it one.

  1. Record or upload. Record your screen with the recorder built into Recourse (nothing to install), or with the Recourse Chrome extension. Or upload a recording you already have: a Zoom handover, a recorded test session, a Loom from the product team. Talk through what you are doing as you record. More in from screen recording to simulation.
  2. Let it build. Recourse splits the recording into screens, finds each click, reads the buttons and labels, and drafts the instructions.
  3. Review. Check each step. Edit the wording, fix a click target, remove a step that is not needed.
  4. Choose the modes. Demo is a narrated walkthrough. Practice has the learner do each step, with a hint, then a nudge, then the answer. Evaluate is scored against a pass mark.
  5. Share it. Send a link, or on the Pro plan export SCORM for your LMS. The SCORM package stays connected, so later edits reach the LMS without a new upload.

Good to know: each simulation follows one correct path, and there is no branching yet. The free plan runs for 15 days with a watermark. If you only want to see what a recording turns into, the video to simulation tool does one for you with a free account.

Which way should you choose?

StorylineCaptivateRecourse
Starts fromIts own recorderIts own recorderBuilt-in recorder, Chrome extension, or any recording
ModesView, Try, TestDemo, Training, AssessmentDemo, Practice, Evaluate
Captions and narrationYou write and record them, or use AI voicesCaptions from button labels, your own voiceWritten and voiced for you, then you edit
Runs onWindowsWindows and MacAny browser
When a screen changesRecord, publish and upload againEdit or record again, publish againCapture that one step again
Custom interactions and branchingYes, a lotYesNo
List price$1,749 per seat a year (Articulate 360 AI)$39.99 a monthFree for 15 days, then from $99 a month

Storyline and Captivate details read from each vendor's own pages on 29 October 2026.

Other tools, including ones built for SAP and Oracle, are in software simulation training tools compared.

After you build it: the checks that matter

  • Test it as a learner. Do the practice mode and click the wrong thing on purpose at every step. Do the hints make sense?
  • Ask a beginner. Someone who has never seen the screen will find the confusing prompt in two minutes.
  • Check the score reaches the LMS. Upload the SCORM package to a test course and complete it. You can open the package first in our free SCORM viewer.
  • Write down the software version. Note which release the simulation was recorded on, so you know what to check after the next update.

Common mistakes

  • Recording too much. A 40 step simulation is a slog. Three short ones are better.
  • Prompts that give the answer. "Click Save" teaches clicking. "Save the order" teaches the task.
  • Real data on screen. Customer names, salaries and patient details end up in training more often than anyone admits. Check before you publish.
  • No plan for updates. Decide who checks the simulations after each release of the software, before the first one ships.

Questions people ask

What is the easiest way to create a software simulation?
Record yourself doing the task once and let a tool turn it into steps. Storyline and Captivate do this from their own recorders. Recourse does it from a screen recording: one you make with its built-in recorder or Chrome extension, or one you already have. It finds each click and writes the instructions for you to edit.
How do you create a software simulation in Storyline?
Choose Record Screen, do the task, then insert the recording as step-by-step slides in View, Try or Test mode. Edit the hotspots and captions on each slide, then publish to SCORM. Storyline runs on Windows and needs the recording to be made in its own recorder.
How do you create a software simulation in Captivate?
Choose New simulation, pick Demo, Training, Assessment or all three, and do the task while the recorder runs. Captivate turns the clicks and typing into slides. Review them, mark which click boxes count towards the score, and publish to SCORM.
Can you turn a screen recording into a simulation?
Not in Storyline or Captivate, which need their own recorder running while you do the task. Recourse can: upload the video and it works out the steps and builds the Demo, Practice and Evaluate modes for you to review.
How long should a software simulation be?
Short. One task, usually three to five minutes for the learner and no more than about 15 steps. Split longer processes into several simulations so people can repeat the part they find hard.
Do I need the live system to build a simulation?
You need somewhere you can do the task once: a test system, a training copy or the live system with example data. After that the simulation runs on its own and learners need no access to the system at all.

Keep reading

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