51 feature areas. Five days.

• Clone a prior tournament and re-date it — end dates, structure, and blackouts shift together — or save one as a template and choose whether its contests come along.
• Copy a division’s structure, duplicate a round, and create several divisions at once with settings carried across.
• Format presets drawn from the team count, and quick seeding with club·team labels and a wide preview.
• Bulk contest generation at round and division scope.
• A setup readiness checklist, so nothing is missing when you start placing courts.
• An organization-level catalog of venues and courts, pulled into an event instead of rebuilt for it, with a pattern-based bulk court generator, reorder, and default facility and rental details a single event can override.

• Challenge matches became first-class flow-chart groups with Winner and Loser advancement.
• Per-group scoring formats, applied consistently across settings, the score sheet, and the scoring app.
• Partial pool round robins set by matches per team, for when a full round robin will not fit the day.
• Day-two pools seeded from the previous round’s standings.
• Whole-division advancement with crossover sources, plus a crossover editor that renames both child pools and resizes them in one place.
• A bracket shape preview with live slot, bye, and match counts before any contest is generated, and a minimum-contests consolation mode.
• A rematch audit that counts the first-round and possible second-round same-pool rematches your advancement rules would create. It reports the risk and changes nothing.
• Pool work-team format maps covering pools of two to eight teams across one to four courts, each carrying its work-team assignment and court preference — including the standard six- and seven-team work orders — with realignment when the court format changes.
• Bracket seed numbers can be hidden on the public schedule, tournament-wide with a per-bracket-group override.

Seed hiding applies to bracket groups. Pool and crossover schedules rely on visible group seeds, so those always show.

• An auto-build wizard: choose dates, courts, and a wave pattern, preview every placement before it lands, and see any group the builder could not place along with the reason.
• Whole groups placed in one drag from a court chip, with a preview that draws a box per planned contest so lunch and blackout gaps are visible before the drop.
• Day window, lunch band, and warmup and transition gaps are enforced as you place — lunch behaves as a court conflict, and a cascade that would push play across a blackout is refused outright.
• Server-side validation that names the actual collision: court and blackout overlaps, and team double-books scored by role, so two playing assignments at once reads as high severity, a play-versus-work clash as medium, and two work duties as low.
• Bracket order integrity: a later stage scheduled before its feeder stage finishes raises a named alert on that day, and a move that would create one is refused.
• Two directors can work the same event. When another device writes the schedule, a prompt offers to refresh or keep editing and says plainly that continuing may overwrite the other editor’s changes.
• Delay or postpone, swap two contests in one batch, nudge a start with the arrow keys, filter the board to a single team, and work across days with multi-day move, copy-day layout, and an all-days occupancy strip.
• Undo for structure deletes and schedule edits.
• Regenerating a group that already has contests asks first, naming the contests that are scheduled or staffed; the matchups that survive keep their court, date, and time.

Minimum rest is flagged as a warning on the grid and in the build preview — it does not block a placement. The day window, lunch band, and blackouts do.

• Publishing gates the public schedule and snapshots contest times and courts. The next republish shows a diff of exactly what changed.
• A schedule change generates a notification scoped to the teams and staff it touches, rather than a blast to the whole event.
• A send preview shows the recipient list and the exact email before dispatch, reconciles the contacts that would be skipped, and lets you choose recipients selectively.
• Email coaches and email staff from inside the tournament, on separate send paths, so a message to officials never lands in a coach’s inbox by accident.
• Dismissible public announcements at info, warning, and urgent levels, for the things that do not need an email at all.

Text messaging is per deployment. Where SMS is configured, a short text goes alongside the email; where it is not, nothing sends and the email path is unaffected.

• Per-contest scoring PINs. A key opens exactly one match, so a work team that scored the previous match cannot reuse its PIN on the next one — and it needs no account of any kind.
• Keys are minted automatically, six characters, from an alphabet with no zero, letter O, one, or letter I, so a PIN called across a gym is unambiguous. An owner can rotate one at any time.
• A wrong, expired, or other-contest key is refused outright. It never falls back to whatever account happens to be signed in on that device.
• Submit-final verifies with a staff PIN and updates standings and brackets, so a result does not need a second data-entry pass to move the tournament forward.
• Offline drafts, retry, forfeit recording, and scorekeeper name capture, for gyms where the wifi is not the strong point.

Watching a live match stays public — anyone with the link can follow it. Only submitting a score is gated, and it opens three ways: a tournament admin, a signed-in staffer holding your organization’s scoring permission, or anyone holding that contest’s PIN.

