Your points system is the rulebook drivers actually feel. It decides whether the title fight stays alive until the finale, whether mid-pack drivers have anything to race for, and whether one bad night ends a championship. GridChief ships F1 and NASCAR presets plus a fully custom builder, and the right choice depends on what you want your drivers to do. Here is how to think about it.
What the classic structures reward
F1 scoring (25-18-15 down to P10) is top-heavy: wins matter enormously and the points cliff after P10 means most of the field scores nothing. It produces sharp title fights between your fastest two or three drivers and not much else. NASCAR-style scoring pays deep into the field with small gaps between positions, which rewards showing up and finishing: consistency beats peak pace. A flat or linear structure sits in between. Ask yourself which behavior you want to reward: brilliance or attendance. For most club leagues, attendance is what keeps the grid full.
Score as deep as your grid
If you run big fields, score big fields. GridChief lets you define points down to P100, so a 45-car grid can pay points to every finisher. This matters more than it sounds: a driver running P28 with zero chance of points has no reason to finish the race, and half the attrition in big-grid leagues is drivers parking it once their night goes wrong. Even one point for finishing changes that math.
Drop rounds keep championships honest
Real life happens. A driver who misses one round to a family event should not lose a championship to someone slower who attended everything. Drop rounds fix this: with 12 rounds and 2 drops, only a driver's best 10 count. The standard advice is one drop per 5 to 6 rounds. More than that and attendance stops mattering, which hurts grids. If your league races multiple times per week, look at week-based scoring instead, where only the best result per week counts; we wrote a full guide to that separately.
Bonus points steer behavior
Bonus points are small numbers with outsized effects on how people drive. Fastest lap keeps front-runners pushing after the win is settled, and keeps mid-pack drivers in the race late for a consolation prize. Pole position makes qualifying matter beyond grid slot. Most positions gained gives a bad qualifier a reason to race hard rather than cruise. And the clean race bonus is the quiet hero of club racing: paying 2 or 3 points for a race under your incident threshold measurably calms down lap one. GridChief lets you set that threshold, so a clean race can mean zero incident points or simply fewer than your limit, which is the realistic standard for longer races.
Qualifying points, used sparingly
GridChief supports per-position qualifying points down to Q20. Used heavily, they let one strong Saturday decide a championship before the race starts. Used lightly (a few points for the top qualifiers), they make Saturday matter and reward one-lap pace as its own skill. If your league treats qualifying as a formality, skip them; if your drivers care about pole battles, a small table works well.
Decide your tiebreaker before you need it
Championships get decided on countback more often than you would expect. Most wins is the classic first tiebreaker, then most seconds, and so on. GridChief lets you configure tiebreak rules per season, and the time to choose is before round one. Announcing the tiebreaker in week 11 of a tied championship is how leagues lose drivers.
Three setups you can copy
The Friends League (8 to 15 drivers): NASCAR-style descending points to the last position, 1 drop round per 6, clean race bonus with a forgiving threshold, fastest lap point. Everyone scores, consistency wins, lap one stays calm. The Sprint Series (15 to 30 drivers): F1 preset, points to P10, fastest lap and pole bonuses, qualifying points Q1 to Q5, 2 drops in 12 rounds. Sharp racing at the front, real stakes on Saturday. The Big Grid (30+ drivers): custom linear table paying every finisher, most positions gained bonus, clean race bonus, 2 drops. Designed so P25 still has a race worth finishing.
Change it between seasons, not during
Whatever you pick, lock it for the season. Mid-season points changes retroactively reshuffle standings and feel like moving the goalposts, because they are. GridChief recalculates the whole season from results whenever you change the system, which is exactly why you should save those changes for the off-season. Run the season, see what behavior your system produced, and adjust for next year.