Write the requested event precisely
Replace conversational wording with contract fields:
| Field | Example of a precise question |
|---|---|
| Event | Which fixture or competition? |
| Period | Regulation time, first half, extra time, or season? |
| Result | Which exact outcome must occur? |
| Player | Which named participant and what appearance rule? |
| Statistic | Which event definition and data provider? |
| Threshold | Over, under, at least, exactly, or a band? |
| Settlement | What happens after a void, push, correction or abandonment? |
The accepted quote controls
An operator can reject the request, alter its wording, remove a leg or return a separately priced product. bet365's current related-contingency explanation shows why some related combinations are not accepted as ordinary multiples. DraftKings' market rules provide a separate operator example for same-game products.
Save a screenshot or receipt containing:
- Final selection wording.
- Accepted combined price.
- Stake and maximum return.
- Product name and timestamp.
- Market and sport rules linked at acceptance.
- Confirmation that the request was successfully placed.
Settlement example
Suppose an illustrative accepted quote requires Player A to score and the match to finish 2-1 at decimal odds 18.00. For GBP 5:
Gross return if the complete accepted event occurs = 5 * 18 = GBP 90
Net profit = 90 - 5 = GBP 85
If Player A does not participate, an own goal occurs, the score is 3-1, or the match is abandoned, the current product rule determines the outcome. Do not import a fallback from a different operator. Betfair's football rules illustrate product-specific football settlement.
Probability check
Custom combinations are often dependent. Estimate the joint event directly or use conditional probabilities; the accepted quote does not prove independence or value.
Verification checklist
- Compare requested and accepted wording character by character.
- Confirm player identity and participation after lineups.
- Reconcile events against the named data source.
- Preserve corrections and final settlement.
- Treat a rejected request as no bet, not as an implied probability statement.
Next step
Use Same Game Multi for the next part of this topic.
Compare the request with the accepted wording
DraftKings' current market rules show how product definitions, participation, pushes and voids are tied to specific market wording. Create a short diff rather than relying on memory, marking every participant, period, threshold, statistic and connector such as and, or, exactly, at least, or to win.
| Stage | Record |
|---|---|
| Requested | Original message or builder selections |
| Quoted | Exact returned market wording and price |
| Accepted | Confirmation, timestamp and stake |
| Settled | Final result, adjustments and rule used |
Reject the analysis record if the accepted version is truncated or ambiguous. A conversational screenshot without the complete market label, event and period may be insufficient to reconstruct the contract.
Before acceptance, test obvious edge states: a named player does not appear, a statistic is later corrected, the match is abandoned, one requested event is void, or two events are ruled related. The aim is not to predict every operator decision; it is to identify which rule must be found while the product is still inspectable.
Continue learning
- Next guide: Using Statistics for Accumulators
- Related guide: Weekend Acca Research
Assumptions and limitations
The product and price are illustrative. Request channels, eligible events, response times, quoted prices and rules vary by operator, jurisdiction and date.
GambleAware
GamCare
Gambling Therapy
GAMSTOP