• A searchable public team directory including staff names, and club pages showing next match and record.
• Follow a team and it pins to that browser. It is a local convenience, not a profile or a subscription — there is nothing to sign up for.
• A court monitor: a now-and-next board with one card per court location, plus a denser kiosk layout with a clock and auto-refresh for the front desk.
• Public pages refresh badges, scores, and standings from a batched results read, so a phone in the stands and a laptop at the desk agree.
• Team calendar subscriptions carrying the venue as the event location, plus directions, sharing, and an offline QR poster on the venue strip.
• Pool sheets and brackets print straight from the public page, and the printed pool sheet adds blank score lines and page breaks for the scorer’s table.
• A link-recovery screen for the parent who lost the link: paste the public link, or type the event’s code, and it opens. Your followed teams and recently viewed events live there too, stored only in that browser.

A draft schedule deliberately returns an empty calendar feed — nothing is promised before you publish. Tournaments are not listed in a global directory, and recovery needs the whole code, so it can never enumerate an organization’s events.

• Public self-serve registration for a single team, and a multi-team pass for club directors with shared contacts and a per-team division, name, and code.
• Multiple role-based contacts per team — coach, director, captain, and other — so a schedule change later reaches the right person.
• A configurable USAV or AAU team code: hidden, optional, or required, per tournament.
• Per-division early, regular, and late registration windows, each with its own open and close time and its own fee, plus a tournament-level late surcharge. A division can also close registration on its own, and its fee is authoritative, so a free division is free.
• A registration desk that approves or waitlists an entry and keeps the fee record straight: entry-fee calculation, balances, payment status, and admin recording of payments, voids, and refunds.
• Every entry ends in a printable confirmation.

Entry fees are records. WNY Athletics calculates what a team owes, tracks the balance and the status, and lets an admin record what was actually collected. It does not process card payments, and money never moves through the platform.

• Day-of team check-in with its own history, so you can see what has already been checked in.
• A searchable check-in desk with each team’s contacts on the same screen.
• Add, edit, or remove a team’s contacts from the desk or the team drawer while the coach is standing in front of you.

• Availability windows with tokenized self-service: an official opens a personal link, with no account, and answers each event day as available all day, unavailable, or partially available with time windows.
• A mass availability request email with merge tags for the tournament, the dates, and each official’s own link.
• A bulk assign wizard that proposes a contest-by-role assignment for you to review before anything is written, shaped by fairness rules — maximum consecutive assignments, a required break after them, a same-court limit, and a team-repeat lookback.
• Overlap detection that names the conflicting match, both among the contests you are assigning and against assignments elsewhere in the event.
• Assignments are drafted and then published per contest, with the option to email the officials their work. An accept or a decline comes back onto the grid.
• Per-official rates by contest type — two sets, best-of-three, challenge — with daily and event minimums, certification level, and earned, issued, and owed rollups an official can see from their own link.
• Payroll closeout in bulk, with per-person amounts, check numbers, and memos, plus an export of the run. A voided row stays in place rather than disappearing.

Unconfirmed, unavailable, and out-of-window days are excluded from automatic assignment. A director can still assign someone by hand. The wizard proposes; confirming is still a decision you make.

• Team lifecycle statuses in the admin Teams panel, and bulk selection actions on the Teams board.
• Contacts that belong to the organization and survive individual tournaments, with derived and custom tags, known-contact autocomplete, and a Contacts panel of their own.
• Mass select with bulk email and bulk tag add or remove, and your selection preserved as you filter.
• Teams, staff, and rosters import by paste or by file, with a dry run and an editable preview before anything is written.
• A staff roster can be copied from another event in the same organization, so a returning official updates in place instead of arriving twice.
• Duplicate-placement warnings that name where a team already sits and offer to move it, and a seat badge on each flow-chart round that warns when the round’s seats do not match the previous round’s outbound teams.

• A searchable activity table: score corrections, match moves, and archives, each with a before-and-after view of what changed.
• Archive restore, and an archived list view, so an event put away by mistake comes back.
• A stable public link for every tournament that keeps resolving after the event is renamed — the link you shared in March still works in June.
• CSV export on every admin list, plus the payroll export, so the board’s spreadsheet is a download rather than a retyping job.
• A webhook when a schedule’s status changes, and a public standings read with caching headers, for a club site or a lobby display.

The webhook and the standings read are an early integration surface, not a published API. There is no versioned contract behind them yet, and we would rather say so than imply one.