Hi All!
I’ve been experimenting with using Coda in ways it probably wasn’t originally intended for 
, and I thought I’d share one of the projects I’ve been working on.
For Alaska Native Youth Olympics (Learn more here - video), I built a system that takes athletes from registration all the way through scoring and (partially live) results. This type of integration has not been done before, so it was awesome to take a stab at it!
We debuted the system at the Juneau Traditional Games, and it worked really well (Developed March of 2026). There are definitely things I’d like to improve, but it was exciting to see athletes, coaches, judges, and organizers all using a system built entirely in Coda. We fully intend to improve and grow with the CODA platform.
Here’s a quick look at what I built:
1. Registration Forms & Waivers (296 athletes, 37 Schools/teams)
-
Built athlete, coach, and team registration forms in Coda
-
Collected waivers and registration information in a single system
2. Team Pages (37 pages button automated)
-
Automated creating team pages based on registration data
-
Coaches could manage rosters and assign athletes to events
3. Athlete Management
-
Registration and team page data fed into a master athlete database
-
Used to organize athletes and plan the event leading up to competition day
4. Athlete Check-In
-
Built a check-in page using Coda Cards
-
Athletes could quickly confirm attendance and verify the games they were competing in
5. ***Digital Scoring***
-
This is that part that pushed my UX/UI skills + CODA features. Specifically, I’d like to share the kicking and hitting events. Those use a specific three attempts scoring but we had to figure out a way to mimic traditional scoring pages.
-
Used Cross Docs to transfer athlete information from the master database into event-specific scoring sheets. (12 game documents)
-
Designed this approach to keep scoring docs smaller and faster on iPads and Lenovo tablets
-
Supported multiple scoring stations running at the same time on the gym floor. (at time there were ~17 stations going all at once)
-
There are so many complex parts to the scoring, from managing heights to measurements that it’s hard to share in just one bulleted list. I hope some day I can make a recording or video of it!
-
There is a double elimination bracket, I have not tackled yet, but hope to do so in the future.
6. Results & Public Posting
-
Judges entered scores digitally or manually
-
Confirmed results were pushed to a master results page
-
Results were then published to a live public-facing results page
One of the most interesting parts of the project was figuring out how to use Coda as an ecosystem instead of a single document. Athlete registration, team management, check-in, scoring, and results all needed to work together while still being fast enough to use during a live competition.
It’s a pretty niche use case, but I wanted to share it because it’s a good example of how flexible Coda can be when you start thinking beyond documents and project trackers.
I’ll share a few screenshots below.( I hid or partially hid names in certain areas for privacy of school aged children). Total there were 66 competitions with up to 6 station each competition.
I automated a lot of the data based on the intake forms. So programming could see how to prepare for the event logistics.
Athlete Check in: In order to get [Check boxes] I had to rig up the form for checkboxes rather than using the selector key. (True/False) values were essential here and for cross doc’ing.
Before we pushed data into scoring sheets, we gave the event coordinators the ability to [randomize] and manage the sheets just in case they needed to modify things.
Kicking and Hitting events- My pride, joy and loss of sleep. Figuring out how to create buttons that show status and also was an input was by far my proudest moment. It combined the original circle and cross out methods with iPad optimization.
Each division (6 total) had different starting heights and we need to be able to change starting heights based on game situation. The heights would then update on the button.
At times competitions would have up to 45 athletes. As a result they would separate athletes into different stations. While that helped make the competitions run more efficiently, it was a struggle to see the status of each station. So we build an over view page using the CODA chip. The head official could then go here and see which station had athletes still competing. When it came down to 6 or 7 athletes the would then group them together and call it “finals”. So the gaming dynamics needed to supported based on the game play.
I was able to figure out how to code automated results. This was new because it’s never been done in this manner. While it was faster, it was much harder to the officials to grasp because they are used to see the “overview” type of situation then hand tabulating comparisons. So it worked great once they felt they could “trust” the system.
The other event utilized measurement of distance or time duration to rank.
The most difficult part of the data entry was moving the numbers around based on the game and the type of measurements they used. It’s innate for me to use metric (as a former athlete) but these games used inches and feed. Some times to the quarter inch, sometimes only inches and other areas in feet or in seconds. We eventually figured out the logic and it worked well!
This was super fun and I have a deep passion for creating and utilizing technology or empower Indigenous organizations and culture!
Thanks for taking a peek!
-Brittany Gene (Navajo)
Max
