Contact

Fantasy Projection Lab covers projection methodology, statistical modeling, and practical fantasy sports decision-making. This page explains how to reach the editorial and technical teams, what information to include for the fastest resolution, and what realistic response windows look like across different request types.

Service Area Covered

Fantasy Projection Lab operates at national scope within the United States, covering projection content for the NFL, NBA, MLB, and NHL — along with daily fantasy sports formats, dynasty leagues, best ball, and keeper formats. The resource addresses both casual seasonal players and deeply analytical users who want to understand the mechanics behind projection models, scoring format impacts, and backtesting methodology.

Editorial inquiries, methodology questions, data sourcing concerns, and factual corrections all fall within scope. Requests related to general fantasy advice — start/sit decisions, trade evaluations for specific personal leagues — fall outside the editorial mandate. For those questions, the FAQ and applying projections to draft strategy pages cover the structural thinking rather than individual decisions.

What to Include in Your Message

A message that includes the right context gets a substantively useful response. One that doesn't tends to generate a clarifying round-trip that delays resolution by at least 48 hours. To avoid that loop:

1. Subject area — Name the specific sport, position, or page in question. "NFL quarterback projections" is useful. "Your projections seem off" opens a door without a frame.
2. The specific claim or figure — If a methodology point or statistic appears incorrect, quote the exact sentence and identify the page by its URL path or title.
3. The basis for the concern — A named public source, a conflicting data point, or a clearly described discrepancy. The editorial standard on this site requires inline attribution for specific figures and penalty ceilings; the same standard applies to correction requests.
4. Contact type — Make clear whether the message is a factual correction, a methodology question, a partnership or licensing inquiry, or a technical issue (broken link, page error, formatting problem).
5. Technical issues — Include the browser, device type, and the exact URL where the problem appears. "The site doesn't work on my phone" describes a category; "The projection confidence intervals page fails to load on iOS Safari at the 375px breakpoint" describes a problem that can actually be diagnosed.

The difference between a correction request and a methodology disagreement is worth flagging upfront. Corrections address verifiable factual errors — a wrong percentage, a misattributed source, a statute cited incorrectly. Methodology disagreements involve interpretive choices about how projections are built, which inputs are weighted, and why certain adjustment factors are included or excluded. Both are legitimate. They just get routed differently.

Response Expectations

Editorial and factual correction requests receive an initial response within 3 business days. If a correction requires pulling source documentation or consulting the modeling team, the full resolution may take up to 7 business days — but the acknowledgment comes first.

Methodology questions that require substantive explanation are treated as editorial tasks. If the question surfaces a gap in existing documentation, the answer may appear as an update to a relevant page — the projection models explained or statistical inputs pages, for instance — rather than only in a private reply.

Technical bug reports are triaged within 1 business day for issues affecting page accessibility, and within 3 business days for visual or formatting issues that don't block content.

Partnership and licensing inquiries — data syndication, content licensing, methodology consulting — are reviewed on a rolling basis. Expect an initial response within 5 business days. These requests are assessed against editorial independence standards before any agreement is considered.

What not to expect: personal fantasy lineup advice, real-time projection updates via email, or responses to messages that don't include the information outlined in the section above. The how to get help page covers self-service paths for the most common questions.

Additional Contact Options

For users who have read through the FAQ and still have an unresolved question, the how it works and key dimensions and scopes pages cover the operational structure of the site in detail — including which sports are modeled, how update schedules work, and how projection outputs are meant to be interpreted.

Factual corrections carry the highest editorial priority. If a named source is misrepresented, a figure is wrong, or a methodology claim contradicts published research, that gets treated as urgent regardless of where it sits in the queue. The credibility of projection content depends on that standard holding, which means correction reporters are doing useful work even when — especially when — they're pointing out something inconvenient.

For context on how specific projection outputs should be read alongside uncertainty ranges, projection confidence intervals and floor and ceiling projections are the relevant reference points. Understanding the architecture of a projection before asking why a specific player's number looks wrong tends to produce sharper questions — and correspondingly sharper answers.