Write the fixture in the order it will be played. Show who plays each game, how many legs decide it, and how that game contributes to the team result.
This example uses six players per side and one board. It is a local format, not a rule that every darts league follows.
Sample fixture
Play six singles games followed by three doubles games. Each singles game is best of three legs; each doubles game is one leg. Award one match point per game won.
| Stage | Games | Players per side | Match points available |
|---|---|---|---|
| Singles | 6 | One per game | 6 |
| Doubles | 3 | Two per game | 3 |
| Total | 9 | Six on the roster | 9 |
Every player appears once in singles and once in doubles. Nine available points mean the team match cannot finish level if every game is completed and awarded.
The singles section needs 12–18 legs; doubles adds three. That gives 15–21 legs for the evening. Estimate time from your group’s actual pace, then allow for practice darts and player changes.
Before the first leg
Captains submit lineups using stable player names. Decide how you choose the starting side and whether it alternates in later legs. Confirm the starting score, finishing rule, and any league rule for an unfinished leg.
Name the scorer and the person responsible for the accepted result. Players should know when to challenge an entry and who can correct it.
Substitutions and absences
Publish whether a substitute can play both sections and when the lineup locks. If someone is absent, apply the stated forfeit or replacement rule. Don’t improvise a new rule after seeing which player is missing.
Match report
Record the players, each game winner, and legs won. Have both captains confirm the final team points before leaving. Keep the individual results so a disputed 5–4 team total can be checked later.
An app must support this whole fixture if you want it to administer the night. A scorer that handles one 501 leg may still require a separate team results sheet.
Play now