Fantasy Football Weekly Logbook: How To Keep a Running Record of the Week
A weekly logbook keeps the important fantasy details in one place so your process can improve over time. It is not a full recap. It is a running record of decisions, signals, and lessons you will actually reuse.
Weekly Logbook Quick Reference
| Item | What to record | Why it matters | Mistake to avoid |
|---|---|---|---|
| Lesson | What mattered most | Gives the week focus | Trying to keep everything |
| Reason | Why it mattered | Preserves the logic | Writing only the result |
| Use | What changes now | Turns the logbook into action | Ending without a purpose |
How To Use The Logbook
Keep the entry short.
The logbook should stay readable.
Write the reason with the lesson.
That keeps the logic visible.
Use it in the next review.
The logbook should feed the next decision.
Common Mistakes
Writing a full report instead of a logbook entry.
Short is more reusable.
Leaving out the reason.
The lesson needs context.
Never revisiting the logbook.
The value comes from reuse.
Best Ball Note
Best ball weekly logbooks are useful for draft-room patterns, exposure shifts, and stack choices.
Worked Example: Tracking A Waiver Decision
On Tuesday, you add a backup running back because the starter missed practice and the backup played passing downs. On Sunday, the starter plays and the backup scores little. A shallow logbook says the add failed.
A useful logbook says the process was reasonable because the role path existed, but the injury did not open the door. That distinction helps you repeat good process without overreacting to one result.
Common mistake: using the logbook only to record winners and losers. The better use is to record the decision logic so you can separate process from outcome.
Logbook Sections
Use sections for injuries, waivers, lineup calls, role changes, and lessons. This makes the record easy to scan later. If everything is written as one paragraph, the logbook becomes hard to reuse.
The logbook should also include dates. Fantasy information changes quickly, and an injury note from Wednesday means something different from a status update on Sunday morning.
Review Cadence
Review the logbook once before waivers and once before lineups lock. That is enough. Constant review can turn into overthinking, but no review means the logbook never affects decisions.
What To Leave Out
Do not record every highlight, ranking change, or social-media opinion. The logbook should prioritize information that can change a move: player availability, role change, usage trend, waiver cost, trade angle, or lineup uncertainty.
Leaving information out is part of the system. A logbook that includes everything becomes another noisy feed, and the point is to make the week easier to review.
Worked Example
A useful logbook entry might read: “Waiver priority spent on short-term RB cover because two starters were questionable; process was correct even though the starter recovered by Sunday.” That preserves the decision context. Later, you can see that the move was about risk management, not panic.
Without the logbook, you might remember only that the waiver add did not start. That would teach the wrong lesson. The record protects the reasoning from hindsight.
Common mistake: using a logbook only to record final scores. Scores are easy to find later; the valuable part is why you made the decisions you made.
What The Logbook Should Capture
The logbook should capture deadlines, injuries, waiver claims, lineup pivots, trade discussions, and the reason behind any meaningful decision. It does not need to include every ranking or projection. The point is to reconstruct the week accurately enough to learn from it.
For fantasy managers handling multiple teams, the logbook is especially useful because the weeks blur together. A short note on why one roster made a move prevents that decision from being confused with a different team later.
Logbook Structure
Use sections that stay the same each week: Monday review, waiver plan, injury watch, lineup decision, and lesson. If you play dynasty, add trade notes and future-pick context. If you play best ball, add draft exposure or portfolio notes instead of lineup sections.
The consistency matters because it makes review faster. You should know where to look for the waiver reason or the injury note without rereading the whole week.
Turning Records Into Decisions
At the end of the week, mark one decision that should change your future process. Maybe you acted too early on an injury, ignored snap counts, or waited too long on a waiver backup. The logbook is valuable only if it feeds the next decision.
Do not let the logbook become a scrapbook. Keep the record practical and focused on repeatable decisions.
A weekly logbook keeps a running record of the week. Capture the lesson, capture the reason, and use the logbook later.
Logbook Review Questions
End the week with three questions: which decision mattered most, what information would have improved it, and what should change next week? Those questions turn the logbook from a storage place into a learning tool.
If the answer is always “nothing,” the logbook may be too shallow. There is usually one timing issue, assumption, missed signal, or useful confirmation worth carrying forward. Write the reason before the outcome is fully known whenever possible so hindsight does not rewrite the process.
For the record layer, see Fantasy Football Weekly Record. For the journal layer, see Fantasy Football Weekly Journal. Start at the learn hub for all resources.