Ripple — preview a reserve before you commit
A read-only quote of what reserving a stop to a machine would actually do — before anything changes.
Look before you reserve
Reserving or force-assigning a stop is a real intervention in a live swarm. Ripple lets you see what it would do before you do it: a read-only preview, right in the reserve control, that quotes the effect without changing a thing.
How to use it
In the reserve control for a stop, pick the machine (and tick Next if you're considering it), then hit Preview. The quote appears inline:
- Natural rank — where that stop already falls in the chosen machine's order, as scored by the live engine. Rank 2 means the swarm was getting there soon anyway.
- How much sooner — when previewing Next, roughly how much earlier the stop would be cleared versus its current projected ETA.
Read-only, guaranteed
The preview consults the exact live scoring engine — the same ranking that drives real dispatch — but the entire computation runs with database writes blocked. It cannot claim, hold, or nudge anything; if anything even tries to write, the preview fails safe and shows nothing. Nothing changes until you actually press Reserve.
Why it matters
Some reserves are free — the stop was next in line anyway. Others are expensive — it's buried fourteen deep and pinning it drags a machine off better work. Ripple turns that from a guess into an informed choice, and because it's harmless, you can preview as often as you like mid-storm.
Updated 2026-08-17
In this topic
- The real-time ops dashboard
- Proactive failure alerts
- The live interactive map
- Reserve a stop for a machine
- Reopen a completed or skipped stop
- How the live fleet feed stays current
- Join a run and start your shift
- Pause and resume a run
- Device handoff — newest device wins
- Turn-by-turn navigation to your next stop
- Leaving a run and breakdown recall
- Dispatcher FAQ: reading the board during a storm