The house rules
Editorial standards
Envelope Editorial is the house desk behind Envelope’s blog and data pages. Posts are drafted with AI assistance, but every statistic is computed by code from a verified winner dataset covering 2000–2025, and every draft must clear a gauntlet of independent fact-checking agents before it publishes. When a published number stops matching the data, the post is corrected and its updated date moves.
Updated August 2, 2026
The masthead
What Envelope Editorial is
Envelope Editorial is the desk that writes this site: the blog, the guides, and the notes on the data pages. It is a house byline, not a person, and not a pretend person either. There are no invented staff writers, no stock-photo headshots, no biographies for people who do not exist. If a real, named contributor writes something, the byline says so.
The desk has one beat: what twenty-six years of award-show results actually say, and how to use that at your watch party. We are not critics, and we are not an academy. We keep score.
The dataset
Where the numbers come from
Every statistic we publish comes from one place: Envelope’s own winner history for the Oscars, Emmys, Grammys, and Golden Globes, covering 2000 through 2025. A result earns its verified flag only after a second, independent source corroborates it, and the whole dataset is validated every time the site builds. A malformed file fails the build instead of shipping a bad number.
The numbers themselves are computed by code from that dataset at build time. Nobody types “1 in 26” into a post; the code counts to 26 and reports back. The same dataset we compute from is public in the data explorer, so you can check our arithmetic whenever the mood strikes.
The robots
How we use AI
Posts are drafted with AI assistance. That is worth saying plainly, because the failure mode of AI writing is confident nonsense, and the desk is built around not shipping any.
The rule is simple: the model writes sentences, code produces numbers. Every figure in a draft has to match a value the dataset can actually produce, and a battery of machine checks runs on every post before publish: winner names against the record, percentages against the arithmetic, internal links against pages that exist, superlatives against the years we actually hold.
We also audit the checker itself. Every run plants known-false claims in a copy of the post (a wrong winner, a flipped number, an invented nominee) and confirms the checks catch every one. A fact-checker that never finds anything might be accurate, or might be quietly broken; the planted lies are how we tell the difference.
The gauntlet
How a post earns publication
No post ships on the strength of one model’s confidence. Before publication, every draft runs a gauntlet of independent fact-checking agents, each with a single specialty and a veto. A claim-mining agent reads the draft and extracts every checkable assertion, from winner names and years to percentages and superlatives, into a structured ledger. Each claim in that ledger is then verified separately against the dataset: names against the record, arithmetic against the raw counts, internal links against pages that actually exist.
A final roundtrip agent re-reads the finished prose cold and confirms it still says exactly what the data says, which catches the subtle drift that creeps in when a sentence gets reworded. One failed claim holds the entire post. The gauntlet is allowed to say no, and a held post does not ship until every flagged claim is fixed or cut.
Corrections
When a number stops being true
Award history grows a new row every season, so a sentence that was true in March can be false by the next ceremony. Every claim we publish is recorded, and when the underlying data changes, a drift monitor re-evaluates the published claims and flags any sentence the dataset no longer supports.
A flagged post gets corrected, and only then does its updated date move. We do not bump dates for cosmetic edits, and we do not quietly rewrite the record: the fix comes first, the fresh date second. When the mistake is ours rather than the calendar’s, the same process applies, with somewhat more wincing.
Spot the difference
Fact, analysis, or prediction?
Three kinds of sentence appear on this site, and they should never be mistaken for one another.
Historical fact
What the record says. “The defending champion repeated once in 26 years” is a fact: computed from the dataset, checkable by anyone, and machine-verified before we publish it.
Analysis
What we make of the record. When we call a category chalky or an upset historic, that is our read of the numbers. The numbers underneath are verified; the interpretation is ours, and you are welcome to argue with it.
Prediction
A guess with receipts. History says what usually happens, not what will happen next. Nothing we publish is a promise about who wins, and no ballot strategy comes with a warranty. The uncertainty is the fun part.
The tip line
How to report an error
Spotted a number that looks off, a winner we miscredited, or a claim that does not hold up? Email cmtemkin+envelope@gmail.com with a link to the page and the sentence in question. The report goes to the person who runs Envelope and gets checked against the dataset. If you are right, the post is corrected and its updated date moves. If you are not, you get the receipts, kindly.
Check our work
The dataset behind every number on this site is public. Browse it yourself, envelope by envelope.