football prediction league scoring
Football Prediction League Scoring Explained
Help players understand how their football predictions become weekly points and how organisers can resolve questions consistently.
By Jim · Updated
Start with the configured mode
A prediction league can reward the correct result, the exact score or a combination defined by its rules. There is no universal scoring table that fits every league. The configuration and rule badges visible inside ScoreSocial determine the points for your group.
Before publishing an explanation, compare it with the league screen and the agreed football prediction league rules. Avoid copying a points table from another competition.
Use a worked example
Choose a fictional fixture and show three possible predictions: an exact score, the correct outcome with a different score, and an incorrect outcome. A compact table is usually clearer than a paragraph.
For example, suppose the published league configuration awards three points for an exact score and one point for the correct result. If Northport beat Riverside 2-1, the explanation could read:
| Prediction | What it got right | Example points |
|---|---|---|
| Northport 2-1 Riverside | Exact score and result | 3 |
| Northport 1-0 Riverside | Correct result, different score | 1 |
| Northport 0-2 Riverside | Incorrect result | 0 |
Replace those example values with the points shown in your own league configuration. Then explain any additional configured rules in the same order that players see them. Do not invent bonuses or penalties that ScoreSocial does not calculate for the league.
Explain the tie-break with a second example
In a result-mode league, the configured first weekly tie-break can be the most correct draws, home wins or away wins. If Sam and Lee both predict eight results correctly, but the configured tie-break is correct draws and Sam has two while Lee has one, Sam ranks above Lee for that week. If both totals are still equal, use the order and points treatment shown in ScoreSocial.
Put the selected tie-break beside the scoring example. Do not copy a result-mode tie-break into an exact-score league unless that rule is actually displayed in its configuration.
Distinguish weekly and season views
The weekly leaderboard answers who performed best in the selected gameweek. The overall table tracks the season. ScoreSocial includes live scores, weekly standings and season standings on every plan; plan limits determine how many seasons can be active at once. Make it clear which view an announcement refers to, particularly early in a season when a single week can move positions sharply.
The features page describes current capabilities and the pricing page sources limits directly from the plan catalogue.
Use the recap to answer questions
When a player asks why their score changed, review the completed fixture, their locked prediction and the fixture-level recap. Rule badges help show the basis of the calculation. Check whether the underlying match result is final before treating the question as a scoring fault.
If a genuine data or configuration issue remains, record what was checked and communicate any correction to the affected group. Avoid privately changing a rule after results are known.
Keep the explanation stable
Publish the scoring summary before entries open. If the group chooses a different system for a future season, date the new version and keep the old season’s explanation available. Mid-season changes undermine comparisons and create unnecessary organiser work.
For the complete setup sequence, use how to run a football prediction league. It connects scoring to deadlines, invitations and the weekly routine.