Require a verified rating before they register.

Two gates, one decision

Set the default once on your tournament or league — it cascades to every new division. Each division can override either way.

How it works

• Flip Require DUPR sync or Require Club Rating in the Default Format section of your tournament or league create form. Every new division inherits the setting.
• Each division has its own override checkbox. Mix and match — open one division, gate another.
• Players see a "DUPR required" or "Club rating required" badge on the division card before they click Register, so there are no surprises at checkout.
• Backend enforces on every entry point — web, mobile, AI chat. The gate returns a clear remediation URL so the player knows exactly how to unblock.
• Organizer-added registrations (you adding a player manually from the admin) bypass the gate by design.

Why it matters

Skill-bucketed events stay fair when every player walks in with a verified rating. The DUPR gate keeps strangers from sandbagging an event with no skill history. The Club Rating gate lets clubs with their own evaluator-driven rating system run internal events where only members in good standing — rated by your coaches — can enter.

The defaults cascade so you don't have to flip the toggle on every division. The per-division override is there for the edge cases — e.g., gate the Pro divisions but leave the Open Beginner division ungated.

What the player sees

On the public event page, every gated division gets a colored badge next to its name and capacity pill. If they don't meet the requirement and click Register, the server returns a 403 with a one-line explanation and a link to sync DUPR or contact the club for a rating.

No silent failures. No fake-form-submit confusion. The requirement is visible before the click.

Unrated players (N/R) get a sensible default

Players with a synced DUPR account but no numeric rating yet — DUPR returns "NR" — can register for any open division, even one with a min/max DUPR cap. The cap doesn't apply when the rating is unknown, so brand-new DUPR users aren't locked out of the events that finally give them a rating.

You still see exactly who showed up unrated. The Teams page filters by DUPR rating: At least one N/R (N) in a single click, and every unrated player gets an orange N/R badge next to their name in the team row. The status is captured at registration, so even if they get a rating mid-event, the report still surfaces them.

Gender and age gates, too

Lock a division to Men's, Women's, or Mixed, and/or set a min/max age band. Wrong-gender divisions are hidden entirely from the player's view — out of sight, out of mind. Right-gender players outside the age band see the division sorted to the bottom, dimmed, with a "NOT ELIGIBLE" pill and a one-line explanation. Tap it and a premium pop-up tells them why and (when possible) gives them a one-tap way to fix it — connect DUPR, set gender, add date of birth.

Tournament defaults cascade to every new division. The "Demographic defaults" block in the create form pairs a gender select with min/max age inputs, exactly like the DUPR defaults above. Per-division overrides preserved.

• Inline gender + DOB capture card on the divisions tab when the player is missing the data the tournament needs. One-tap chips (Male / Female), HTML5 date picker for DOB. Saves and re-renders in place — never sends them to a settings screen.
• Backend gate composes with DUPR + Club Rating gates in deterministic order — gender first, then age, then ratings. Players get the most actionable error, not a confusing DUPR error for a division they can never join.
• Mobile parity in the same release. The division picker on iOS / Android hides + sorts + disables identically.

Scores submitted to DUPR — or not

If you've enabled DUPR scoring for the tournament and connected a DUPR club, the public event page tells players that explicitly. If you've only set the registration gate without enabling score submission, the page says so just as plainly:

• "Match scores from this event will be submitted to DUPR." — when the tournament is DUPR-sanctioned with a connected club.
• "A DUPR account is required to register. Match scores from this event will NOT be submitted to DUPR." — when you require the account for gating but don't run the event as DUPR-sanctioned.
• Both messages include a "Don't have one? Sign up at dupr.com" link so players who hit the gate can solve it in one click.