Handicapping Workflow: A Five-Pass Research Process

Where does your analysis begin, with the stats or with the question? A handicapping workflow starts with the question: which market, which rules, and at what moment are you estimating a fair probability? The lesson sets an information cutoff so Saturday news never leaks into a Friday forecast, then moves through five passes: data integrity, baseline ability, matchup evidence, pricing, and decision with audit. It stresses that "Team A is better" is not a bet until it has a price and a probability attached. You also practice turning a margin into a chance and comparing it with an executable quote. If your research feels like a pile of interesting facts, this gives it a spine.

Learning objectives

By the end, members should be able to implement and explain the method, reproduce the worked example, identify failure modes, and distinguish a supported research conclusion from an unsupported betting claim.

Overview

A handicap is a forecast supported by evidence, not a collection of interesting statistics. The professional workflow starts with an explicit target: Which market, which rule set, and at what time are we estimating a fair probability? A spread, moneyline, total, and player prop each require a different probability output. A claim such as “Team A is better” does not specify a price, outcome, or testable probability. Define all three before looking for supporting evidence.

Begin with an information cutoff. Record the precise timestamp when the analysis starts, the event identifier, the market, the available quote, and the data that would have been knowable at that time. Keep a separate log of later news. This prevents hindsight contamination: adding a starting-quarterback absence learned on Saturday to a Friday forecast is not an honest Friday backtest. Maintain a baseline forecast from a pre-registered method, then log justified adjustments one by one.

Organize research into five passes. Pass one is data integrity: confirm opponents, venue, home designation, game format, rest, injuries, and market settlement. Pass two is baseline ability: strength ratings and expected pace. Pass three is matchup-specific evidence: lineups, positional interaction, stylistic strengths, and game environment. Pass four is pricing: transform your forecast into a market-specific probability and compare with the executable quote after removing commission or vig as appropriate. Pass five is decision and audit: save the final estimate, sensitivity range, reason codes, and whether the opportunity cleared a pre-specified decision threshold. No qualifying opportunity is a valid outcome.

Use a versioned research sheet with columns for source timestamp, estimate, adjustment size, assumption, analyst confidence, and post-event audit notes. An injury adjustment supported by historical replacement performance is distinguishable from an anecdotal “team always struggles in cold games.” Assign the latter a lower evidentiary grade or leave it out. Keep correlated changes together: a missing quarterback can affect passing efficiency, turnover risk, total points, and receiver usage; treating each downstream effect as an independent penalty will double count it.

Worked example

Suppose a fictional model projects Home 26.0 points and Away 23.0: Home by 3.0 and a total of 49.0. Verified lineup information changes the Home offense by −1.5 expected points and the Away offense by +0.5, giving Home 24.5, Away 23.5, Home by 1.0, and total 48.0. Compare that forecast with the market only after choosing an outcome distribution. A projected one-point margin alone does not identify the probability that Home covers −2.5; estimate the distribution of scoring margins, including football's discrete final-score effects. If simulation estimates Home covers −2.5 in 46% of realistic scenarios, −110 requires 52.38% to break even, so the fictional price is unattractive. This is a methodological example, not an actual live game or line.

Quality controls

Before publication, a second reviewer should independently recreate the arithmetic, confirm each source existed at the recorded cutoff, inspect the adjustment ledger for double counting, and verify that the final decision used an obtainable price. Teaching content should show both rejected and accepted fictional ideas; otherwise members learn selection bias instead of process.

Exercises and answer key

Exercise 1. Baseline Home 28, Away 21. Revised Home −2, Away +1. What is the new projected margin and total? Answer: 26–22; margin Home +4, total 48. Exercise 2. An analyst learns of an injury after the event and retroactively changes the pregame prediction. What failed? Answer: timestamp integrity and information-cutoff discipline. Exercise 3. The projected margin changes materially but the analyst cannot explain why. What happens next? Answer: suspend the forecast, audit source and adjustment history, and do not invent an explanation.

Three-point recap

1. A handicap is a forecast tied to a market, a rule set and a time: fix an information cutoff, then log every adjustment one at a time against a pre-registered baseline.
2. A projected margin is not a cover probability; estimate the distribution of margins, including discrete scoring effects, before comparing with a price.
3. Have a second reviewer recreate the arithmetic and confirm each source existed at the cutoff, and suspend any forecast whose change you cannot explain.

Frequently asked questions

What is handicapping in sports betting?

A handicap is a forecast supported by evidence, tied to a specific market, rule set and time. "Team A is better" is not a handicap, because it names no price, outcome or testable probability. Define those three things before collecting supporting evidence.

What is an information cutoff in handicapping?

It is the recorded timestamp from which you analyze: the event, market, quote and data knowable at that moment. Later news goes in a separate log. This avoids hindsight contamination, like adding Saturday injury news to a Friday forecast and calling it an honest Friday test.

Does a projected point margin tell you the cover probability?

No. A one-point projected margin alone does not give the chance a team covers a spread. You need the distribution of scoring margins, including football's discrete final scores. In the lesson, a 46% cover estimate against the 52.38% needed at -110 makes the price unattractive.

How do you avoid double counting adjustments?

Keep correlated changes together. A missing quarterback can affect passing efficiency, turnovers, total points and receiver usage, so treating each effect as a separate penalty counts one shock several times. Log adjustments one at a time in a versioned sheet and have a second person check the ledger.

Related lessons

• Power Ratings vs Market Prices: Find the Gaps
• Adjusting Power Ratings for Injuries, Lineups, Weather
• Handicapping Decision Log: Build an Auditable Record
• CBB + March Madness — angle stacking, pace, line value

Sources and further reading

• About Sharp App: who builds these lessons and how the tools work.

Try it in the Odds screen. Examples in this lesson are fictional, built to show the method. Work the numbers by hand first, then repeat the same steps on a real board. You can also read how Odds & Markets works on the Sharp App site.

Questions? Ask ARBAI about this lesson · Ask our Sharps in Discord →

Sharp App surfaces +EV opportunities from public sportsbook data. 21+ where legal. Betting carries risk, so only stake what you can afford to lose. If betting stops being fun, call 1-800-GAMBLER or visit ncpgambling.org. More at Sharp App responsible gaming.