A team building competition is not one sport. One game is decided by finishing order, the next by a stopwatch, the next by how many of something a team collected, and at least one of them has penalties that change the result after the fact. If you want the spreadsheet version of what follows, formula by formula, that is the Excel guide; this one is about the decisions those formulas cannot make for you.
Most scoring tools handle one of those. That is the whole problem.
Below: why these events break spreadsheets specifically, the penalty rule that gets applied in the wrong place more often than any other, and what we built after doing it the hard way for a few hundred events.
Six Games. Four Ways Of Scoring. One Table.
A normal day looks something like this.
Tug of war. Finishing order. First, second, third.
Relay. A time. Lowest wins.
Ring toss. A count. Highest wins.
Puzzle challenge. A score out of something. Straight points.
Obstacle course. A time, plus penalties. Ten seconds added for a dropped baton, ten more for a missed gate.
Bonus challenge. Points, but the client wants it to count double.
Every one of those produces a different kind of number, and all six have to resolve into one standing that a room will accept.
That is not a spreadsheet problem you solve once. It is a conversion problem you solve for every game, every time the games change.
Those are four of the seven ways this platform can score a game. Most events use three or four of them. The point is not the count, it is that they all have to end up in the same table.
The Penalty Rule Most People Get Wrong.
This one is worth its own section because it is subtle and it silently produces wrong winners.
A penalty on a timed game has to be applied to the time, not to the points.
Take a team that runs the obstacle course in 84 seconds and picks up two ten-second penalties. Their time is 104 seconds. That 104 is what gets ranked against everyone else, and the resulting rank becomes their points.
The wrong way is to rank the raw 84, convert that to points, and then deduct points for the penalties. It feels equivalent. It is not.
Ranking is relative. Adding 20 seconds might move a team from first to fourth, or it might not move them at all if the field is spread out. Deducting a flat number of points ignores the field entirely. The two methods give different winners, and the difference shows up exactly when the results are close, which is the moment everybody is paying attention.
Same rule in reverse for bonuses on timed games. Subtract the seconds first, then rank.
If you take one thing from this page, take that. Penalties belong to the raw result, before conversion.
What Actually Happens On The Day.
The scoring logic is the easy half. Here is the rest.
Results come from people who are not at a laptop. A facilitator at station four saw the result. They are also briefing the next team, watching the clock and answering a question. The score reaches the scoring laptop by radio, by group chat, or by memory.
The client changes the shape of the event. Not usually by adding. By cutting. The morning overruns, they drop a game, and everything that was pre-programmed around six games now has to work with five. Weightings, conversions, the lot.
The team count is wrong. You were told fifty. On the morning it is forty-seven, because a department pulled out.
Someone keys the wrong number. Then you either find it, or you don't.
We found one. A team had taken several games, clearly, and the standings put someone else first. We caught it early. It still cost us a replacement prize, because the result had already been read out and buying the trophy twice was the only decent option.
That is the honest version of the risk. Not that you hand the wrong team a trophy and never know. That you catch it, it costs you anyway, and you spend the rest of the day wondering what else is in there.
Why Spreadsheets Struggle Here Specifically.
They can do the maths. We have written the formulas out in full and given away a working template, because for a handful of events a year a spreadsheet is genuinely enough.
What they struggle with is everything around the maths.
Conversions are hard-coded, so a cut game is a rebuild rather than a setting. Several people keying at once means scores overwrite each other and nobody is told. Anyone who can enter a score can also move a cell, delete a row or type over a formula, and the file will keep producing confident, wrong numbers. And a spreadsheet on a ballroom screen looks like a spreadsheet on a ballroom screen.
At two or three events a year, none of that matters. At ten events in a week it is a headcount, because one person keys and a second person checks, and the checking is not optional.
What GamesTally Score Does About It.
Seven scoring modes in one event. Direct points, position, quantity, win/loss/draw, multiplier, podium where only the top few count, and a custom mode for the game that fits none of them. A time goes in as a quantity with lowest winning. Weighted scoring sits on top, per game. Converted onto one scale you set, resolving to one table.
Round robin tournaments when a game needs one. Up to eight groups, full standings tables, generated. Single elimination and a group stage feeding a knockout are built and not yet released.
Facilitators enter from their phones, at the station. The person who saw the result records it. They see their station, not the whole event, and their name is on every entry they make.
Two people cannot overwrite each other on tournament matches. If someone else has saved that match since you loaded it, your save is stopped and you get an error rather than a silent winner. On the other scoring modes that check is being added and is not there yet.
Everything is logged. Score saves, match results, bracket changes, facilitator joins. What changed, who changed it, when.
Rules live centrally. A cut game, a changed multiplier, a different team count is a setting, not a formula rebuild.
Set it up once. Save an event as a template and build the next one from it. If you run the same format repeatedly, setup happens once.
The screen is yours. Standings in your branding, or your client's logo and colours. Participants can follow it on their own phones too, if you want them to.
USD 4,000, once. Not per event, not per participant.
Who This Is Actually For.
Team building companies and event agencies. The core case. You already have the games, and the scoring is the part that eats your team's afternoon.
Schools. Sports day, house competitions, inter-class events. The same mix of timings, positions and points, and usually the same spreadsheet, maintained by whoever drew the short straw.
Venues and attractions that run team building. This is the group nobody builds for. Trampoline parks, arcades, bowling centres, adventure parks, activity venues. You run corporate groups as a revenue line, you run broadly the same format every time, and the staff running it are venue staff rather than event professionals. A configured scoring system pays back faster here than anywhere, because the format repeats. Set it up once, and every group after that is the same three taps.
Save your format as a template and every booking after the first one starts from a copy. That is the whole setup problem, solved once.
Common Questions.
How much is it?
USD 4,000, once, for GamesTally Score. Launch pricing, normally USD 5,000. There is no per-event or per-participant charge.
Can one event use several scoring methods at the same time?
Yes. Points, timings, quantities and finishing positions, in the same event, converting onto one scale.
How are penalties handled on a timed game?
You add the penalty to the time before you enter it, so 84 seconds plus two ten-second penalties goes in as 104, and the system ranks that. There is no separate penalty field that reaches back into another game's raw result. Where a penalty is not tied to a specific game, add it as its own entry with a negative number. See the section above for why applying it to the time rather than to the points afterwards produces a different winner.
What if the client cuts a game halfway through?
Change the setting. The standings recalculate. Nothing to rebuild.
What if the number of teams changes on the morning?
Adjust it. Everything recalculates from the new count.
Can facilitators enter scores from their phones?
Yes, from the station, seeing only what is relevant to them.
Can we put our client's branding on the leaderboard?
Yes. Your branding, or your client's logo and colours. It is your platform.
What happens if two teams tie?
They share the position. The system does not break ties for you, because the right tie-break is a decision about your event rather than a default we should pick. Agree it before the day and apply it.
Can two people enter scores at the same time?
Different games, yes. The same game at the same moment, no. The second save is stopped, that person gets an error, and the game reloads showing the scores that were saved first. They re-enter theirs on top. It is deliberate, and we would rather cost someone thirty seconds than quietly overwrite a score.
How do penalties work on a timed game?
Enter the adjusted time. A team running 84 seconds with two ten-second penalties goes in as 104. Penalties have to affect the ranking, not just the points, or a close finish comes out wrong.
Can participants submit their own scores?
No. Participants can watch the leaderboard; they cannot enter results. Scores come from your facilitators.
We only run a few events a year. Is this worth it?
Probably not, and we would rather say so. Take the free spreadsheet template instead. Come back when the events do.
Next: See GamesTally Score ยท Schedule a demo. Bring your spreadsheet or your score sheet, whichever is closer to the truth.