01 / Still moving
Unchanged is not final
A score can sit still while a player is still on the field, or while a late game has not started. Treat a quiet number as unfinished.
The commissioner job
Write the recap after the week is over.
A recap is a record, not a live blog. Wait for the host week to close, list every final, pick one lead result, and leave out anything the scores cannot prove.
Live scores can sit still and still be wrong. Write after the scoring week has rolled, then keep every final score next to the story.Why live scores lie
A quiet scoreboard is not a result.
A Sunday night lead can hold for twenty minutes and still flip. The commissioner job is to wait, then write what actually finished.
02 / Missing games
A full-looking week can have a hole
One missing matchup, bye, or blank score keeps the week from being a complete record. Do not invent the missing result.
03 / Later corrections
The host can still adjust
Sleeper can apply later stat corrections. A recap is a dated snapshot of confirmed scores, not a promise the source can never change.
The recap method
Do the evidence work first.
The writing is the last step. The commissioner job is to wait for the host week, list every final, and choose one lead result.
Wait, then list every final
- Wait until the host scoring week has rolled.
- List every team exactly once with a real final score.
- Leave scheduled byes and unpaired playoff slates visible.
- Pick one lead result: both teams, the winner, the margin.
What not to invent
- A winner the source has not confirmed.
- A missing score or an invented matchup.
- Play-by-play the league data cannot support.
- Quotes, injuries, or motives you cannot prove.
Leagueborn waits for Sleeper to move on and checks the complete week twice before a recap can publish. See how a weekly recap is built or read the fictional sample recap.
What Leagueborn does
The evidence parts can be automatic.
Leagueborn does the waiting, the complete-score check, and the ledger. Writing can phrase those facts. It cannot change them.
01 / Wait
Host week has to roll
Leagueborn keeps live scores labeled live until Sleeper advances beyond the scoring week, unless the league season is already complete.
02 / Confirm
The same scores, twice
The complete week is read twice, at least 15 minutes apart. If any score changes, confirmation starts again.
03 / Keep
Every final stays visible
The published edition keeps every final score beside the story so anyone in the league can check the recap against Sleeper. After it publishes, send the recap to group chat.
Common questions
What counts as a finished week?
The host has moved on, every matchup has a real score, and nothing in the recap was invented to fill a gap.
- When should I write a fantasy football recap?
- After the host platform has moved on from the scoring week and every matchup has a real final score. A quiet Sunday night score is not enough.
- Can I write the recap from live scores?
- No. Live scores can sit still while a game is still on, then flip a matchup later. Treat live numbers as unfinished until the host week rolls.
- What should a recap never invent?
- Do not invent a winner, a missing score, a play-by-play, or a quote the league data cannot support. If a matchup is missing, leave the gap visible.
- What does Leagueborn automate in a recap?
- Leagueborn waits for Sleeper to move on, confirms the complete week twice, lists every final score, and keeps writing from changing the result.
See a finished week written down.