Closing line value is only useful if you can reconstruct what you actually bet and compare it with the market that existed later. That sounds obvious, but many betting logs begin with the final result and try to fill in the entry details afterward. By then the sportsbook screen has changed, the market has moved, and memory has turned an exact execution into an estimate.
The season kickoff is the cleanest moment to prevent that problem. Start logging from Week 1 and make the entry record complete before the game begins. You do not need a complicated dashboard. You need a consistent set of fields that lets you answer a simple question later: what price did I actually take, and what did the relevant market close at?
First, define what CLV record you are trying to preserve
Closing line value compares your executed bet with a later market reference, typically the relevant closing market. The important word is executed. A line you considered, screenshotted, or saw in another tab is not your entry if it is not the price at which the wager was placed.
If you want a refresher on the concept itself, use the closing line value explainer. The checklist below focuses on the operational side: preserving enough information at bet time that the comparison can be computed later without guesswork.
The minimum fields to log at bet time
A useful CLV record should make the wager uniquely understandable after the market has moved. Record:
- Event: the game or contest the wager belongs to.
- Market: spread, total, moneyline, player prop, or the specific derivative you actually bet.
- Selection: the side of that market you took.
- Entry line or threshold: the exact spread, total, prop threshold, or other market term attached to the wager.
- Entry price: the price attached to that line when your wager was accepted.
- Book or venue: where the bet was executed.
- Timestamp: when the wager was accepted, preferably in a consistent timezone.
- Model or rationale reference: which model, rule, or decision process produced the bet.
Those fields are not busywork. Together they identify the thing that needs to be compared with the close. If any one of them is ambiguous, your later CLV calculation can become ambiguous too.
Do not collapse the line and the price into one field
For markets that have both a threshold and a price, preserve both. A spread can move while the price changes. A total can stay on the same number while the price becomes more or less favorable. A player prop can move its threshold, its price, or both.
If your log only records “team spread” without the line and price, you cannot tell whether the later market moved toward your position. If it records only a price but not the threshold, you may compare two different bets as though they were the same market. A clean CLV log keeps the market terms explicit.
Use the actual accepted price, not the price you meant to take
Markets move quickly. You might click when one price is displayed and receive confirmation at another. For CLV purposes, the confirmation is the record that matters. The same applies if a sportsbook reprices the wager and asks you to accept the new terms.
The habit to build in Week 1 is simple: after the wager is accepted, log from the confirmed ticket. Do not rely on the pre-click screen or a stale odds board. This keeps the entry side of the CLV comparison anchored to something that really happened.
Match the closing reference to the market you bet
A closing line is only a useful comparator when it describes the same market. A full-game spread should be compared with the full-game closing spread. A first-half total should be compared with the first-half closing total. A player prop needs the closing version of that player prop, not a team market that happened to move in the same direction.
This sounds mechanical, and that is the point. CLV becomes trustworthy when the matching rule is boring and repeatable. If you change the reference market after seeing how the game went, you are no longer measuring the process you used at bet time.
Decide your closing-source rule before the season
Another source of drift is changing which closing market counts as the reference. You may have access to several books, an exchange, or a consensus feed. Pick a rule that you can apply consistently and write it down.
The rule might be a designated reference book, a defined consensus, or another market source that your workflow can capture reliably. The key is consistency. If you use whichever close makes each individual bet look best, the CLV record becomes selection-biased and loses its value as a process metric.
Why starting in Week 1 matters
Starting from the opening week gives you a complete season-long record of your own decisions. Starting later creates a hole that is difficult to repair because historical market screens do not always preserve the exact price you received, and your own memory is unlikely to preserve every accepted term.
The benefit is not that Week 1 is magically more predictive. The benefit is continuity. When every wager follows the same logging rule from the beginning, you can review the process later without wondering whether the early part of the season used a different standard.
That continuity also makes it easier to diagnose changes. If your entry process, model, or preferred market evolves, the log shows when the change happened. A mid-season spreadsheet assembled from memory often cannot separate a genuine process change from missing information.
Add context without turning context into the official entry
Notes are useful. You may want to record an injury report, a weather concern, a model version, or the reason you acted when you did. Keep those notes, but keep them separate from the official market fields.
The CLV calculation should not depend on prose interpretation. The market, selection, entry line, entry price, venue, and timestamp should be structured enough that another person could identify the same wager. Notes explain your reasoning; they should not be required to decode the bet.
Record pushes, voids, and market changes honestly
Not every accepted wager reaches a normal settlement. A player may not participate. A market may be voided. Rules can differ by venue. These cases should remain in the log with their actual status rather than disappearing because they are inconvenient for performance reporting.
CLV is about the quality of the entry process, so preserving the history matters even when the bet is later void. If the market itself changes definition or the comparable closing market does not exist, mark the CLV comparison as unavailable instead of inventing a replacement.
Keep CLV separate from game result
A bet can beat the closing market and still lose. A bet can get a worse price than the close and still win. That separation is the reason CLV is useful. It lets you evaluate price-taking discipline without letting one final score rewrite the story of the entry.
Your log should therefore have separate fields for market comparison and settlement. Do not overwrite the entry record after the game. Preserve what you knew and what you accepted at bet time, then append the closing reference and final settlement later.
Use Builder as the home for a repeatable tracking workflow
The existing Builder workflow provides a natural place to keep model context and backtest logic together. The already-published CLV guidance in Shark Snip describes a tracking-column approach for preserving entry information and comparing it with the close. The important part is not the presentation. It is that every row follows the same rule.
If your model generates candidates in Builder, attach the model identity or version to the bet log. That lets you later distinguish whether CLV came from one model family, one market type, or one decision rule without rewriting history after results arrive.
A practical season-kickoff checklist
Before the first live wager, verify that your logging workflow can answer each of these questions:
- Can I identify the exact event and market?
- Can I identify the exact selection?
- Can I recover the accepted line or threshold?
- Can I recover the accepted price?
- Can I prove where and when the wager was accepted?
- Do I know which closing source will be used?
- Can I match the close to the same market definition?
- Can I keep the closing comparison separate from the final result?
If the answer to any of those is no, fix the logging process before adding volume. CLV cannot be made reliable later by adding more bets to an incomplete record.
Review the log for missingness, not just performance
A good weekly review starts with data quality. Look for missing prices, missing timestamps, unmatched closing markets, and bets whose market definition is unclear. Those are process defects. Fix them while the events are still recent enough to verify.
Only after the record is complete should you summarize the direction of your CLV. This ordering matters because a flattering average built from only the easiest-to-match bets is less useful than a complete record that includes unfavorable entries too.
What not to reconstruct later
Avoid backfilling an entry line from a historical odds chart unless you can establish that it is the exact price you received. Avoid using the closing line as a stand-in for a missing entry. Avoid inferring a timestamp from when you remember watching the game. Missing data is an honest state. Fabricated precision is not.
If a field is missing, mark it missing and improve the process for the next wager. A clean null tells you where the logging system failed. An invented value hides the failure and contaminates the metric you were trying to protect.
Make the log portable before you need to audit it
A useful CLV record should survive a change in tool. If you can only understand a wager while one sportsbook app, one browser tab, or one custom dashboard is available, the record is too fragile. Keep the core fields in a form that can be exported or reviewed independently of the interface that captured them.
That portability also protects the distinction between source evidence and analysis. The accepted ticket or captured market record is evidence. Your later CLV calculation is analysis derived from that evidence. Preserving both makes it possible to correct a calculation without rewriting the original bet, and it makes disagreements about the closing reference easier to resolve.
Bottom line
The season-kickoff CLV habit is simple: preserve the bet as executed, define the closing reference in advance, and never let the final score rewrite either side of the comparison. Starting in Week 1 gives you continuity; logging every field gives you auditability.
Use the CLV concept page for the underlying idea, then keep the operational record alongside your model work in Builder. The goal is not to make the log look sophisticated. The goal is to make every later CLV comparison reproducible.
Model calibration: predicted vs observed
Predicted win probability bucket vs the empirical win rate inside that bucket on the test set. Points on the y=x reference line are perfectly calibrated; points below mean the model is overconfident in that bucket.
EV per $100 across win rate × odds grid
Expected value of a $100 stake at each combination of true win rate and market odds. Anywhere the cell is positive you have a long-run profitable bet; the magnitude shows how aggressive Kelly will size it.
