Agree the format, match order, points system, tie-breakers, player eligibility, postponement policy, result deadline and dispute process before registration opens. Put one approved version where captains can find it.
Run a darts league from rules to final standings.
Use this eight-step framework to define the competition, publish a workable fixture programme, capture accepted results and keep every team clear on what happens next.
Collect the team name, home venue, captain contact, eligible player list and scheduling constraints. Name a primary and backup captain so fixture communication and result confirmation never depend on one unavailable person.
Choose the season dates, rounds, home-and-away pattern and rest weeks. Check venue capacity, holidays and known conflicts before publishing. Give every fixture a stable reference that will also identify its match sheet and result.
Confirm the date, venue, start time, line-ups and scoring method. Make the official match sheet and order of play available before the first leg. Decide who is authorised to record corrections if a player or line-up changes.
Record each leg and match through the agreed official workflow rather than copying only the final score into a separate table. Keep players, teams and the scheduled fixture attached to the scoring record so the result can be checked later.
Require both captains or designated officials to review the submitted result. Route disagreements to a visible dispute process with the relevant match context. Do not update the accepted standings from an unconfirmed message.
Update the public competition view after confirmation so teams can see completed results, the current table and upcoming matches. Apply points and tie-breakers consistently, and preserve corrected results with a clear audit trail.
At the end of the season, confirm the final table, close unresolved disputes and retain fixtures, results and player records. Joony Darts connects supported league administration, captain confirmation, mobile scoring and public league pages so organisers can keep this operating record in one system.