Check your platform is ready to launch

Use this list in the last days before launch, ideally in one meeting with the people who own each area. Tick a line only when someone has checked it on the public site or in the apps, not just in the Studio. The warnings mark the lines that cost money or a broadcast when they’re missed.

Brand and language

• Dark-mode logo, light-mode logo and favicon uploaded in Studio → System → Settings → Appearance → Branding.
• Brand and status colours applied, and light/dark mode decided, in Appearance → Theme.
• Site language chosen in Locale → Language, and interface wording read through in that language.
• Default currency and timezone set in Locale → Region.
• Renamed labels — Events to Fixtures, Shop to Pro Shop — edited in Locale → Translations.
• Social links, app-store links and copyright text filled in under Appearance → Footer.

Site, pages and search

• Modules you won’t launch with switched off in Studio → System → Settings → Content → Features.
• About, Contact, Terms and Privacy written and published in Studio → Library → Pages.
• Contact page recipients set, and a test message received in Studio → Library → Contact Inbox.
• Site title, meta description and social share image set in Appearance → SEO.
• One event pasted into a messaging app, with the right title and image in the preview. A homepage link shows your site title only, with no image.
• Your custom domain opening with a padlock in the browser, and the other spelling (with or without www) forwarding to it.

Money

• Every payment provider you use connected in Studio → Management → Payments → Gateways and switched from test to live.
• One small real purchase made, then refunded in the provider’s own dashboard.
• Plans, season passes and prices checked in Studio → Management → Subscription Plans, with any test plans hidden.
• Discount codes checked in Studio → Management → Coupons, with expiry dates and redemption caps set.
• Ticket prices and access windows checked on every event going on sale.

Email and notifications

• Outgoing email set up and enabled in Studio → System → Settings → Security → SMTP, with a from address on your own domain.
• A password reset requested from a viewer account, and the email received.
• The wording of automatic notifications — receipts, renewals, reminders — reviewed in Studio → System → Notification Templates.

Broadcast

• A full test event run end to end: live on web, phone and TV, ended, and its replay checked in Studio → Content → On-Demand.
• Encoder settings saved on the machine that will stream on launch night.
• Simulcast destinations tested, if you stream to other platforms at the same time.
• The broadcast console password known to the people who need it, and only them.
• Crew and scorer logins created and tested on the devices they’ll use.

Team and access

• Every staff member signs in with their own account and a role that grants only what they need.
• At least two people have full administrator access.
• The Require sign-in to watch decision made in Studio → System → Settings → Content → Viewer Access.
• Comments switched on or off on purpose, with a named moderator if they’re on.

On the day

1. 1
   Copy your bypass URL

   In Studio → System → Settings → System → Maintenance, copy Your bypass URL somewhere your team can find it.

2. 2
   Bring the site online

   On the same screen, click Bring site back online and confirm.

3. 3
   Visit as a stranger

   Open your homepage in a private window on a phone, sign up as a new viewer and play something free.

4. 4
   Watch the Dashboard

   Keep Studio → Dashboard open for the first hours. New sign-ups, orders and payments show there and in your notifications.