See how a tandem customer goes from booking to manifest to waiver in one flow
Click through a working prototype in your browser: book a sample tandem, assign it to a load, and sign a mobile waiver, then watch the waiver status appear on the manifest. All names and numbers are made up. At the end, three quick questions let you tell us what you'd change.
This is a prototype, not a finished product. No live customers, no pricing set yet. Blunt answers help us more than polite ones.
One tandem guest, three screens
Suggested path: 1. book a tandem, 2. assign it on the manifest (or try to overfill a load), 3. sign the waiver and return to the manifest, 4. answer three short "what would you change?" questions.
Book a sample tandem
Sample load board
Full loads can't be selected, which is how the demo avoids a double-booked slot.
What would you change? Three quick questions
Three optional questions, about a minute. Your answers stay in your browser until you choose "Add to pilot form" and then submit that form yourself.
Manifest · sample day
Click a name below (or drag it) to assign it to a load.
What the guest sees on their phone
Sign with a finger or mouse. Choose "Under 18" to see the guardian branch. When the waiver is submitted, its status flows to that guest's row on the manifest.
Important: the waiver text in this demo is placeholder text only. It is not a legal waiver and makes no claim of legal validity. Any real waiver wording must be reviewed by the dropzone's own counsel.
Tandem waiver DEMO
Sample Dropzone · placeholder text
No pending waivers. Book a tandem on step 1, or reset the demo.
What's in the demo, and what's still planned
"In demo" means you can click it above, using sample data in your browser. "Planned" means it is not built or shown yet. No dates are promised.
In the demo
- Tandem booking with date, slot and video/photo add-onsWrites to the sample load boardIn demo
- Capacity check per loadBlocks assigning more people than free slotsIn demo
- Manifest assignment by drag or clickKeyboard-friendly button path includedIn demo
- Digital waiver with signature padIncludes minor / guardian branch · placeholder text onlyIn demo
- Waiver status on the manifestPending / complete; a pending waiver holds boardingIn demo
- Check-inSimple per-guest toggleIn demo
- Payment statusPaid / unpaid flag only; no payment processingIn demo
- Load calls and status stepsOpen → call → boarding → departed; no messages are actually sentIn demo
- End-of-day summaryBasic on-screen totals from the sample boardIn demo
- "What would you change?" promptThree questions after the waiver step (or via the skip button); answers prefill the pilot form message, nothing is sent until you submit itIn demo
Planned · provisional order, not yet ranked by operator answers
- Real payment processingPlanned
- Guest text / email confirmations and load-call messagesPlanned
- Saved data, staff logins and multi-day historyPlanned
- Exportable end-of-day reportsPlanned
- Weather holds and rebookingPlanned
- Staff, gear and jumper recordsPlanned
How operator answers will shape the Planned list
The order above is our own starting guess. It is not ranked by demand yet. We have not published any tally of operator answers, because we only want to report what real dropzone people have actually told us through the pilot form.
When real replies that include the three demo questions arrive, we'll count the answers and use them like this:
- Waiver fields → what we change in the demo waiver (extra fields, shorter form, guardian path, or "bring your own wording").
- Load-call method → the priority of guest messages and load-call notifications, and how the demo's call step behaves.
- Report contents → the priority of exports, payment, weather-hold and per-staff reporting.
We'll publish only aggregate results here, never individual quotes, names or dropzones, and we won't publish percentages from a handful of replies. Want your own requirements counted? Answer the three questions after the waiver step and send the pilot form.
Get the first genuine replies
Goal: five distinct, real replies that include the three demo answers. Send this one by one to dropzone people you already know personally. Then open /#tally. Nothing here is uploaded or tracked.
1 · Message to send
2 · Ground rules
- Send only to dropzone people you know personally. One message per person; no mass posting, no scraped lists.
- No incentives, no pressure, no claims about customers, pricing or compliance. The demo is a prototype.
- Never fill in or guess answers for someone. A reply counts only if that person gave it.
- If someone answers by text, email or phone instead of the form, transcribe only what they said, with their OK, using the template below and the exact option wording. Keep the original private.
- Paste each reply into the tally once. When five distinct replies exist, run /#tally.
3 · Transcription template (off-form replies)
Tally real pilot replies
Paste real pilot-form replies below (several at once is fine). This reads every [Demo feedback] block, counts the answers to the three questions, suggests a Planned order, and, once at least five distinct usable replies are pasted and you confirm they are genuine, drafts an aggregate-only snippet and a hand-edit checklist for the readout card. It runs only in your browser and uploads nothing. Counts come solely from what you paste.
Three day-of frictions the demo is designed around
These are common situations at busy dropzones. We're testing whether one connected record helps, and the pilot is how we find out.
Paper waivers
Clipboards, handwriting and a stack to match back to the manifest. A digital waiver can put the status next to the guest's name, so staff see who is ready.
Phone-tag bookings
Back-and-forth calls and messages to settle a date, a time and add-ons. A booking form that shows only open slots can cut down the repeat conversations.
Double-booked slots
When the booking list and the manifest are separate, they can disagree. In the demo, bookings and the manifest read the same board, and full loads can't be overfilled.
Already using manifest software?
This is built for operators who want booking, waiver and manifest to work from one record. If you use Burble or another tool today, tell us in the pilot form, and we'll learn what you'd want to keep. We aren't claiming feature parity with any existing product.
Request a pilot walkthrough
Tell us about your dropzone. We'll reply by email to set up a walkthrough and talk about what a pilot could look like. Pricing hasn't been set, and there's no obligation.
Tried the demo? Your answers to the three "what would you change?" questions can be added to the message box, so we start from your actual requirements and use them to order what we build next.
Honest limits: this is an early prototype with no live customers. We don't claim FAA or USPA compliance, and we don't guarantee that any waiver is legally valid. Waiver wording must be reviewed by your own counsel.
Prefer email? julien@relaycairn.com