How to set scoring rules for a company prediction pool

Blog · May 17, 2026

How to set scoring rules for a company prediction pool

Scoring is the underrated detail that decides whether your pool ends up with 5 or 50 players. Three pillars, recommended values and mistakes to avoid.

Scoring rules are one of the most underrated decisions when setting up a company prediction pool. People configure them in three minutes, sometimes pulling a random formula from a colleague's spreadsheet, and only realise a week later that the whole competition is broken. Points do not add up fairly, one match weighs more than ten others, and the people at the bottom lose motivation before the group stage is even over.

This article sums up how to set scoring rules so that as many people as possible play your pool all the way to the final. No complicated maths — just a clear understanding of which details matter.

The three pillars of any solid scoring

Almost every working prediction pool rests on three layers of points, which add up together.

1. Picking the winner. The participant guesses who wins — home, away, or possibly a draw. This is the foundation and should make up the main part of the points. Picking the winner correctly is harder than it looks for most matches, especially in tournaments like the Ice Hockey World Championship where a weaker team regularly surprises.

2. Exact score (or goal difference). A bonus for predicting not just who wins, but with what score. This layer is psychologically important — it rewards risk. Without it, everyone would just mechanically pick the favourite and the table would be boring.

3. Bonus for an extra pick. More advanced pools can add a pick for a scorer, an assist, or the total number of goals. This tunes towards fans who follow the tournament closely. For a regular workplace pool it is not necessary.

Whenever you see a scoring proposal built on just one of these layers (for example, "whoever picks the winner gets one point"), that is a recipe for a boring competition. Good scoring rests on at least two layers.

The recommended standard model

For a workplace pool where most participants are not hardcore sports fans, a simple model works well:

  • 1 point for correctly picking the winner
  • +2 points for the exact score

That means whoever hits the exact result gets 3 points in total. Whoever only picks the winner gets 1 point. Whoever misses both gets zero. This ratio (1:3) is large enough to make risk-taking meaningful, but small enough that one lucky guess does not decide the whole league.

If you want the pool to feel more dynamic, you can shift the ratio. For example 1 / 3 / 5 (winner / correct goal difference / exact score). A three-tier model adds a middle step: "I correctly guessed that there would be a lot of goals, just not the exact number." It is more interesting for fans. For a regular office pool, though, it starts to get harder to follow.

What to do with draws in hockey and overtime

In hockey, a draw after regulation effectively does not exist — matches end in overtime, a shootout, or in playoff overtimes until decided. That raises a rule question: does the "who won" count by the score after 60 minutes, or by the final result?

Recommendation: count the final result, including overtime and shootouts. Most public statistics work this way, and it is more intuitive for participants. If you hit the exact score after 60 minutes (for example 3:3) but the match ended 4:3 in overtime, it is often seen as a "win with an asterisk". Some apps handle this so that the exact score is counted from the state after 60 minutes, but the final winner from the whole match. This rule needs to be communicated up front — otherwise an argument will follow.

In football and basketball, draws are common — there is no overtime problem, but the scoring rules need an explicit entry for a draw (typically the same points as picking a winner).

Bonus for scorer and assist

If you use a dedicated tool for a prediction league that works with team rosters, you can add a scorer and assist pick. The participant chooses before the match which player they think will score or assist, and after the final whistle they receive bonus points.

A scoring model for this layer:

  • +1 point for the correct scorer (anyone on the team you predict)
  • +1 point for the correct assist

I do not recommend making this too high (for example +5 points) — a fan who follows the tournament in detail would gain an insurmountable lead over the casual predictor and the table would lose its tension.

If you include a scorer bonus, expect that some later joiners will miss this detail. Remind people before each match that players can be predicted too.

Three most common mistakes

Mistake 1: Too big a gap between winner and exact score. If you give 1 point for the winner and 10 points for the exact score, one lucky guess on the fifth match decides the league. People give up.

Mistake 2: No bonus for boldness. If you only score "whoever picks the winner gets a point", everyone will pick favourites and the table will be one point apart. A bonus for the exact score or goal difference is necessary for predicting to stay interesting.

Mistake 3: Changing rules mid-tournament. A classic scenario — three weeks after the start someone notices the system is unfair and you propose a change. Never do that. The community will read it as cheating. Set the rules at the start, test them mentally on three matches, and then leave them alone.

Recommendations by league size

Small office league (5–15 people). Use the simple 1 + 2 model (winner + exact score bonus). Do not add scorer or goal difference. The risk that someone will not understand the rules is greater than the gain from more dynamics.

Mid-size league (20–50 people). Same model, but add a scorer bonus. That separates random pickers from those who actually follow the sport. For a corporate league it creates a nice mix — everyone can play, but fans get a way to stand out.

Large fan league (50+ people). I recommend all three layers: winner + exact score + scorer/assist. With large groups it is important to have more scoring steps, otherwise clusters of people with the same point total appear and the table becomes hard to read.

Conclusion

Good scoring is not about maths, it is about the psychology of the players. People want to feel their picks mean something, that taking risks can pay off, and that even halfway through the tournament it is worth keeping going. Three layers — winner, exact score and optionally scorer — cover those needs and work in practically any sport.

If you are setting up your first prediction pool and you are not sure, start with the basic 1 + 2 model and expand it in the next tournament if needed. A simple league everyone finishes is better than an elaborate system nobody understands.

How to set scoring rules for a company prediction pool