Book Bahamas · Demo paths

Scenarios

Nine ways a shift actually goes. Each one runs through screens that already exist, in the order an instructor would meet them — start at step one and follow the buttons, or jump straight to the step you want to show.

9Scenarios
1Rider per ski
~3mEach
7 steps

The clean run

Nothing goes wrong. This is the spine every other scenario branches off — worth running first so the manager knows what normal looks like.

  1. Open the appSplash, then sign in — nothing is validated
  2. TodayBoarding pass, 18-minute countdown
  3. Check-inTick the first four
  4. Machine checkAssign a hull from your register, fuel and hours, walkaround
  5. On the waterTide starts filling the screen
  6. Close outReadings in, tip, machine away
  7. ReceiptTrack, timings, payment
Watch forRider count stays at 1 on every single screen.
Run scenario
5 steps

The rider never turns up

Fifteen minutes past the booked start, no answer on the phone. The commonest way a slot dies, and the one with money attached.

  1. TodayCountdown has run out
  2. TrackingThey haven't left the hotel
  3. Check-inCall them from here first
  4. Report a no-showRide stays unstarted
  5. Follow the ticketMarcus replies, slot released
Watch forBack on Today, the boarding pass now carries an amber On hold strip.
Run scenario
4 steps

The machine fails its check

Quarter tank, and a hull mark that wasn't there yesterday. The app refuses the launch rather than letting you find out two miles offshore.

  1. Check-inTap the locked fifth item
  2. Machine checkSet fuel to ¼ — the launch button dies
  3. Report a machine faultDispatch reassigns the unit
  4. Follow the ticketWorkshop replies, JS-04 assigned instead
Watch forPhotos stay optional throughout — the gate is fuel and damage, not paperwork.
Run scenario
3 steps

The weather turns

Wind over the limit, swell over the limit, small-craft advisory in force — and a paying customer standing on the dock expecting to ride.

  1. ConditionsBoth limits breached, advisory until 15:00
  2. Stand the ride downRefund or reschedule is the base's call
  3. Open reportsThe conditions ticket joins the queue
Watch forPick Conditions are workable and it pushes back at you. That's deliberate.
Run scenario
3 steps

Emergency on the water

Rider off the ski, half a mile out. The screen has to work with one wet hand and no time to read anything.

  1. On the water34 minutes in, mid-ride
  2. Hold SOS two secondsA tap does nothing — hold it
  3. File the incident afterOnce everyone's ashore, not before
Watch forNo confirmation dialog and no form. Position goes to base the instant it fires.
Run scenario
3 steps

They run past the hour

The rider is having too good a time to turn back. Overtime is never charged automatically — it's a judgement you make at the dock.

  1. Turn-back warning56 minutes: amber, turn for shore
  2. Eight minutes overScreen goes red, counts up
  3. Close out with a surchargeTick it only if it was the rider's doing
Watch forThe tide colour changes with the state — teal, amber, then red.
Run scenario
3 steps

Damage disputed at the dock

A new scratch on the sponson. The rider says it was already there. This is the scenario your walkaround photos exist for.

  1. Close outFlag the panel before they walk away
  2. Attach the photosBefore-and-after, timestamped
  3. The resolved threadTimestamps settled it, no deposit taken
Watch forA resolved ticket hides its reply box — closed means closed.
Run scenario
3 steps

A walk-up with no booking

Someone wanders down the beach asking to ride now. No booking means no waiver and no cover, so it goes through the base first.

  1. Scan or type the codeTry RS-1256, then RS-1249, then anything else
  2. What to doHelp Center answers it directly
  3. Check-in as normalOnce the base pushes the booking through
Watch forAn unknown code fails cleanly rather than inventing a rider.
Run scenario
4 steps

Starting a new instructor

Marcus hands a new hire an invite code on their first morning. Nothing here is validated, so it runs without real credentials.

  1. RegisterInvite code, details, password, certifications
  2. ProfileCertifications, working preferences, edit sheet
  3. Help CenterSearch it — try typing "fuel"
  4. ScheduleTap Sunday for the empty state
Watch forProfile flags the rescue refresher expiring in seven weeks.
Run scenario
Reports persist, everything else doesn'tTickets you file survive a refresh so a scenario can be followed across screens. The three demo tickets reset each load, so every scenario can be run again from the top.

Every ride is one rider on one machine, plus the instructor.
Nine scenarios across twenty screens. No build step, no framework, no network calls.
← All screens  ·  Today