Daily Workflow
The eight-step routine for running BetBot end to end — from confirming data health in the morning to reviewing the track record after games settle.
Start on Live Data Health. Confirm results are coming from ESPN and that no critical provider is missing. If odds are stale, refresh before trusting any edges.
Open the Card Dashboard to see the full slate, BetBot's official picks, and what it is watching or passing. This is the day's headline view.
Compare the lines across sportsbooks in Markets & Odds. The official card uses the best available price; verify it still holds before acting.
Use the Official Card Builder to see which candidates were selected and why others were dropped. The slip preview mirrors what an alert would contain.
Log the day's preview picks in Tracking so they can be graded later. Tracking is read-only here — it records, it never places a wager.
Once games finish, grade each pick against the ESPN final score. Wins and losses flow into the running record automatically.
Open Loss Review to read why each missed pick went wrong — a bad line, a late scratch, or variance. Patterns here feed model calibration.
Finish on Track Record to see the cumulative win rate, accuracy by confidence band, and the model's spread-error trend over time.
Troubleshooting
4If the freshness badge reads Stale, the cache is old. Re-run the odds refresh script and re-export the snapshot before relying on edges.
An empty card usually means nothing cleared the edge and confidence thresholds. That is expected on thin slates — discipline over volume.
Missing on Live Data Health means that data source returned nothing. Check the relevant API key on Settings Status; fallbacks may apply.
On Pipeline Status, a red step shows the failure and its log path. Critical steps block the card; non-critical ones degrade gracefully.