Good TourneyHelp & Support

Your first tournament

Welcome to the Good Tourney web pilot. Start with your personal director invitation, then follow these steps on your phone, tablet, or computer. You do not need a ChatGPT account.

  1. Sign in and set a password

    Open the invitation Charles sent you and request a secure email link using the invited address. Open the newest email to finish signing in; check Spam or Junk if it is missing.

    If onboarding offers password setup, choose a password and select Save password and continue, or choose Skip to keep going. You can also create or change your password later in Password settings. Your old website password does not carry over. If you cannot access the invited email, contact Charles first.

  2. Bring over your old records

    Open Settings → Bring over your old records. If offered, connect your old account and sign in on the old website using the same email as the pilot. If records were prepared for you already, choose Check for records.

    Review the players, tournament history and exclusions. Resolve possible matches with players already in your library before choosing Import my records and confirming. You do not need to delete your existing players.

    Check your Players, past Tournaments, and a player’s history. If records are missing or look wrong, contact Charles. Doubles history can preserve team names without creating individual player profiles. Your old password does not carry over.

  3. Use your website records in the Apple apps

    In Good Tourney on your iPhone, iPad, or Mac, open Settings → Good Tourney Account. Sign in with your pilot website email and password. Signing in in a browser does not sign in the app.

    Open Players and imported tournaments → Review Players to Import. Uncheck players you do not want, and review possible duplicates before choosing an existing player to merge with. Players already imported appear under Already Imported.

    Imported players use the app’s iCloud sync across your Apple devices signed in to the same iCloud account. Imported website tournament history can be viewed in Website records. Website tournaments and app tournaments do not automatically sync with each other, and importing players does not keep later website edits in sync.

  4. Prepare the room

    On the device and network you will use, open Settings → Test venue connection. Then choose Tournaments → New Tournament.

    Review players or teams, tables, chip assignment, payments, side pots, and payouts. Fargo assignment uses your configured rating ranges; manual assignment lets you set chips. Paid-entry controls track payments and do not collect money.

    Choose Start Tournament, review the summary, and confirm when ready. Clearly name any practice event as a practice tournament.

  5. Run and share your tournament

    Use one device to edit. To switch devices, let the current editor finish syncing, then choose Take Over Editing on the new device.

    In Live Link controls, choose Enable Live Link and share the spectator link or QR code. Spectators do not need an account. Choose Back to tournament to return to directing.

    Open your tournament online before relying on its device copy offline. After reconnecting, keep it open until changes sync. Keep the browser’s saved data while changes are waiting, and compare device/cloud recovery choices before selecting one.

  6. Keep the final results

    Review Results and let them sync. Open Export and share results → Download JSON backup and keep the file somewhere you can find again.

    For Singles Fargo submission, choose Prepare Fargo email → Download Fargo results. Send the XLS file to the recipient shown. Check the attachment in your email service—opening a prepared email does not attach it automatically.

    After your first event, tell Charles whether the final results, spectator view, and saved records matched what you expected. Include any confusing steps.

Need a hand?

Include the tournament name, what happened, the approximate time, and your device and browser. Screenshots help. Keep passwords and sign-in links out of support messages.