A fantasy league almanacinjuries, waivers and the league’s history, updated every Tuesday

Method

1. 1

   Put the rules in one place

   Copy your league’s settings page from the fantasy platform, or take screenshots of it, and give them to your assistant along with the old rules email. Ask it to build a Rulebook in know.sh with one finding per area: scoring, roster and lineup, waivers and the budget for bids, trades and vetoes, playoffs and tiebreakers, and the league’s own customs.

   Where the email and the settings disagree, ask your assistant to leave a proposed note rather than choose. Settling those is the commissioner’s job, and the league’s.

2. 2

   Fix the rulebook and share it

   Open the Rulebook and read every finding in the editor. Put the league’s own words back where the assistant tidied them away (“no trading with the defending champion’s team in week 13; tradition”), and file each rule change the league has voted on as a Decision with the date of the vote.

   Then press Share and pin the read-only link in the group chat. The league reads it on their phones; only the commissioner edits, and Revisions shows exactly when each rule last changed, which ends most arguments before they start.

3. 3

   Schedule the Tuesday run

   Create a scheduled task in your assistant for Tuesday morning, after Monday night’s game and before most platforms process waivers. In Claude, scheduled tasks are on the Pro, Max, Team and Enterprise plans; in ChatGPT, on every plan. Give it your scoring rules and the players on each roster, and ask for the weekend’s injury news, depth-chart changes and the best waiver targets per position under your scoring, each with a link to where it came from.

   When the result arrives, reply file this in know.sh as Week 5 of Season 2026. Some setups can file straight into know.sh during the scheduled run; that is newer and not every plan or connector supports it yet, so check Revisions after each run either way.

4. 4

   Trim the week in the editor

   Ten minutes on Tuesday: open the week’s finding and cut it to what the league will read. Keep the injuries that matter to a roster, the three or four waiver targets worth a bid, and the week’s result. Add the part no assistant can write: who lost to the worst team in the league, and what the group chat said about it.

   Injury news moves quickly. The NFL’s official injury reports come out from Wednesday to Friday, so a Tuesday report catches what happened over the weekend; managers should still check Friday’s game statuses before setting a lineup.

5. 5

   Keep the league’s history

   At the end of each season, copy the platform’s season summary, or screenshot it, and ask your assistant to add a finding to League history: champion, runner-up, the regular-season leader, the most points in a week, the worst trade. Over the years it becomes the book the league argues from.

   Mark the finding for each championship season as Key. The managers’ names recur across seasons, so the index gathers each manager’s championships, trades and worst weeks under their name.

6. 6

   Answer disputes with the text

   When a trade veto argument starts, don’t paraphrase the rule from memory. Ask your assistant: “Using know.sh, find the rule on trade vetoes in the Gridiron Irregulars Rulebook, quote it exactly, and tell me when it last changed.” Paste the answer and the link into the group chat.

   For anything the rulebook doesn’t cover, write the league’s decision as a new Decision finding the day it is made, so next season’s argument is already settled.