MDX vs YOR Match Intelligence And Turning Point Review

Completed

Back To Live Match

Public model signal

Yorkshire

Chasing side is still within the model's scoring range.

68%

Score97/2

Overs20.0 overs

Expected finalExpected final 274

BattingYorkshire

BowlingMiddlesex

CRRCRR 4.85

RRRRRR 5.00

ResourcesResources 64.7%

Resource WPResource WP 57%

Par paceScore vs par pace -30.9

PressurePressure 6.50

How these metrics are calculated

CRR: current runs divided by completed overs. RRR: runs still required divided by overs remaining.
Expected final: resource-calculator estimate for the completed innings. Projected score: current-rate extrapolation.
Venue average: full-innings venue scoring baseline. Score vs par: current score minus resource-adjusted par.
Resources: model-calculated resources remaining. Resource WP: the structural win probability from that resource state.
Model probability: calibrated public win probability from the selected gender-aware T20 or ODI model.

Sources: the public-safe prediction payload and the match snapshot. Raw training features are not exposed.

Win Probability

Current model probability

Yorkshire 68%MDX 32%

The probability line shows how the model view changed during the match, keeping the first-innings batting side as the same reference across both innings.

19.4Innings 220.0

Model probability by update 50% balance

Open prediction update log (3 updates)

Inn 2 · 19.496/265%Expected 275

Inn 2 · 19.596/260%Expected 273

Inn 2 · 20.097/268%Expected 274

Expected finish

Expected final versus venue

Expected final comes from the model resource calculator; venue average is the full-innings venue scoring baseline.

Expected finalExpected final 274

Venue averageVenue average 160.0

Resource and pace

What the innings has left

Par pace compares current score with resource-adjusted par. CRR is runs per over; RRR is the required chase rate.

Resources remainingResources 64.7%

CRR / RRRCRR 4.85 · RRR 5.00

Pressure

Why the state feels difficult

The model sees measurable pressure against the current resource position.

Momentum

How the match is moving

Recent updates have moved toward the batting side. The timeline shows the direction rather than a certainty.

Confidence

How strongly to read the signal

The direction is available, but confidence is reduced because this model update is older than the freshness window.

Model factors

Why the signal leans this way

Expected final 274, 114 above the venue average.
Current score is 30.9 runs below resource-adjusted par.
Chase pressure is 5 required runs per over from here.

These are public-safe factors from the current match state; raw training features remain private.

Match briefing

Context beyond the score

Venue behaviourTracking above the venue baseline.

Toss impactToss impact will appear when toss context is available.

Expected score274

Turning point20.0 · 97/2 · +8%

Latest swing60% to 68%

This public briefing reuses the explanation-pack pattern from the intelligence/video workflow. Player picks, market replay, and operator-only fields stay excluded.

Win probability

Yorkshire

68%

Chasing side is still within the model's scoring range.

What changed

Latest visible shift

start became the clearest public signal for where control moved in the final result.

Why it changed

Current explanation

Expected final 274, 114 above the venue average.

What matters next

Next watchpoint

Use the scorecard and commentary archive to verify where the match flipped, then move to the next eligible match intelligence page instead of stopping at the result.

Keep the signal

Get the next match update

Follow the match from score context to model change without losing the live match page.