What’s new

Every stage in the Simulator canvas is made up of processes (a unit of work such as “Valuations” or “Fraud screening”), and every process can carry multiple variations, the specific paths a case can take through it, each with its own processing time, share of traffic and fall-through rate. Any variation can be dragged onto any stage, so a simple stage with one way of working still looks simple, and a complex stage shows the real mix of routes running through it.

Before you commit to a change, hovering a variation in the library shows its impact if applied against what is already in place, in days, colour-coded faster or slower. Compare mode goes further: it freezes today’s configuration as a baseline and opens a second, editable strip below it, so you can build an alternative mix of variations and see the difference in both journey time and annual fall-through cost, side by side, before saving anything.

Why it matters now

Because fall-through and processing time are tracked at the level of the individual variation, not just the stage, you can see precisely which route through a stage is losing applications or adding days, and test a specific substitution, more traffic through the faster valuation route, say, rather than a generic ambition to “speed up valuations.” The same calculation runs in the browser, for instant feedback while you drag, and is re-checked on the server every time you save, so a saved scenario is validated, not just estimated.

How this helps mortgage lenders

• Build the business case at the level a change actually happens. A proposal to shift traffic share between two variations of the same process can be modelled, saved and shown with a specific days-and-pounds delta, rather than argued from an average.
• See the cost of “quick and cheap” honestly. A faster variation is not automatically the right choice if its fall-through rate is materially higher; Compare mode puts both effects on the same screen.
• Test before you commit operationally. Because nothing is written back until you choose to save, process, risk and product teams can explore several configurations in a single working session without disturbing the live baseline.
• A shared, named record of intent. Saved journeys carry a name and a description, so the reasoning behind a modelled scenario is still legible to a colleague, or an auditor, months later.