Fix Attendance First, Then Worry About Your Points System
A league with twelve regulars and a scoring argument is in better shape than a league with a perfect formula and five people in the room. Turnout is the input everything else multiplies.
Turnout sets the ceiling on everything else
At 25 players you have a proper tournament: a full field, a finish worth reaching, and faces the regulars have not seen before. At nine you have a home game with paperwork. Entry fees scale with the field, and bounties need people to hunt.
Your points formula already pays for attendance
Under the default Chiprally model, points are a placement multiplier times the number of players in the game. The default table is 10, 8, 7, 6, 5, 4, 3, 2, 1, so the top nine score and everyone below them scores zero. Field size is inside every score.
| Finish | 30 player game | 12 player game |
|---|---|---|
| 1st | 10 x 30 = 300 | 10 x 12 = 120 |
| 4th | 6 x 30 = 180 | 6 x 12 = 72 |
| 9th | 1 x 30 = 30 | 1 x 12 = 12 |
Fourth in the busy room scores 180. Winning the quiet one scores 120. That is the most important consequence of field size scaling, and it is worth explaining out loud, because the first player to spot it assumes a bug.
Now run it over a 20 game season. Player A plays 18 and averages a mediocre 90 a night: 1,620. Player B plays 10 and averages a strong 140: 1,400. The better player loses by 220, and the only difference is eight nights on the sofa.
Attendance points and the participation trophy complaint
The usual fix for thin turnout is awarding points for showing up. It works, at a price worth calculating first. Size it against a normal result: if your typical field is 20, a win is worth 200 and ninth is worth 20. So a flat 25 points for attendance beats a ninth place finish, and a perfect record across 20 games banks 500 points, about two and a half wins.
Here is the test that settles the argument. Compare the attendance points available in a season to the gap between first and fifth in last season's table. If the attendance component is bigger, it is not a nudge, it is picking your champion. That is when the participation trophy complaint is fair.
Ten points a night is half a ninth place: symbolic, and symbolic is often enough, because the players who need the nudge are not doing arithmetic. They notice that the board acknowledges them. Either way, do not guess. Work out who the change would have crowned last season before you announce it for this one.
The quieter leak: everyone who scores zero
Only nine players score under the default table. In a 30 player field, 21 go home with nothing, some of them out inside an hour. Do that to one player four weeks running and they stop coming, without telling you why. Better answers:
- Run a second chance game. The default second chance table is 100, 50 and 25 for the top three, so going out early is a reason to stay.
- Run a knockout race. A player who goes out tenth having knocked two people out scores nothing at all under the default table, which is the whole problem. Keep a separate count of knockouts, hand it its own trophy at the end of the season, and that player leaves with something they won.
- Score deeper in big fields. Nine of 12 is fine. Nine of 30 leaves most of the room outside the system, and the length of the table is a setting.
- Keep the rewards that are not points. The unluckiest exit of the night pays a free drink, which rescues a bad night for nothing.
Ask for a commitment, do not just publish a schedule
A schedule is passive: it says a game exists. An RSVP asks for a yes, and a yes said in front of the group is a different thing from an ignored calendar entry.
The practical value is the headcount. Nine yeses on Tuesday for a Thursday game gives you 48 hours to act: post in the feed, call the regulars who never answered, ask two people to bring somebody. Without RSVPs you find out at 7pm at the venue, when all you can do is apologize.
Chiprally takes RSVPs per game and tracks who actually attended. Log yeses against turnout for ten games and you know your conversion rate, which turns a headcount into a forecast.
Reminders, and when to send them
Treat a no show as a memory problem before you treat it as a verdict. Somebody forgot, or left it too late to arrange the evening.
The league posts an automatic game-day reminder in the feed, and the organizer who also sends one by hand on the morning of a game night gets the last three people through the door.
Two touches is usually right: one early in the week, far enough out that somebody can move a shift, and one on the day a few hours before, when the decision gets made. More than that and people mute you, which costs you the two that worked. Put a reason in the message, not just a date: who is chasing the leader, or how close the bounty race is.
Make the standings public and hard to avoid
Standings in a spreadsheet on your laptop do nothing for turnout. Standings a player can open on a phone on Tuesday keep the league in their head between games. Someone who sees they are 40 points off fourth has a reason to show up on Thursday. Live standings and profiles with head to head records both give people a number that moves when they attend.
Give the mid pack something to chase
By week eight, three players can win your season and everybody else knows they cannot. If the title is the only recognized outcome, you have told two thirds of the league that the rest of the year is an exhibition. Recognize more:
- Bounty leader. A separate race decided by aggression rather than survival, often led by somebody nowhere near the top.
- Most games played. Purely attendance, and the honest place to reward it instead of smuggling it into the points.
- Most improved. Compare average points a game in the first half of the season against the second. It is the only trophy a beginner can win.
Chiprally works out the season champion for you, and most games played is already one of the season awards it counts. The bounty race and most improved are yours to keep and to announce in the feed, as they move. A trophy nobody hears about until the last night motivated nobody all season.
Breaking the death spiral
The failure mode is quick. Turnout dips, the night is less fun, the field is smaller, two regulars skip the next one, and six weeks later you are canceling. Waiting for it to correct itself is not a plan.
- Cut the calendar before you cut the league. Ten players twice a month is worse than 20 once. Merging two thin games into one full one is a promotion, not a retreat.
- Set a floor and say it publicly. "We run with eight or more." A stated minimum makes RSVPs worth answering, because the answer decides whether there is a game.
- Shorten the season. Twelve games people can plan around beat 30 nobody can commit to, and crowning a champion sooner resets interest.
- Ask by name, not in general. A general call for new players is ignored. Asking Dana on Tuesday to bring her brother on Thursday is not, and thanking her in the feed rather than in the standings keeps recruiting out of the scoring.
- Fix the night, not the format. Game nights that run past midnight, a venue with no food, a start time that clashes. Ask two people who stopped coming, and believe them.
The short version
Attendance is the input, not a side effect of good scoring. Field size scaling already rewards showing up, so price any attendance bonus against a real season first. Ask for RSVPs. Send two reminders, not six. Publish the standings. Recognize more than the champion. And when turnout slips, act in week two, not week six.
Run this on your own league
Turnout and scoring are the same lever seen from two ends. Put a thin season and a full one through the points simulator and watch how much of the title the empty weeks decided.