Account access and the editorial watch-party companion
This route is editorial. The desk does not operate an account system. The watch-party companion describes a pattern the desk recommends for following a tournament schedule.
Editorial independence
Sources cited · Updated 2026-08-04 · No invented fixtures · No fabricated rosters
Account access
Where to watch and the watch-party companion
This route is editorial. The desk does not operate an account system. The watch-party companion below describes a pattern the desk recommends for following a tournament schedule: pick a timezone, pick a broadcast platform, pick a viewing context.
If a comparison or route is referenced in editorial copy, the route is disclosed in line. The desk does not embed external destinations in editorial HTML.
Watch-party companion
Three steps to a watch-party that matches the schedule
- Pick a timezone. The desk's match ledger carries the start time in UTC; convert once and stick with it for the week.
- Pick a broadcast platform. The viewing matrix tells you which platform carries the broadcast by region.
- Pick a viewing context. The desk recommends a single match at a time for the first match of a watch-party, then two matches for the second session.
Disclosed route
Comparison route disclosure
Where the desk references a comparison route in editorial copy, the route is disclosed in line with a one-line description of the route's purpose. The route is operated on a first-party basis.
Disclosed first-party route
/Login/playnow
Watch-party shape
What the watch-party companion covers
The watch-party companion covers three surfaces: timezone conversion, broadcast platform selection, and viewing context. The surfaces are independent — a reader who already knows the timezone can skip the first surface and start at the second.
The companion is editorial. The desk does not operate an account system, and the companion does not require sign-up. Where a comparison route is referenced in the companion, the route is disclosed in line.
Route disclosure
What the disclosure block covers
The disclosure block names the first-party route the desk uses for editorial comparison references. The route is operated on a first-party basis; the desk does not embed external destinations in editorial HTML. The disclosure block is published on this route and on the responsible-play route.
Where the desk updates the route, the disclosure block is updated on the same day. Where the desk retires a route, the disclosure block is updated on the next refresh.
Watch-party shape
What the watch-party companion covers
The watch-party companion covers three surfaces: timezone conversion, broadcast platform selection, and viewing context. The surfaces are independent — a reader who already knows the timezone can skip the first surface and start at the second.
The companion is editorial. The desk does not operate an account system, and the companion does not require sign-up. Where a comparison route is referenced in the companion, the route is disclosed in line.
Route disclosure
What the disclosure block covers
The disclosure block names the first-party route the desk uses for editorial comparison references. The route is operated on a first-party basis; the desk does not embed external destinations in editorial HTML. The disclosure block is published on this route and on the responsible-play route.
Where the desk updates the route, the disclosure block is updated on the same day. Where the desk retires a route, the disclosure block is updated on the next refresh.
Who uses the companion
Three reader profiles the desk has in mind
- The first-time watcher who has not yet picked a timezone. The companion's first surface (timezone conversion) is the surface this reader opens.
- The platform switcher who already knows the timezone but wants to compare platforms. The companion's second surface is the surface this reader opens.
- The viewing-context planner who is planning the second session of a watch-party. The companion's third surface is the surface this reader opens.
Updates
How the companion stays current
The companion refreshes when the calendar ledger refreshes — every Monday and on every Tier 1 release. The refresh date is published in the methodology block.
Where the companion's timezone conversion is wrong for a specific region, the desk routes the correction through the contact page rather than overwriting the conversion silently.
FAQ · login
Frequently asked questions, in editorial voice
The desk answers the most common reader questions about this surface in editorial voice. The FAQ is editorial — the desk does not invent answers; the answers cite the surface that already carries the answer.
Does the companion require sign-up?
No. The companion is editorial and read-only. The desk does not operate an account system.
What does the companion cover?
The companion covers three surfaces: timezone conversion, broadcast platform selection, and viewing context. The surfaces are independent — a reader who already knows the timezone can skip the first surface.
What does the disclosure block carry?
The disclosure block names the first-party route the desk uses for editorial comparison references. The route is operated on a first-party basis; the desk does not embed external destinations in editorial HTML.
Where do I find the source hierarchy?
The desk's source hierarchy lives on the methodology page. Every dossier, ledger row and match note carries one of four tiers: Tier 1 (League/Official), Tier 2 (Verified org), Tier 3 (Established media), Tier 4 (Community).
What does the source badge tell me?
The source badge tells you what the desk trusts about the row. A Tier 1 source is a league announcement; a Tier 2 source is an org confirmation; a Tier 3 source is a named reporter; a Tier 4 source is a community post the desk has not yet verified.
How does the desk promote a row's tier?
The desk does not promote a row's tier by editorial decision. A Tier 4 row carries a rumor badge and stays Tier 4 until a Tier 1 or Tier 2 source confirms it. The desk's case for the no-promotion rule is that an editorial promotion would conflate the desk's confidence with the source's confirmation.
How often does the surface refresh?
The surface refreshes weekly on Monday and on every Tier 1 release. The refresh date is published in the methodology block at the foot of every route.
How do I subscribe to updates?
The desk's RSS feed at /feed.xml carries every news desk story. The LLMs manifest at /llms.txt carries the editorial surface as a single document.
How do I file a correction?
Corrections are routed through the corrections email at corrections at esportswagerin dot com. The desk verifies the correction against a Tier 1 or Tier 2 source and updates the row within 48 hours.
Extended notes
Why this route exists without an account system
This route exists without an account system because the desk's editorial surface is its product. The route covers the watch-party companion — a pattern for following a tournament schedule that pairs timezone conversion, broadcast platform selection, and viewing context. The three surfaces are independent.
The route is editorial. The disclosure block names the first-party route the desk uses for editorial comparison references; the route is operated on a first-party basis. The desk does not embed external destinations in editorial HTML.
Where the watch-party companion is wrong for a specific region's timezone, the desk routes the correction through the contact page. The corrections log lives on the methodology page; the previous wording is kept for context.
Publication
How the watch-party companion stays current
The companion refreshes when the calendar ledger refreshes — every Monday and on every Tier 1 release. The refresh date is published in the methodology block.
Where the companion's timezone conversion is wrong for a specific region, the desk routes the correction through the contact page rather than overwriting the conversion silently. The desk's case for the explicit correction path is that an unverified timezone would land on the desk as opinion.