This page says who writes FF Beacon, where the numbers on it come from, which parts are written by a person and which are produced by software, and what happens when something is wrong. The short version: one person is responsible for everything published here, and nobody pays to change what a page says.
1. Who is responsible
FF Beacon is built, written and published by Michael, a fantasy manager of twenty seasons who is blind and plays by the numbers. His background is on the author page, and the reasons the site exists are on the About page. There is no staff, no parent company and no outside editor. When a page is wrong, it is his mistake to fix.
2. Independence and money
The site is self funded. Today the money it takes in comes from two places: donations, and the Personal Team Review, a written review of one team that a reader can buy. Neither buys a better ranking, a kinder trade grade or a mention anywhere on the site, and the rest of the site is free to use.
Advertising would be a third source if it runs. An ad on a page is served by Google, which chooses it. An advertiser has no say in what is written and never sees a page before it is published. The Privacy Policy says what serving an ad involves. There is no sponsored content today, and if a sponsor ever backs a tool or an edition, the page will say so in words beside the thing sponsored.
FF Beacon is a fantasy football site. It is not a sportsbook, it takes no bets, and nothing on it is betting advice. Where a weekly edition shows a point spread or a total for a game, that is context for how the game was expected to go, not a recommendation to wager on it.
3. The guides
Every guide carries Michael's byline, the date it was published and the date it was last updated. A guide explains a method the site really uses, so when the method changes the guide is rewritten and its updated date moves. A date is never changed to make an old page look new.
A guide defines a term where it first uses it, and shows the arithmetic behind a claim instead of asking you to take it on trust. If you cannot follow one, that is a fault in the guide, and worth telling us about.
4. The Beacon Brief and its Relays
The Beacon Brief has two main kinds of page, and they are made differently.
Relays
A Relay is a short report of something an NFL reporter posted: an injury, a signing, a depth chart change. A Relay is an automated summary of the reporter's post, and each one names the reporter it came from. It is published once a software check confirms that the names and numbers in it are in the post. One that fails the check is held back for Michael to look at.
A Relay is not original reporting and does not claim to be. Relays are kept out of search engines on purpose, because a summary of someone else's report is not a page that should compete with it. Older single-story articles in the Brief were produced the same automated way and are kept out of search engines too.
Weekly editions
A weekly edition is the long read: the week's games, how the projections did, injuries, and what to do about it. The research for an edition is done with the help of a language model, which gathers material from three places only: the week's Relays, numbers the site computed from its own data, and pages it fetches to check that a report is still true. Its instructions forbid it from bringing back a roster, a timeline or a contract detail that is in none of those.
Michael puts each edition together from that research. He reviews all of it, rewrites it, edits it, and decides what the edition says. No edition is published automatically: one goes live only when he approves it. The charts, tables and score cards in an edition are drawn by the site from its own data, so a figure in a card is the stored figure and not a number somebody typed.
5. Where the numbers come from
Player values come from the value source you choose, and the page names the source by name wherever a value appears. A source is only offered for the scoring formats it really publishes. Where a source defines a format as a formula over its own base values, we apply that formula instead of inventing a number.
League data and most stats come from Sleeper. Weekly projections come from Sleeper or from FF Beacon's own model, and the page names which one it is showing. Projections are rescored under each format's own rules, and inside a synced league under that league's own scoring settings. Historical rosters in the games come from the nflverse data releases, and the game lines in a weekly edition come from a betting odds data feed. The league models and how each is calculated are set out in How FF Beacon Works.
When a number does not exist, the page says so in words. No value source prices individual defensive players, so a defender shows "No market value" and never a zero. A week that has not been played shows a projection labeled as a projection, and a model that has not been calculated for a league says that it has not, in place of a figure that would be believed.
6. Where language models are used, and where they are not
Language models are used for research: summarizing a reporter's post for a Relay, and gathering the material for each weekly edition, as described above. The guides and the editions are written by Michael. Language models do not grade trades. A trade verdict and every reason printed under it come from arithmetic and fixed sentence templates, so each sentence cites a figure that is on the same screen and can be checked against it. Projections and the league models are calculations, not generated text.
One more place a model can appear: FF Beacon's own player values are built from a formula, and that formula can include a small, capped adjustment suggested by a language model. Values from the other sources are shown as those sources publish them.
7. Corrections
If something here is wrong, say so through the contact page or by email to michael@ffbeacon.com. Name the page and what is wrong with it. A factual error in a guide or an edition is fixed on the page and the updated date changes with it. A wrong number that comes from a calculation is fixed in the calculation, so every page that uses it is corrected together.
We do not quietly delete a page to make a mistake disappear, and we do not change what a past edition said about a game after the fact, beyond correcting an error. An older edition may be rebuilt into a newer page layout; when that happens it keeps its address and its original date.
8. What readers post
Signal profiles, ranking boards and wall posts are written by the readers who own them and are their views, not the site's. Wall posts and comments carry a Report control for signed-in readers, and reports are reviewed by a person. To report a profile or a ranking board, write to us. The Terms of Service set out what may be posted.
9. Changes to this policy
When how the site is written changes, this page changes with it and the date at the top moves. Questions about any of it go to michael@ffbeacon.com.