Software simulations

What is a software simulation?

A software simulation is a safe copy of an application's screens that a learner clicks and types in, to practise a task before they do it in the real system. Nothing they do in it touches real data.

Updated

Software simulations
Short answerSomeone records a task once, such as raising a purchase order in SAP. A tool turns that recording into a copy of the screens that learners can work through themselves. They can watch it, practise it with help, and then be tested on it. It is the software training version of a flight simulator: the controls look real, and mistakes cost nothing.

One note on the word. Engineers also say "simulation software" for programs that model physics, traffic or circuits. This page is about the training meaning: a simulation of a piece of software, made so people can learn it.

What a software simulation looks like

Take a company moving 400 managers onto Workday. Every manager has to approve time off in the new system from day one.

A video would show them where to click. A simulation makes them do it. The learner sees the Workday inbox, exactly as it will look. A prompt says "Open the request from Priya". They click it. The next screen appears. They choose Approve, type a comment and submit. If they click the wrong thing, the simulation tells them and lets them try again.

The whole thing takes three minutes, runs in a browser, and can sit inside a course in the company's LMS. The real Workday is never touched.

The three types: show me, try me, test me

Most tools make three versions of the same task from one recording. The names change from tool to tool. The idea does not.

TypeWhat the learner doesWhat it is for
Show me (demo)Watches the task play, step by step, with captions or a voiceSeeing the whole task once before trying it
Try me (practice)Does each step themselves, with hints when stuckBuilding the habit without fear of breaking anything
Test me (assessment)Does the task with no help, and gets a scoreProving they can do it before go-live

We cover the three in detail, with what each tool calls them, in show me, try me, test me.

Four ways a simulation gets built

All four start with someone doing the task once. They differ in what gets captured.

MethodHow it worksTools that do it
Screenshots with hotspotsThe tool's own recorder takes a picture at each click and places a clickable area where the click happenedArticulate Storyline, Adobe Captivate
Cloned interfaceThe tool captures the fields, menus and buttons themselves, so the copy can be edited later without a new recordingAssima
Replica of a web appThe tool copies a web application into a version people can click around inWhatfix Mirror
From a screen recordingThe tool reads a screen recording of the task and works out the screens, the clicks and the instructions for youRecourse

There is a side by side list in software simulation training tools compared, and the steps are in how to create a software simulation.

Software simulation examples

  • ERP rollout. A buyer practises raising a purchase order in SAP: pick the supplier, add two lines, choose the cost centre, submit for approval. Tested before the old system is switched off.
  • New CRM. A sales rep practises logging a new opportunity in Salesforce and moving it to the next stage, so the pipeline report is right in week one.
  • HR system. A manager practises approving time off and starting a performance review in Workday.
  • Hospital records. A nurse practises admitting a patient and recording observations in the electronic health record, on made-up patients, before the ward goes live.
  • Contact centre. A new agent practises finding a customer, issuing a refund and writing the case note, before they take a real call.
  • Customer training. A software company gives new customers a practice version of "set up your first project" inside its help centre. See customer education.

What these share: the task has a right way to do it, many people must do it, and a mistake in the real system costs money or time.

Simulation, video, sandbox or in-app guide?

What it isGood atWeak at
Video or screen recordingThe learner watchesQuick to make, good for a first lookNobody practises, and you cannot tell who can do the task
SimulationThe learner does the task in a copy of the screensSafe practice, scores, works before go-live, no logins neededCovers the paths you recorded and nothing else
Sandbox or training environmentA spare copy of the real systemFree exploration, long end to end scenariosCosts money to keep, data gets used up, no hints or scores
In-app guidanceTips that sit on top of the live systemHelp at the moment of need, after go-liveThe system must be live, and the work is real

What about interactive demo tools?

Tools such as Storylane and Navattic also turn a product into something you can click through. They are made for a different job: showing a product to a buyer, on a website or in a sales email. A training simulation is made to teach a task and check that someone can do it, so it has hints, a score, a pass mark and a report to the LMS. The mechanics look alike. The purpose is different.

More on simulations and sandboxes in simulation vs sandbox. In-app guidance is the job of a digital adoption platform.

When a simulation is worth making

  • The task is done by many people, or done rarely enough that people forget it.
  • A mistake is costly: a wrong payment, a wrong patient record, a failed audit.
  • People need to be ready before the system goes live, when there is nothing real to practise on yet.
  • You need proof. An auditor, a regulator or a project sponsor wants to see who passed.

When it is not: a task three people do, a screen that changes every week, or knowledge that is about judgement and not clicks. A short video or a one page guide is enough for those.

What makes a simulation good

  • One task, one simulation. Three to five minutes. "Raise a purchase order", not "Procurement".
  • Real looking data. Supplier names and amounts a learner would recognise, with nothing confidential on screen.
  • Hints that build up. A small clue first, then a stronger one, then the answer. A learner who is stuck should never be left stuck.
  • A fair test. The test should match the practice. Same task, no hints, a clear pass mark.
  • Easy to update. Software changes. If fixing one screen means recording everything again, the simulation will be out of date within months.

How Recourse fits

Recourse builds simulations from a recording. Record the task once, with the recorder built into Recourse or with its Chrome extension, or upload a recording you already have, such as a Zoom handover or a recorded test session. It produces three modes: Demo (a narrated walkthrough), Practice (the learner does each step, and gets a hint, then a nudge, then the answer) and Evaluate (scored, with a pass mark). You review and edit every step before anyone sees it.

What it does not do: it does not sit on top of your live system, it is not a sandbox that people can wander around in, and each simulation follows one correct path for one task. How the recording becomes a simulation is in from screen recording to simulation. It is free to try for 15 days.

Questions people ask

What is a software simulation in eLearning?
It is an interactive copy of an application's screens, placed inside a course. The learner clicks and types as they would in the real program, gets feedback on each step, and can be scored. It lets people practise a task without access to the real system and without any risk to real data.
What is the difference between a software demo and a software simulation?
A demo is watched. A simulation is done. In a demo the task plays in front of the learner like a video. In a simulation the learner has to make each click and type each entry themselves. Most simulation tools make both from the same recording.
What is the difference between a simulation and a sandbox?
A sandbox is a spare copy of the real system, with a real database, where people can do anything. A simulation is a recorded copy of the screens for one task, with prompts, hints and scoring. A sandbox suits free exploration. A simulation suits teaching and testing a set task for many people.
Is a software simulation the same as an interactive demo?
No. Both let someone click through a copy of a product. An interactive demo is a sales and marketing tool that shows a product to a buyer. A software simulation is a training tool that teaches a task, gives hints, scores the learner and reports the result to an LMS.
Can a software simulation be tracked in an LMS?
Yes. Most simulation tools export a SCORM package that reports completion and a score to the LMS. Check which version your LMS needs. Recourse exports SCORM 1.2 on its Pro plan.
Do learners need a login to the real system?
No. A simulation is a copy that runs in the browser. That is why simulations are used before go-live, when most people do not have access yet, and for contractors or customers who will never get a training login.
What happens when the software changes?
The simulation has to be updated, or it will teach the old screens. How hard that is depends on the tool. Some need the whole task recorded again. Some let you replace only the step that changed. Ask this question before you choose a tool.

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.