GUIDES · BETSLIP DOCTOR
How can I reconstruct the sequence of a saved ticket and its later result?
Read each time by its label. Placed and settled describe events in the ticket's record; first recorded and last observed describe the history record's own storage and observation. Imported and self-reported records have different sources, and some times can be missing.
For Bettors reconstructing the timeline of their own saved records · Updated
A ticket's timeline and its record's timeline are different
Start with the time the ticket was placed, if the record includes one. Then look for its settlement time or a separately supplied settlement date. Those fields describe the ticket's activity. First recorded and last observed describe when BSD's history record was stored or observed. They do not replace the placement and settlement times.
This distinction helps explain why a result can appear in history after the wager itself was placed or settled. The record may have been imported or updated later. Its storage or observation date does not prove when the wager happened.
Check whether the record came from an import or manual entry
An imported record can carry provider-supplied placement time, settlement time and settlement date. The first-recorded time comes from BSD's stored import; the observed time comes from the import's recorded check time. Provider data can omit placement time, settlement time or the settled result.
A manually entered record uses the placement and settlement values entered for it. Its first-recorded and observed times come from the saved manual record. Its placement and financial result were entered by the person who recorded them, rather than confirmed by a sportsbook. Read the record's source and limitations with its timestamps.
Build only the sequence the fields support
For each entry, write down the event time that exists, then the record time. If the placed time is missing, you cannot infer it from when BSD first stored the record. If a provider supplies a settlement date but no settlement time, keep it as a date; it does not establish an exact instant. A later observed time is not a substitute.
Compare the same record revision and source when dates appear to change. The import may be checked again, and a manually entered record may be updated. A new observation or edit changes the record's own chronology without moving the original placement event.
Use event time to order the result
Suppose a hypothetical imported ticket contains a placement time, a later settlement time, a first-recorded time after settlement and an observation time later still. The supported sequence is: ticket placed, ticket settled, record first stored, record observed. This is only an example of how to read distinct fields; not every record contains all four.
Illustrative example: a record arrives after settlement
Imagine an imported ticket is placed on Monday and the provider marks it settled on Tuesday. BSD first stores the import on Wednesday and observes it in a later check on Friday. Monday and Tuesday are ticket events; Wednesday and Friday describe the record. If the settlement time is absent, do not infer it from the settlement date or Friday's observation. This is hypothetical, with no customer record or wager details.
Related questions
Does first recorded mean the ticket was placed then?
No. It marks when the history record was first stored. Use the separate placed time when the record supplies one.
Can I get an exact settlement time from a settlement date?
No. A date without a time establishes a calendar date, not an exact instant. The history record may also explicitly say that settlement time is missing.