Replace Your Skateboarding Competition Spreadsheet

Spreadsheets work fine for the first few jams a skatepark runs. Skaters enter on a Google Form, a head judge scribbles numbers on paper, someone types them into a sheet between heats, and a final ranking exports to PDF. For a 30-skater park jam, that holds.

The failure modes start above 40-60 skaters:

• Trimmed-mean math. This is the real break point: each run needs five judges' 0-100 scores, drop the high and the low, average the middle three. Doing that by hand or with nested Excel formulas across 60 skaters × multiple runs is where mistakes appear, and a wrong middle-three average is invisible until a skater disputes a placing.
• Street aggregation. Olympic street compounds it: best run plus the top 2 of 5 trick attempts, max 300. That is a per-skater max/sort over seven performances, layered on top of the trimmed mean. Spreadsheets rarely get this right under time pressure.
• No leaderboard. Skaters and the crowd wait for the head judge to read placings off a laptop between heats. The contest feels dead during the run window, and a livestream has nothing to show.
• Manual progression. Building qualifying heats, then advancing the top N to semis and finals, is hand-managed. Seeding errors surface mid-contest in front of everyone.
• Two formats. Street and park diverge: one counts best run + 2 tricks (max 300), the other counts best of 3 runs (max 100). Running both in one sheet means two parallel formula blocks that drift.
• Concurrent editing. A scorekeeper at the judges' table and an MC updating the same sheet on another device create merge conflicts and lost scores.

The threshold is consistent: somewhere between 40 and 60 skaters, the trimmed-mean-by-hand workflow stops scaling.

A typical migration from a spreadsheet to JudgeMate takes about half a working day for a street or park contest with 60-150 entries.

Step 1: Prepare your entry list

If you collected entries on a Google Form, you have two paths into JudgeMate:

• Self-registration (preferred). share the public event URL on Instagram and at the skatepark. Skaters create a JudgeMate account (free, about 30 seconds), open the event, tap Join category, and fill the fields you configured (age division, stance, waiver checkbox, etc.). You approve joiners per division.
• Bulk import. for an existing list from a Google Form, use the JudgeMate Excel template (userName + userNumber columns) and import the roster.

Step 2: Create a JudgeMate event

Log in, create a new event, set the sport to skateboarding. Set the event date, the skatepark or plaza as the venue, and the registration window.

Step 3: Bring skaters into the event

For self-registration, your work is done, skaters appear unapproved and you approve them per division in the dashboard. For Excel bulk import, the registration screen accepts the template (userName required, userNumber optional). Other fields (age division, stance, sponsor) are configured per division in the dashboard or assigned manually after import.

Step 4: Configure judges, criteria, and format

Add your judges and set the panel to five. Pick the format per category: street (2 runs + 5 best-trick attempts, best run + top 2 tricks, max 300) or park (3 runs, best run counts, max 100). The trimmed mean (drop high and low, average middle three) is applied automatically on every run and trick, so there is no formula to validate, only the format choice. To see the math before locking it in, read how skateboarding is scored.

Step 5: Run a 30-minute test heat

One day before the public contest, have 2-3 staff open the event in JudgeMate, run a fake heat, and submit test run and trick scores from five judge devices. Verify division assignment, the trimmed-mean result, the best-run-plus-top-2 total, and the leaderboard display. Clear the test data when done.

The migration is reversible. If something does not work, score the public contest on the spreadsheet and try JudgeMate at the next jam. Most skateparks commit fully after one successful pilot. For the full event playbook, see how to organize a skateboarding competition.

A skatepark ran a monthly street and park jam for three years on a Google Form plus a shared sheet. The sheet held at 25-40 skaters per jam. By year three, entries grew to 70-120 across divisions, and the workflow broke:

• The head judge read five scores per run off paper, and a scorekeeper computed the drop-high-drop-low average by hand between heats. Placings took 30-40 minutes after the final run.
• Twice, the middle-three average was computed wrong and a skater was bumped a place, caught only after the podium photos.
• The live leaderboard was a laptop screen the MC turned around between heats. The Instagram stream had nothing to show during the runs.
• The street total (best run + top 2 tricks) was a separate formula block from park (best of 3 runs); one jam the street block silently summed all five tricks.

The skatepark moved to JudgeMate at the start of year four. Results from the first contest on the new platform:

• Five judges scored on phones; the trimmed mean and the best-run-plus-top-2 total were computed automatically. Final placings were ready about 3 minutes after the last run.
• Zero scoring-math errors, the drop-high-drop-low and the 300-point aggregation are handled by the platform.
• The live leaderboard ran on the venue screen and the stream overlay, updating after every judged run.
• Some skaters asked to bring their old results across; the team explained the spreadsheet history stays in Google Sheets and new history accumulates in JudgeMate going forward.

The transition cost was about 4 hours of setup before the first public contest.