Pool Rules
These rules describe the app’s current mechanics. Commissioners should explain their group’s approval and entry settings before play. The app administrator manages the shared schedule and final scores.
1. Joining and roles
Create a group to become its commissioner, or enter an active invitation code in My groups. New accounts are not automatically enrolled. Group names are unique across the app, ignoring capitalization and normalized extra whitespace. Members can participate in multiple groups, with separate entries and results in each. Use the current-group selector to check where you are playing.
2. Completing an entry
Select one team for every game in the week and predict the combined score of the designated Monday tiebreaker game. Saving creates or updates a draft; use the submission action to send the entry. The server validates completeness and the weekly lock time. If multiple entries are allowed, each entry has its own number, picks, and tiebreaker. Turning multiple entries off prevents additional entries but does not remove existing ballots.
3. Weekly lock and progression
Weeks unlock sequentially within each season. A week is available for picks only after all earlier weeks in that season have been finalized by the app administrator through scoring. Merely passing a deadline or finishing the last game does not finalize the week. The first scheduled week has no previous-week requirement. Finalizing a previous week does not extend the next week's deadline. Place picks shows playable weeks first, locks future weeks, and places finalized weeks at the bottom for read-only viewing. Reminders are sent only for unlocked weeks.
All entries for a week use the administrator-configured weekly picks deadline; this is not an independent rolling lock for each game. The deadline shown in the app is the deadline to follow. Browser clocks, email delivery, or a previously opened form do not override server validation. Draft and rejected entries must be corrected and submitted before that time. A reminder is a convenience, not a condition for a deadline to apply.
4. Review and approval
When approval is required, member submissions become pending review and cannot be edited until rejected. Commissioners approve or reject their group’s pending entries. Rejection includes a reason and permits editing and resubmission while the week remains open. Commissioners do not approve their own picks; their completed submissions become submitted immediately. Groups with approval disabled automatically submit members’ completed entries.
A settings change applies to future submissions, not a pending queue already created. Commissioners should review promptly. The current review system can resolve already-pending entries after the lock; it does not let a player edit the locked picks. Only entries in submitted status count for scoring. A late approval after results have been scored requires administrator review and rescoring to be reflected.
5. Visibility
Group views reveal approved/submitted picks after the weekly lock. Draft, pending, and rejected entries are not public approved picks. Commissioners can inspect pending submissions for review. Display names, entry numbers, and scores can identify participants in group views and result emails. These are group features, not a promise that another participant cannot copy information they can view.
6. Scoring and ties
A pick is correct when the selected team has the higher recorded final score. The current scoring calculation awards no correct pick for a tied game. Winners are determined independently in each group by most correct picks, then smallest absolute difference between the predicted and actual combined score of the designated Monday game. Going over is not separately penalized. If both measures remain equal, entries are co-winners; entry order does not break that tie.
Example: with an actual Monday total of 45, predictions of 42 and 48 both have a difference of 3. If those entries also have equal correct-pick counts and are best in their group, both win. There is no in-app financial payout attached to a win.
7. Final results and corrections
The app administrator records game scores and runs scoring after all games have final status and the designated tiebreaker has a final total. A results email is generated when scoring runs; the app does not independently settle results just because the last game ended. Re-scoring unchanged data does not repeat the same result emails. Corrected data may produce updated winners and another results email.
8. Postponed, cancelled, or unusual games
The current app has no automatic blanket policy for voiding cancelled games or replacing a missing Monday tiebreaker. A non-final game blocks scoring. Commissioners should escalate unusual schedules to the app administrator, who should explain the handling to affected groups before results are finalized. Do not assume an absent game is automatically a win, loss, refund, or excused pick.
9. Questions and disputes
Contact your commissioner about review decisions and group settings. Use support for schedule, scoring, security, or technical issues. Include the exact group, week, and entry number, expected behavior, and relevant times. Group-specific arrangements outside these mechanics must not misrepresent what the software enforces. There are no app-collected fees, app-held funds, or app-paid prizes.