Project Brief: Marshal Incident Reporter (Bubble.io Build)
Purpose
A real-time incident reporting app for motorsport marshals (multiple during event) to log on-track incidents quickly and reliably during live events from various positions around the course into race control. Marshals must be able to mark the time of an incident, enter basic details, and receive confirmation (“ACK”) back from race control all on mobile or tablet devices. GPT was used to mock this in canvas to determine needs and flow. While currently this will be used internally only, this may be offered in the future to other event production teams on a subscription basis.
This is required to deploy as a beta test for an event beginning September 10. Please submit bid directly to joejanowski6j@gmail.com.
Key Features
-
Two-Screen Flow (Mobile-first)
-
Screen 1: Big red “Mark Time” button → captures current timestamp.
-
Auto-advance to Screen 2: incident detail entry.
-
-
Incident Details (Screen 2)
-
Location: selectable from customizable presets (T1, Pit Entry, etc.)
-
Incident Type: selectable from a preset customizable list (Contact, Blocking, Loss of Component, Stopped Kart, Off-Track Return, etc.).
-
Vehicle Numbers: entered via keypad. Shows as removable “chips.”
-
Reset Button (Black): Removes an entry.
-
Submit (Green) button → saves record and resets back to Screen 1.
-
-
Device ID (Auto-assigned per device)
-
Each marshal device is automatically assigned a unique ID on first load.
-
Editable in Settings; can regenerate if needed.
-
Stored locally so the same device always identifies consistently.
-
-
ACK (Acknowledgement)
-
After submission, marshal device shows “Awaiting ACK” banner.
-
Control room marks the incident as ACK’d.
-
Only the originating device receives feedback:
-
Sound (short beep) and/or Vibration.
-
Duration and number of responses customizable.
-
-
Banner disappears when ACK is received.
-
-
Log (Control Room View)
-
Displays all incidents in a table (time, type, vehicle, turn, track, sender ID, ACK status).
-
Audio or haptic response when incident received in log.
-
Control can click Send ACK to acknowledge an incident, with audio or haptic response.
-
Highlights possible double entry by two marshals reporting same incident. Mark Time within +/- 10 seconds, same Location.
-
-
Settings Page
-
Manage Device ID.
-
Manage Incident Types (add/remove/reset).
-
Manage Track & Location presets (add/rename/delete).
-
Toggle ACK preferences (sound on/off, vibrate on/off).
-
Data reset / export controls.
-
-
Export
- Ability to export all incidents to CSV (columns: timestamp, type, karts, turn, track, ack status, sender ID).
Technical Notes
-
Must be mobile-first design (optimized for tablets/phones in the field).
-
Core functionality is real-time (Bubble DB sync). If not able to send a haptic response a message indicating ‘Did Not Send-Report via Radio’ will trigger the marshall to report via radio. Non reported data should still be visible to relay information.
-
Real-time updates required so that control-room ACKs instantly reflect on marshal devices.
-
Potential future: Wrap with BDK Native for App Store/Play Store distribution and stronger vibration APIs.
Deliverables
-
Bubble.io app with:
-
Incident data structure.
-
Report page (2-step flow + Awaiting ACK banner).
-
Log page (control view with ACK workflow).
-
Settings page (Device ID, presets, toggles).
-
CSV export function.
-
-
Functional on mobile browser; optionally prepared for native wrapper.
Thanks for your time and consideration!
