Make both sides answer the same question
The comparison unit should be a probability for a defined outcome at a defined time. A human who selects only five fixtures cannot be compared directly with a model covering 200 unless non-selections and coverage are part of the result. Likewise, a human confidence label such as “strong” needs a probability mapping fixed before outcomes are known. Published human-machine football forecasting research demonstrates a same-task benchmark design rather than a comparison of unrelated pick lists.
Fair comparison contract
| Element | Requirement |
|---|---|
| Fixtures | Same eligible set and exclusion rules |
| Target | Same market, match period and settlement |
| Cutoff | Forecasts locked at the same information time |
| Output | Full probability vector or declared probability |
| Baselines | League frequency and relevant timestamped market |
| Metrics | Proper probability score, calibration and coverage |
| Record | Immutable timestamped forecast before kickoff |
Published AAAI research reports a particular benchmark combining machine-learning and human football forecasts. Its findings belong to that dataset and design; the paper does not establish that machines or people always dominate.
Metrics answer different questions
Accuracy measures whether the selected class was correct under one decision rule. Log loss and Brier score use the probability assigned to outcomes. Calibration asks whether cases assigned similar probabilities occur at similar rates. scikit-learn's evaluation guide documents classification and probability metrics, and its calibration guide explains reliability analysis.
Illustrative comparison
Suppose both forecasters cover 500 later fixtures. The model has log loss 0.990 and the human forecast 1.004; the difference is 0.014 on that sample. If the human is better in one league and the model is miscalibrated above 0.70, those findings belong in the conclusion. The lower overall score is not proof of universal superiority. The numbers are illustrative.
Test combinations separately
A combined forecast should be treated as a new model. Set the weighting rule on training or validation data, then test it on later fixtures. Do not average forecasts after inspecting which forecaster was right. Chronological evaluation, such as the ordered structure documented by TimeSeriesSplit, prevents future results from choosing the combination.
Human and machine failure modes
| Human process | Machine process |
|---|---|
| Selective memory or unpublished picks | Leakage from final or corrected data |
| Confidence labels changed after results | Pipeline or model version changed silently |
| Uneven fixture selection | Coverage failures omitted from metrics |
| Narrative inconsistency | Drift after provider or league changes |
Neither list implies that every person or model has that failure. It defines what the audit should look for.
Convert human confidence before the test
Ask human forecasters for probabilities or map confidence labels to fixed probabilities using a development period. The mapping must be locked before the comparison period. If a forecaster can abstain, give the machine the same option or report coverage as a separate dimension.
| Output issue | Fair treatment |
|---|---|
| Probabilities do not sum to one | Reject or normalize under a declared rule |
| Forecast arrives late | Exclude under the shared cutoff rule |
| Fixture skipped | Keep in coverage denominator |
| Forecast edited | Preserve versions and use the last eligible one |
| Explanation changes | Score the locked probability, not the narrative |
Published human-machine football research supplies one documented benchmark context. A new comparison still needs its own protocol and sample.
Compare decision usefulness separately
After probability scoring, a blinded reader study can assess whether explanations help users detect missing evidence or limitations. That is a different outcome from match prediction. A persuasive explanation should not improve the recorded forecast score, and a sharp forecast may have no useful explanation.
Publish disagreements, not only the winner. Cases where the person and model diverge can reveal missing data, overconfidence or a genuinely informative human observation for a future locked experiment. Published human-machine football research supports treating combination and disagreement as testable within a declared benchmark rather than a universal conclusion.
Continue the workflow
The prediction-service evaluation guide extends the same-fixture comparison into attribution, timestamp, price and settlement checks.
Continue learning
- Next guide: XGBoost vs Random Forest for Football Prediction
- Related guide: AI Premier League Prediction Accuracy
Assumptions and limitations
“AI” and “expert” are broad labels, not quality measures. A fair result is specific to the target, information set, period and participants. This page provides a comparison method and does not rank current tipsters or claim a profitable advantage.

