# The 2026–27 Hockey Pool Launch Checklist for Commissioners A practical, no-surprises checklist for choosing rules, inviting your group, testing the setup, and opening a 2026–27 hockey pool with confidence. Published: 2026-09-02T10:15:00+00:00 Updated: 2026-09-10T00:48:06.520259+00:00 Language: en Author: Dav Czar Reviewed by: Dav Czar ## Key takeaways - Choose the experience first, then select one of PoolForge's five supported formats. - Publish scoring, locks, tie handling, transactions, and time zones before invitations. - Test joining, mobile access, and the highest-risk workflow at least 24 hours early. - Record any post-launch correction instead of changing the contract silently. **A reliable hockey pool launch is mostly decided before the first invitation goes out.** The commissioner needs one clear format, a written scoring contract, tested access, and a short operating plan for draft day and opening night. This checklist turns those decisions into a sequence your group can verify. The 2026–27 NHL preseason begins September 19 and the regular season opens September 29. That leaves a useful preparation window, but not much room for an avoidable rules debate. Work from the deadline backward and make every decision visible. ## 1. Decide what the pool is trying to reward Start with the experience, not the settings screen. A casual office group may want low maintenance and cumulative points. A highly engaged group may prefer head-to-head matchups, a salary constraint, daily decisions, or an exclusive live draft. PoolForge currently supports five distinct formats: Standard, H2H, Salary Cap, Daily, and Draft League. - **Standard:** shared player availability and cumulative scoring with the lightest weekly workload. - **H2H:** scheduled opponents and matchup results for groups that enjoy a weekly rhythm. - **Salary Cap:** roster construction under a budget constraint. - **Daily:** a contest-date slate with daily lineup decisions and no trades. - **Draft League:** a live snake draft, exclusive player ownership, persistent exact-position rosters, and optional trades—without Daily-style per-game lineups. If the group cannot explain why its chosen format will be fun in one sentence, compare the options in the [PoolForge pool directory](/en/pools/discover/) before you configure anything. ## 2. Write the rules before you invite people Your rules are the pool's operating agreement. Keep them short enough to read and specific enough to settle a dispute. At minimum, record the roster slots, scoring values, tie handling, transaction rules, lock times, commissioner correction policy, and the time zone used for every deadline. Use a worked example. Suppose your scoring awards a fictional three points for a goal and two for an assist. Show a one-goal, two-assist night as seven points and label the example as illustrative—not a PoolForge default. A calculation that everyone can reproduce is more useful than a paragraph of legal-sounding copy. For H2H, define what wins a matchup and how ties work. For Salary Cap, state when cap compliance is checked. For Daily, explain the slate lock. For Draft League, publish the pick clock, timeout policy, exact position quotas, trade availability, and what happens if someone loses connection. ## 3. Build and test the pool as a participant would Create the pool early enough to inspect every review-screen value. The [five-step pool creation flow](/en/pool/create/) takes you from type through basics, settings, scoring, and final review. Do not treat the review step as ceremony: compare it line by line with your written rules. - Open the invitation in a private browser window. - Confirm the pool name, format, and commissioner identity are obvious. - Verify that a participant can join without receiving private commissioner controls. - Check the mobile layout at the width your group actually uses. - Confirm dates and times display in the intended time zone. You can also walk through the [read-only H2H demo](/en/demo/) to see how standings, rosters, matchups, and game-night context fit together before inviting your own group. ## 4. Send an invitation that answers the first five questions A good invitation should state: what the format is, when the draft or roster deadline occurs, how much weekly attention is expected, where the rules live, and whom to contact through the in-product support flow. Ask every participant to join at least 48 hours before the first hard deadline. “I saw the message” is not the same as “my account works.” Track three states: invited, joined, and ready. For a live draft, ready means the participant opened the room on the device and network they plan to use. For other formats, it means they understand how the initial roster is submitted. ## 5. Rehearse the highest-risk moment Draft League commissioners should run a short rehearsal with two or three people. Test the pick clock, order, reconnect behavior, queue, and timeout policy. Keep a paper copy of the order and a second way to reach participants. The rehearsal is not about predicting every failure; it is about making the recovery path familiar. For Daily pools, rehearse the first slate instead: confirm the contest date, lineup limits, and lock behavior. For H2H, inspect the initial schedule. For Salary Cap, test one compliant and one intentionally non-compliant roster so the error is understood before it matters. For the rehearsal, bring the [printable 2026–27 draft reference](/en/fantasy-hockey-draft-cheat-sheet-2026-27/) . Its verified historical statistics give participants a common reference; check the displayed source season and keep your pool’s custom scoring rules alongside it. ## 6. Use a launch-day control sheet When Commissioner check Evidence 24 hours before Membership, rules, time zone, draft or roster deadline Every participant marked ready 60 minutes before Device, connection, room access, backup contact Room opened and controls visible At launch Announce the official start and avoid unrecorded rule changes One timestamped commissioner message After launch Review standings inputs and resolve objective setup defects Correction note if anything changed ## 7. Freeze the contract, then communicate exceptions Once the pool starts, do not change a scoring value or deadline quietly. If an objective setup error must be corrected, document the old value, the new value, the reason, the effective time, and any affected result. Consistent process matters more than pretending a commissioner never makes a mistake. The final pre-launch question is simple: could a participant who missed the group chat understand the pool by reading the rules and the PoolForge review screen? If yes, you are ready to [create the pool](/en/pool/create/) . If not, fix the explanation before adding more settings. ## Frequently asked questions ### When should I invite participants? Invite them early enough to join and test access at least 48 hours before the first draft, roster, or lineup deadline. ### Should I change scoring after the pool starts? Avoid it. Correct only objective setup defects, document the change, state its effective time, and explain any affected result. ### Does Draft League use daily lineups? No. Draft League uses exclusive ownership and persistent exact-position rosters. Daily is the format built around contest-date lineup decisions. ## Sources - [NHL 2026-27 preseason schedule to begin Sept. 19](https://www.nhl.com/news/2026-2027-preseason-nhl-schedule-to-begin-september-19-2026) — NHL Public Relations - [NHL releases 2026-27 regular-season schedule](https://www.nhl.com/news/nhl-releases-2026-27-regular-season-schedule) — NHL.com