Without and with FloorPilot
What actually changes?
Two parties look at the same event differently. An organiser wants to know whether everything is ready on time and who does what. A municipality wants to know whether the agreements are kept and what can be shown afterwards. Choose below which story you want to see. Both use the same fictional event.
Havenlicht Festival, the municipality of Vlietkade and everyone named here are invented. No data from real customers or municipalities appears on this page.
Whose story would you like to see?
- 1Situation
Eleven weeks before the gates open.
Without FloorPilotThe job is confirmed. From that moment the run sheet grows by itself: a document here, an email there, a group chat for the crew. Nobody chooses this, it simply happens.
With FloorPilotThe event gets one place. The seven things that must be done before opening are in there from the start, each with someone who does it and a week by which it must be done.
Fictional exampleHavenlicht FestivalSaturday · 18,000 visitors · 18:00 to 01:00 · municipality of VlietkadeConditions from the permit processedSanne · week 3Site map and escape routesMark · week 5Security staffingDilan · week 7Crew briefing sentSanne · week 9Contact persons recordedMark · week 4Traffic plan latest versionin consultationConfirmation first aid post 2in consultation - 2Problem
The sources drift apart.
Without FloorPilotThe permit says music stops at 00:30. The roster runs until 01:00. The email chain says Mark is on the entrance, the group chat says Dilan. All four were correct the moment they were written.
With FloorPilotThere is one version. Whoever changes something changes it for everyone, and the previous version is kept. Two people can no longer hold different truths without anyone noticing.
Without FloorPilotFictional examplePermit_final_v3.pdfPDF · 11 MBmusic until 00:30Roster week 40.xlsxSpreadsheet · 6 tabsshifts until 01:00RE: RE: entrance changeEmail · 14 messages in the chainentrance: MarkCrew HavenlichtGroup chat · 212 messagesentrance: Dilan - 3Consequence
On the night it costs time you do not have.
Without FloorPilotAt 20:14 the entrance jams. The question is not what needs to happen, but who does it. Three phone calls later someone is there. Nobody knows exactly how many minutes it took, because nobody was keeping track.
With FloorPilotThe report immediately gets an owner and a timestamp. Whoever picks it up confirms that in the app. From then on the clock runs visibly for everyone watching.
20:17Report acknowledged · 20:17Security LeadHavenlicht FestivalSOS · need helpTo do1 of 3 openExtra traffic marshals at entrance2 done tonightTonightTasksReportMoreThe Security Lead's appWhat the organiser seesINC-021 · Crowding at the entranceResolved20:14Reported by entrance crew20:16Assigned to Security Lead20:17Acknowledged20:22Extra traffic marshals deployed20:31Resolved - 4Result
Afterwards there is a record, not a reconstruction.
Without FloorPilotTwo weeks later someone asks how it went. The answer has to come from inboxes, phones and memory. Whatever was not written down is gone.
With FloorPilotThe timeline, the decisions and the improvement points are already there, built up during the evening itself. Nothing to reconstruct; you only decide what you share.
Event record Havenlicht FestivalFictional exampleIncident reports1 report, handled within 17 minutesPreparation7 of 7 done, last two came in on FridayChoices during the event3 recorded with time and responsible roleShared with the municipality4 documents · last updated Sat 13:05Improvement (noted by the organiser)Staff the entrance earlier at peak arrival
Half an hour. We show the product with invented data, just like above.