Build a source card for Shai Hope's unbeaten 162 in the 352 chase

A record chase should be captured as a completed match, not a future probability

The ICC reported on 4 October 2026 that West Indies chased 352 in the final ODI against India in New Chandigarh, led by captain Shai Hope's unbeaten 162. The report also notes India's 2-1 series win and a five-match T20I series due to begin on 6 October. This is a verification and record-keeping method, not a prediction, payment instruction, legal opinion or promise of an account outcome.

The ICC article is official competition reporting for the named match and includes comments attributed to coach Daren Sammy and Hope. A full scorecard is the stronger source for ball-by-ball detail. Readers need result, innings and series facts separated from quotes and any claim about the next format.

Create the match identity first

Test the statement at the level it was published. The report concerns the final ODI of an India–West Indies series in New Chandigarh and was published on 4 October 2026. Venue, format and series position prevent the result from being mixed with the coming T20Is. A different system, period or jurisdiction requires a different evidence row.

Before advancing, record the event identity and completed status before individual figures. The retained evidence is teams, format, match number, venue, match date, publication date and status. Do not attach T20I conditions to the ODI.

Record target and chase outcome

Test the statement at the level it was published. India posted 351 and West Indies completed a chase of 352 according to the report. The target and successful result are historical facts, not a repeatable performance promise. A different system, period or jurisdiction requires a different evidence row.

Before advancing, link innings totals and outcome to the same match ID. The retained evidence is first-innings score, target, chase score, wickets, overs if sourced and result. Do not fill unsourced over details from memory.

Attach Hope's innings to its context

Test the statement at the level it was published. Shai Hope scored an unbeaten 162 after keeping wicket through India's innings. The not-out status, role and chase context are part of the performance record. A different system, period or jurisdiction requires a different evidence row.

Before advancing, record only figures stated in the official report or scorecard. The retained evidence is player, team, role, runs, dismissal state, innings and source. Do not turn 162 into a projected next score.

Preserve series contributor figures

Test the statement at the level it was published. The article states that Hope scored 278 runs in the three ODIs, Amir Jangoo 239 and John Campbell 173. Series aggregates answer a different question from the final-match innings. A different system, period or jurisdiction requires a different evidence row.

Before advancing, keep match and series tables separate with their own periods. The retained evidence is player, series, matches or innings if stated, aggregate runs and source wording. Do not invent averages or strike rates.

Label coach and player comments as quotes

Test the statement at the level it was published. Sammy praised Hope and discussed partnerships, while Hope referred to advice from MS Dhoni about pacing a chase. Attributed reflections are not statistical proof or guaranteed strategy. A different system, period or jurisdiction requires a different evidence row.

Before advancing, paraphrase the themes and keep attribution and publication date. The retained evidence is speaker, role, topic, context, source and paraphrase. Do not present opinion as a model prediction.

Separate the next series from the result

Test the statement at the level it was published. The report says the teams next meet in a five-match T20I series beginning 6 October in Lucknow. A change of format, venue and squads creates new uncertainty. A different system, period or jurisdiction requires a different evidence row.

Before advancing, record the schedule statement while leaving outcome fields empty. The retained evidence is next format, first date, venue, official schedule check and unknown outcome. Never use the ODI chase to chase a T20I wager.

What the named source establishes and leaves unresolved

The ICC report supports the completed chase, Hope's unbeaten 162, the named series aggregates, attributed comments, the 2-1 series context and the stated next T20I date.

The news article may omit full scorecard fields and can be updated. It does not provide wagering probabilities, guarantee player selection or predict the T20I series.

Close the record with a bounded decision

The source card contains match ID, format, venue, innings and target, player figures, series aggregates, attributed comments, publication time, correction field and a separate next-series schedule row.

Betting is for adults 18+ only where lawful. A dramatic chase is not a betting edge; set fixed time and disposable-money limits, never raise stakes after a result and use timeout or self-exclusion when needed.

Use the responsible-play centre, the editorial policy and the guide library for related safeguards.

Create the match identity first: Follow-up review

Archive the first observation before updating teams, format, match number, venue, match date, publication date and status. Record the event identity and completed status before individual figures. The explanatory note must account for this fact: The report concerns the final ODI of an India–West Indies series in New Chandigarh and was published on 4 October 2026. Do not attach T20I conditions to the ODI. The follow-up stores no password, one-time code, recovery code, seed phrase or private key and never treats an unresolved field as permission to continue.

Record target and chase outcome: Follow-up review

Archive the first observation before updating first-innings score, target, chase score, wickets, overs if sourced and result. Link innings totals and outcome to the same match ID. The explanatory note must account for this fact: India posted 351 and West Indies completed a chase of 352 according to the report. Do not fill unsourced over details from memory. The follow-up stores no password, one-time code, recovery code, seed phrase or private key and never treats an unresolved field as permission to continue.

Attach Hope's innings to its context: Follow-up review

Archive the first observation before updating player, team, role, runs, dismissal state, innings and source. Record only figures stated in the official report or scorecard. The explanatory note must account for this fact: Shai Hope scored an unbeaten 162 after keeping wicket through India's innings. Do not turn 162 into a projected next score. The follow-up stores no password, one-time code, recovery code, seed phrase or private key and never treats an unresolved field as permission to continue.