Football Player Props: Data, Participation and Settlement

The minimum prop contract

Betfair's current football rules provide one operator example that names Official Opta data for listed player-stat products and supplies product definitions. Another operator can use a different source or threshold rule.

Event labels can hide provider choices

Opta's published football definitions show that event data is constructed from declared rules. A shot on target is not every attempt directed toward the goal in ordinary language; blocks, woodwork, own goals, and goalkeeper intervention require a provider definition.

Do not combine a price settled by one provider with historical counts from another without a reconciliation study. Save provider, competition coverage, event version, and correction timestamp.

Threshold settlement

The notation 2+ is inclusive, while Over 2.0 can be a whole line with a push depending on the product. Copy the exact visible notation rather than normalising labels by intuition.

Participation and minutes

Sportmonks' lineup documentation distinguishes confirmed and predicted lineups and includes lineup metadata. A model should store predicted status at its cutoff, confirmed status when available, actual appearance, entry and exit times, and position.

A non-participant can be void under one product and a losing all-in selection under another. A substitute who plays 12 minutes can remain live under an any-appearance rule but be void under a minimum-minutes rule. Use the accepted contract.

Worked return and expected value

For an illustrative GBP 10 stake at decimal odds 2.10:

Gross return = 10 * 2.10 = 21

Net profit = 21 - 10 = 11

If an illustrative model estimates a 0.49 chance that the prop wins and a 0.08 chance it voids, the loss probability is:

Loss probability = 1 - 0.49 - 0.08 = 0.43

For one unit:

EV = (0.49 * 1.10) + (0.08 * 0) - (0.43 * 1) = 0.109

OpenStax's expected-value method supports including the void state with zero net payoff. The probabilities are illustrative, not a player forecast.

Reconciliation checklist

1. Store operator market ID and provider player ID.
2. Copy event definition, threshold, and period.
3. Save predicted, confirmed, and actual participation states.
4. Preserve substitutions and minutes.
5. Reconcile event-level data with the final operator result.
6. Retain corrections, voids, rejected stakes, and accepted prices.

Next step

Use Player Performance Metrics for the next part of this topic.

Continue learning

• Next guide: Half-Time/Full-Time Betting
• Related guide: Over/Under Goals Betting

Assumptions and limitations

Examples are illustrative. DraftKings' soccer rules and Betfair are operator references, not universal settlement. This page does not recommend player props or claim that recent per-90 rates are stable forecasts.