Staff move on. Your records shouldn't.
Every call, every form and every correction stays with the resort, not with whoever wrote it. When the claim arrives three seasons later, it's all there.
Incident reports and dispatch for ski resorts
They're the best people on the hill, and they're gone in April. ResortHuddle keeps the record instead: dispatch takes the call, the patroller fills in one record on a tablet, and every form the call needs prints from it, complete, dated and signed. Nothing depends on who remembers what.
A live demo of a made-up resort. No sign-up, nothing to install, no lift ticket.
Every call, every form and every correction stays with the resort, not with whoever wrote it. When the claim arrives three seasons later, it's all there.
Paperwork hours are paid hours, spent indoors while the hill waits. With each question asked once and every form printed from the record, the report gets done on the spot, the patroller is back outside, and the same team covers more of the hill.
Least of all volunteers, who give you their weekends for the love of it. Less time on paperwork is one more reason to come back next season.
The call comes in on the radio and lands on a notepad. At the end of the shift, the patroller writes the same name, time and injury on four forms, by hand, with a pen that works on the second try. The binder lives in the patrol room, the spreadsheet on someone's laptop, and the one person who knows where both are follows the snow to New Zealand in April. Three seasons later, the claim arrives.
Incident software often just puts the paper form on a screen: the same boxes, one form at a time, and the same questions again on the next one. ResortHuddle starts from the record instead.
| The usual way | With ResortHuddle |
|---|---|
| The same name, time and injury written on four forms | Asked once, printed on every form that needs it |
| The radio log on a notepad, typed up again after the shift | The board keeps every time as it happens |
| Each form filled in on its own, from scratch | One record, every form of the kit printed from it |
| A paper form can't tell you what it's still missing | A counter of what's left, and Next missing goes straight to it |
| A correction squeezed into the margin | Each correction beside the original, with who made it and why |
| Software that stops where the signal does | Keeps working offline and sends when it can |
| The one person who knows where everything is, until April | Every season in one place, for whoever asks next |
Quick math for management: last season's reports, times the minutes each one took, times an hourly wage. That's what the paperwork cost. We'll wait.
One sore knee, followed through four screens of the demo.
Lift operations radio in a skier down. Dispatch clicks what the caller knows, which is never much: nothing is required, since everything changes once patrol is there. The call is named the way patrol says it on the radio, one click sends a free patroller, another a toboggan, and every time is kept for the paperwork.
See the board in the demo ›
On the tablet the call is already waiting, with everything dispatch knows filled in. The record reads top to bottom and asks only what this call's forms need: the guest once, the assessment on a body map, the treatment, the transport. Too slow to type? Dictate. No signal at the bottom of the run? It keeps working.
See the patroller's screens in the demo ›
A counter shows how many answers are left, and Next missing jumps straight to the next one. At zero every form of the kit is complete: the accident report, the patroller's report, the on-site inspection and diagram, the photo list, and the communications log, printed from the dispatch log. Nobody has to remember which forms a knee needs: the kit follows the answers.
For the day legal wants one more form: it joins the kit and asks only what nobody has answered yet. Every other box fills in from what was already said, so your lawyers get their form and your patrollers keep their sanity.
The paperwork desk sends a report back with a question on the exact field that needs one, instead of a sticky note on the binder. Management sees the calls of the day, the week and the season by level, live, with nobody counting by hand.
The demo is a made-up resort with made-up people, in the browser, with nothing to install. Pick who you are at the top of any screen to see it as a patroller, a dispatcher or management.
In your browser only
Nine incidents in ninety minutes, written by patrollers to test the board: a red trauma, a lost child, a snowcat that needs a spot closed, 71 radio calls and board events, 11 patrollers. Play it at up to 60 times the speed, which is about how it feels on the radio. Nothing you do in the replay is saved.
Start the replayShared with other visitors
Take a call on the board, be the patroller on the tablet, submit the report, then find it in the review queue. Other visitors see what you enter, so please use made-up names. Bob is always available.
Try the live demoLess paperwork, more skiing. Every question asked once, what dispatch knows already filled in, dictation for the long answers, and buttons big enough for gloves.
Twenty calls at once with the fewest clicks: each call by stage, who is free in each zone, the gear in each cache, and who has the toboggan.
Complete reports, questions sent back on the field itself, every correction kept with its reason, and no handwriting to decipher.
Calls by level today and over the season, the calls under way and who is free, live, without asking anyone for a count.
Both modules work on the same record, so a resort that adds Dispatch later keeps all its history and enters nothing again. Both are subscriptions: nothing to install or host, and every update arrives on its own.
Entry level
Premium
The usual ones, answered before the lift reaches the top.
No. ResortHuddle learns your forms, not the other way around: runs, lifts, places, the start questions and the forms in your kit are settings of your resort, so the record asks what your own manual asks.
It keeps working. The tablet holds every answer until the signal catches up, usually on the way down, and deletes nothing before the server confirms it has it.
If they can work a radio with gloves on, they'll manage. The record asks one question at a time, top to bottom, only what the call's forms need, and Next missing goes straight to whatever is left.
No. It runs in the browser on the tablets and laptops you already have: no server room, no install day.
Health details are encrypted and kept out of logs and error messages, and no resort ever sees another resort's records.
Nothing. That's the point. Every call, form and correction stays with the resort, season after season, for whoever asks next.
Take a call in the demo and follow it to the filed report. It takes about one chairlift ride.