Replace Your Climbing Competition Spreadsheet

Spreadsheets work surprisingly well for the first few competitions a gym runs. Athletes register on a Google Form, the scoring sheet calculates points, and the final leaderboard exports to PDF. For a 30-athlete club event, this is fine.

The failure modes start above 50 athletes:

• Manual scoring bottleneck — at the end of a scramble session, one person has to type every result into the sheet. With 100 athletes × 25 boulders = 2,500 cells to update. Human error compounds.
• No live leaderboard — spectators wait for the final spreadsheet refresh. The competition feels static during the climbing window.
• No category automation — sorting athletes into U16, U18, Senior, Masters happens manually. Misassignments are common and visible to athletes mid-event.
• Tie-break math gets messy — the IFSC 25/10/-0.1 formula is doable in Excel but error-prone. Tops/zones/attempts hierarchy is worse.
• Multi-round events break — best-N-rounds scoring across a season requires linked sheets that few organizers maintain reliably.
• Concurrent editing fails — two staff updating the same sheet during the event creates merge conflicts and lost updates.

The pain shows up at the same threshold every time: somewhere between 50 and 80 athletes, the spreadsheet workflow stops scaling.

JudgeMate replaces the spreadsheet with infrastructure that scales:

• Live leaderboard — public URL updates after every athlete submission, sub-second on a healthy connection.
• In-app self-reporting — athletes sign in to JudgeMate on their phone and tap their result on each numbered boulder. No data entry by event staff.
• Automatic categories — athletes assigned by birth year (IFSC convention) and gender at registration. No manual sorting.
• Server-side scoring — configurable Flash/Top/Zone points calculated on the server with no spreadsheet formula errors. To run an IFSC-style event, set Top=25, Zone=10, Flash=15 (or any custom values) per boulder; native enforcement of the per-attempt -0.1 deduction is on the roadmap.
• PDF and Excel exports — final results in standardized formats for federation reporting and internal records.
• Season standings without a master sheet — a series adds up inside the platform: link each round, import its final places, and the standings map place to points. Best-4-of-6 is a slider, not a formula you maintain.
• A place limit and a waiting list — set the cap and entry number N+1 goes into the queue instead of bouncing off an error. Promotion is manual, because there are no notifications to announce it.
• Entry fees on the record, not in a bank account — paid, waived or unpaid per person, with a running total, on the start list and in the exports. We never take the money.
• Multi-staff dashboard — registration, scoring, and chief judge dashboards available to staff simultaneously without merge conflicts.

The gym keeps the same registration process and the same routesetting workflow. What changes is the scoring infrastructure underneath.

A typical migration from a spreadsheet to JudgeMate takes about half a working day for a 25-problem scramble with 100-200 registered athletes.

Step 1: Prepare your athlete list

If you collected registrations on a spreadsheet, you have two paths into JudgeMate:

• Self-registration (preferred) — share the public event URL on social media. Athletes sign up to JudgeMate (free, 30 seconds), open the event, click Join category, and fill the fields the organiser configured (T-shirt size, waiver checkbox, ID upload, etc.). Approve the joiners per category.
• Bulk import — for an existing list (e.g. from Google Forms or Competit.pl), use the JudgeMate Excel template (userName + userNumber columns) and import the roster.

Step 2: Create a JudgeMate event

Log in, create new event, set sport to bouldering, format to scramble (or whatever your event uses). Configure event date, venue, and registration window.

Step 3: Bring athletes into the event

For self-registration, your work is done — athletes appear with isApproved: false and you approve them per category in the dashboard. For Excel bulk import, the registration screen accepts the template (userName required, userNumber optional). Other fields (DOB, gender, category) are configured per-category in the dashboard or assigned manually. Native CSV import with broader column auto-mapping is on the roadmap.

Step 4: Configure boulders and scoring

Add 25 boulders to the event. Set point values: Flash 15 / Top 10 / Zone 5 (scramble default). For an IFSC-style event, set Top=25, Zone=10, Flash=15 per boulder; native -0.1 per-attempt enforcement is on the roadmap. A second preset is decimal (Zone 0.01 / Top 1 / Flash 1.0001), where a total of 5.1203 encodes 5 tops, 12 zones, and 3 flashes in a single number — useful when you want every counter visible without separate columns. Validate scenarios in the free IFSC points calculator before locking your config. Print boulder number tags (B1, B2, …) for each problem station.

Step 5: Run a 30-minute test event

One day before the public competition, have 2-3 staff members open the event in the JudgeMate app, walk through the boulder list, and submit test results for every problem. Verify category assignment, leaderboard updates, and projection display. Clear test data when done.

The migration is reversible — if something does not work, run the public event on the spreadsheet and try JudgeMate at the next round. Most gyms commit fully after one successful pilot.

If you keep an athlete spreadsheet today, here is where each field ends up after migration:

A Polish climbing club ran four years of monthly bouldering scrambles on a Google Sheet. The sheet worked at 30-50 athletes per round. By year three, registrations grew to 80-120 per round, and the workflow broke:

• Scoring took 45 minutes after the climbing window, with two staff typing results from paper cards.
• Live leaderboard was a projector showing the spreadsheet; updates stopped during the climbing window because the spreadsheet was being edited.
• Three athletes were misassigned to wrong age categories in one event, discovered only after final standings published.

The club migrated to JudgeMate at the start of year four. Results from the first event on the new platform:

• Final standings ready 2 minutes after the climbing window closed.
• Live leaderboard updated continuously, no projection dropouts.
• Zero category misassignments — birth-year automation handled it.
• Three athletes asked to migrate their old performance history; the team explained the spreadsheet history stayed in Google Sheets but new history accumulates in JudgeMate going forward.

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