One system behind the scenes of an obstacle run.
For Obstacle Run Etten-Leur I built the website, the system behind the sign-ups, and a dashboard that shows the organisers who’s taking part at any moment.
In short
- Website, sign-ups and dashboard working as one
- The organisers see everyone taking part in one overview
- Built around how the event actually runs
The problem
An obstacle run lasts a day, but the preparation takes months. Participants want to know when they start and what to expect. The organisers want to know, at any moment, how many people are taking part.
Loose forms and spreadsheets hold up for a while. But the closer the day gets, the more has to line up at once.
What I built
I built three parts that talk to each other, so everything a participant does shows up for the organisers straight away.
The website
The public side: everything about the course, the start times and the sponsors, and the place where participants buy their tickets.
The event system
Behind the website, the system processes the sign-ups and keeps track of who’s taking part where. One source of truth instead of a pile of lists.
The operator dashboard
For the organisers: an overview of every sign-up, so everyone looks at the same numbers.
- Public websiteInformation and ticket sales for participants
- Event systemProcesses and stores the sign-ups
- Operator dashboardAn overview for the organisers
What it changed
The website, the sign-ups and the dashboard now work as one. What a participant fills in ends up in one place, and the organisers no longer have to hunt for the latest version of a list.
Before
- Loose forms and spreadsheets
- A pile of lists
- Hunting for the latest version of a list
Now
- One event system for every sign-up
- Everyone looks at the same numbers
- Seeing who’s taking part at any moment