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
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.
| Type | What the learner does | What it is for |
|---|---|---|
| Show me (demo) | Watches the task play, step by step, with captions or a voice | Seeing the whole task once before trying it |
| Try me (practice) | Does each step themselves, with hints when stuck | Building the habit without fear of breaking anything |
| Test me (assessment) | Does the task with no help, and gets a score | Proving 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.
| Method | How it works | Tools that do it |
|---|---|---|
| Screenshots with hotspots | The tool's own recorder takes a picture at each click and places a clickable area where the click happened | Articulate Storyline, Adobe Captivate |
| Cloned interface | The tool captures the fields, menus and buttons themselves, so the copy can be edited later without a new recording | Assima |
| Replica of a web app | The tool copies a web application into a version people can click around in | Whatfix Mirror |
| From a screen recording | The tool reads a screen recording of the task and works out the screens, the clicks and the instructions for you | Recourse |
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 is | Good at | Weak at | |
|---|---|---|---|
| Video or screen recording | The learner watches | Quick to make, good for a first look | Nobody practises, and you cannot tell who can do the task |
| Simulation | The learner does the task in a copy of the screens | Safe practice, scores, works before go-live, no logins needed | Covers the paths you recorded and nothing else |
| Sandbox or training environment | A spare copy of the real system | Free exploration, long end to end scenarios | Costs money to keep, data gets used up, no hints or scores |
| In-app guidance | Tips that sit on top of the live system | Help at the moment of need, after go-live | The 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?
What is the difference between a software demo and a software simulation?
What is the difference between a simulation and a sandbox?
Is a software simulation the same as an interactive demo?
Can a software simulation be tracked in an LMS?
Do learners need a login to the real system?
What happens when the software changes?
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.