Pickleball League Rules Template (Copy, Adapt, and Actually Use)

Most leagues don't fall apart because nobody can play pickleball. They fall apart because the rules lived in the commissioner's head, got rewritten mid-season, or never covered the situations that actually happen: absences, lineup disputes, weather, and "who decides this?"

This is a practical rules template for a team-based rec pickleball league. Copy it into a Google Doc, adapt the brackets, and publish it before week one. Where the Five Player Rec (FPR) format has a specific answer, this template points there so you don't invent a second system by accident.

1. League identity and season

• League name: _______________
• Season: _______________ (start date → end date)
• Night / time / venue: _______________
• Division / skill band: _______________ (how you define it — DUPR range, self-rate, or commissioner judgment)
• Number of teams: _______________
• Regular season length: _______________ weeks / rounds
• Playoffs: yes / no — format: _______________

State the season in writing. "We'll figure out playoffs later" is how you get arguments in week seven.

2. Eligibility and registration

• Players must register by _______________ and pay dues of $_____ by _______________.
• Rating policy: DUPR only / self-rate / either / none. (Pick one and stick to it.)
• Minimum age / facility waiver requirements: _______________.
• Late adds: allowed until _______________ with commissioner approval.

Keep registration boring and complete. Incomplete profiles become match-night problems.

3. Rosters and team size

Default FPR recommendation: five rostered players per team. The fifth player is in the rotation, not a bench warmer who only appears when someone flakes. See how many players per team and the Handbook section on why five players.

Template language you can paste:

> Each team consists of five rostered players. Positions and rotation follow the league format document. Outside substitutes are not used for a single absence when four rostered players are present.

If you run a different size, write the absence rules explicitly — don't leave them implied.

4. Captains and responsibilities

• Each team has one captain (optional: one assistant captain).
• Captains submit lineups by _______________ before match start.
• Captains are responsible for communicating schedule changes to their roster.
• Captain selection happens before the draft; captains should be of comparable skill so the draft can balance the rest of the pool. (See the Handbook on captain selection.)

5. Draft and team construction

Choose one and document it:

• Snake draft with peer ratings / Combine Day / draft survey
• Commissioner-assigned teams
• Returning teams with limited free-agent adds

If you draft, write:

> Draft order, timers, and roster finalization follow the published draft procedure. Once the draft ends, rosters are locked except for commissioner-approved replacements.

More context: draft format ideas.

6. Schedule, weather, and venues

• Matches are scheduled by the commissioner; the master schedule lives at _______________.
• Weather cancellations: decided by _______________ by _______________ time.
• Makeup policy: _______________ (next open week / designated makeup night / cancel without makeup).
• Court assignments: _______________.

One source of truth for the schedule. Not the group chat.

7. Match night rules

Adapt to your format. For FPR-style play, the full match structure (10-game series, P1–P5 positions, partnerships) is defined in the FPR Handbook. At minimum, publish:

• Match start time and warm-up window
• How lineups are submitted and when they lock
• Whether the trailing team sees the opponent's lineup first (FPR underdog rule)
• Scoring method per game and how a match is won
• Tiebreaker procedure (if any)
• Forfeit conditions (e.g., fewer than N players by start + X minutes)

8. Absences and substitutes

This section prevents 80% of mid-season drama. Write the policy you will actually enforce:

1. Players notify their captain by _______________ when they will miss.
2. With one absence and four present: follow format rotation (no outside sub required in FPR).
3. With two absences: _______________ (format rules / reschedule / forfeit threshold).
4. Outside substitutes: allowed / not allowed — if allowed, rating and eligibility limits: _______________.

Background reading: handling absences.

9. Standings, playoffs, and disputes

• Standings ranking: match wins, then _______________ (e.g., games won, game differential).
• Playoff seeding: _______________.
• Score disputes: raised within _____ hours to the commissioner; commissioner's decision is final unless _______________.
• Code of conduct: respect opponents and facility staff; ejections and warnings decided by _______________.

10. Dues, refunds, and communication

• Dues cover: _______________.
• Refund policy: _______________.
• Official announcements: _______________ (league app / email / both).
• Group chats are optional social channels, not the rules archive.

How to publish this without creating a second rulebook

1. Fill the blanks above.
2. Link the FPR Handbook for format specifics instead of rewriting them.
3. Share the doc (or league announcement) before registration closes.
4. Freeze mid-season rule changes except for safety or facility requirements.

A short rules doc that people can find beats a perfect rules doc that lives only in your notes.

Want the format and operations handled together? PlayFPR runs FPR seasons — draft, lineups, absences, standings — so your published rules match what the software actually enforces. Start with the free Handbook.