Glcs vs SUR Match Intelligence And Turning Point Review

COMPLETEDCompleted

Back To Live Match

Public model signal

GLCS

Chasing side under pressure: required rate is above current scoring pace.

Score292/10

Overs49.0 overs

Expected finalExpected final 292

BattingGLCS

BowlingSurrey

CRRCRR 5.96

RRRRRR 20.00

ResourcesResources 1.0%

Resource WPResource WP 0%

Par paceScore vs par pace -19.0

PressurePressure 50.00

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

GLCS 0%SUR 100%

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.

47.1Innings 249.0

Model probability by update 50% balance

Open prediction update log (12 updates)

Inn 2 · 47.1278/90%Expected 285

Inn 2 · 47.2279/90%Expected 285

Inn 2 · 47.3280/90%Expected 286

Inn 2 · 47.4280/90%Expected 286

Inn 2 · 47.5281/90%Expected 286

Inn 2 · 48.0282/90%Expected 286

Inn 2 · 48.1283/90%Expected 287

Inn 2 · 48.2284/90%Expected 287

Inn 2 · 48.3285/90%Expected 288

Inn 2 · 48.4286/90%Expected 288

Inn 2 · 48.5292/90%Expected 294

Inn 2 · 49.0292/100%Expected 292

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 292

Venue averageVenue average 257.7

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 1.0%

CRR / RRRCRR 5.96 · RRR 20.00

Pressure

Why the state feels difficult

The required rate is elevated, so the current resource position is carrying meaningful chase pressure.

Momentum

How the match is moving

The recent probability path is relatively stable.

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 292, 34.3 above the venue average.
Current score is 19 runs below resource-adjusted par.
Chase pressure is 20 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 score292

Turning point48.2 · 284/9 · +0%

Latest swing0% to 0%

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

GLCS

Chasing side under pressure: required rate is above current scoring pace.

What changed

Latest visible shift

+0% became the clearest public signal for where control moved in the final result.

Why it changed

Current explanation

Expected final 292, 34.3 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.