Story tips, correction requests and methodology questions are routed through the editorial desk. The desk responds to verifiable pitches and to corrections that cite a Tier 1 or Tier 2 source.
Story tips, correction requests and methodology questions are routed through the editorial desk. The desk responds to verifiable pitches and to corrections that cite a Tier 1 or Tier 2 source.
Editorial email: editorial at esportswagerin dot com
Methodology questions: method at esportswagerin dot com
Correction requests: corrections at esportswagerin dot com
The desk publishes pitches that cite a Tier 1 or Tier 2 source and that the desk can independently date. The desk does not publish anonymous tips without an independent source path.
Corrections are routed through the corrections email. Each correction entry carries the previous wording, the corrected wording, the date and the source badge of the corrected information.
The corrections log lives on the methodology page. The desk does not silently edit history.
The desk responds to verifiable pitches within the cycle. The cycle is the qualifier window for the relevant event. The desk's case for the cycle-based response time is that a pitch that arrives during the cycle can be verified against the same week's Tier 1 sources.
The desk responds to correction requests within 48 hours of receipt. The desk verifies the correction against a Tier 1 or Tier 2 source and updates the row within the same response window.
The desk does not respond to pitches or corrections that lack a verifiable source. The desk's case for the verifiable-source rule is that an unverifiable pitch would land on the desk as opinion rather than as coverage.
Pitches that lack any of the three fields are routed back through the editorial email with a request for the missing field.
The desk responds to verifiable pitches within the cycle. The cycle is the qualifier window for the relevant event. The desk's case for the cycle-based response time is that a pitch that arrives during the cycle can be verified against the same week's Tier 1 sources.
The desk responds to correction requests within 48 hours of receipt. The desk verifies the correction against a Tier 1 or Tier 2 source and updates the row within the same response window.
The desk does not respond to pitches or corrections that lack a verifiable source. The desk's case for the verifiable-source rule is that an unverifiable pitch would land on the desk as opinion rather than as coverage.
Pitches that lack any of the three fields are routed back through the editorial email with a request for the missing field.
The desk's reply carries three fields. The first field is the verification path the desk used to confirm the pitch or the correction. The second field is the desk's reading on the story or the correction. The third field is the next step the desk will take.
Where the desk cannot verify the pitch or the correction within 48 hours, the desk replies with a status note rather than a substantive reply. The desk's case for the status note is that an unverified reply would land on the reader as opinion rather than as a desk response.
The desk replies to verifiable pitches, to correction requests that cite a Tier 1 or Tier 2 source, and to methodology questions that cite a methodology reference. The desk does not reply to anonymous tips without an independent source path; the desk does not reply to customer-care questions; the desk does not reply to commercial solicitations that do not match the editorial surface.
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.
The desk replies within the cycle. A pitch that arrives during the cycle can be verified against the same week's Tier 1 sources. Correction requests are verified within 48 hours of receipt.
The desk looks for the event, the source and the verification path. Pitches that lack any of the three fields are routed back with a request for the missing field.
The desk does not publish anonymous tips without an independent source path. The desk's case for the verifiable-source rule is that an unverifiable pitch would land on the desk as opinion rather than as coverage.
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).
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.
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.
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.
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.
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.
The desk publishes its email addresses in plain text rather than as mailto links. The desk's case for the plain text is that a mailto link would expose the address to a wider set of harvesters without changing the desk's response time. The plain text is human-readable; the reader can compose the address in their mail client.
The three addresses — editorial, method, corrections — are routed through the same inbox. The desk triages incoming messages into the three lanes within 48 hours of receipt. Where a message arrives without a verifiable source, the desk replies with a status note rather than a substantive reply.
Where a message arrives with a verifiable source but outside the desk's coverage scope, the desk replies with a routing note. The routing note names the editorial surface that does cover the topic and points the reader at the surface.
The contact page refreshes when the editorial desk's email triage changes — for example, when the desk adds a named beat reporter or when a methodology question type becomes common enough to warrant a dedicated address. The refresh date is published in the methodology block.
Where a reader needs an address the contact page does not list, the editorial email routes the request through the desk's triage. The desk's case for the single triage address is that a single inbox is easier to verify than a per-route address list.