A fantasy app does not score cricket. It scores the record a reader has already verified elsewhere. The 22 June 2026 Taunton outing of Manav Suthar — 5/100 in 46.5 overs in Somerset’s second innings, a match haul of seven, and an 11-wicket, 28.09 two-match stint for Warwickshire — is the kind of verified data set an app reader will see flash past in a player card without ever being told what the figure is actually built from. The case study below is the desk’s reference read on how that record should be captured into the app’s player-card workflow: which numbers travel, which numbers get dropped, what dates belong to the file, and which surface caveats an app reader should attach to the entry before the next contest window opens.
The verified source for the stint is the Sportstar (The Hindu group) report of 22 June 2026, cross-confirmed against the Warwickshire CCC scorecard at Taunton and the BBC County Championship scorecard for the County debut against Yorkshire. Nothing in the case study below is a market call, a rumour, or a forecast; it is a translation of the verified record into the input discipline an app reader needs in order to keep a player card honest across a multi-match stint. Where the surface, the role, or the opposition changes the meaning of a figure, that caveat is attached to the number, not left for the reader to discover later.
What the player card needs first, before the numbers
An app reader who only transcribes the headline figure — 5/100 — will write a thin card. The card needs four context inputs before the bowling line is filled in. The first is the date the spell was bowled: 22 June 2026, the second day of the Warwickshire–Somerset fixture at Taunton, with the spell running into the third. The second is the surface profile: a flat early-summer English first-class track, dry, with little seam movement on day one, and the kind of slow turn that becomes readable in the second innings. The third is the role: Suthar bowled as the second spinner in a four-pronged attack, sharing the new ball with a pace pair and rotating with the senior off-spinner. The fourth is the opposition: Somerset’s batting order, with the South African Jordan Hermann at the top, Tom Kohler-Cadmore in the middle, the night-watchman Josh Shaw, and Beau Webster’s Australia A credentials in the lower order. None of the four inputs is optional. Each one changes the read of the figure that follows.
The discipline of attaching date, surface, role and opposition to the player card is what separates a paper trail from a note. A note is a single number. A paper trail is a number plus the four lines that make the number legible to a future reader. App users who treat the player card as a note are the readers who later cannot explain why a verified five-for did not transfer to a different surface. The four inputs are the first line of defence against that error.
The headline 5/100, written into the card as a primary line
The first bowling line on the card is 5/100 in 46.5 overs. The figure is the maiden first-class five-wicket haul, taken on a flat track, with an economy of just over two an over and a strike rate of 9.4 balls per wicket. None of those second-order numbers is a stand-out figure on its own. The card should record the headline exactly as the verified source records it, and add two context lines underneath: the match situation (Somerset’s second innings, 435 all out, with Suthar’s 5/100 the second-innings effort after a 2/50 in the first innings) and the dismissal pattern (three top-order wickets early, two lower-order wickets at the back end, with the top-order trio being Hermann caught slog-sweeping, Kohler-Cadmore stumped, and Shaw edging to slip).
The reason the dismissal pattern belongs on the card is that the five-for is not a single spell. It is a morning spell that broke the top order, a middle-overs phase where the partnership was rebuilt, and an evening spell that took the lower order. A card that records only the headline 5/100 cannot tell those three phases apart, and the reader who later needs to price a Suthar card against a different opposition will not know which of the three phases is the comparison data. Writing the dismissal pattern into the card is the difference between a one-line note and a multi-phase record.
The match haul line, written below the headline
The second bowling line on the card is the match haul: 7 wickets for the match, drawn from 2/50 in the Somerset first innings and 5/100 in the second. The match haul is the working number; the five-for is the milestone. A player card that carries the five-for without the match haul is a card that the app will treat as one-innings dominant, which is not what the verified record says. The card should carry both lines, with the first-innings figure on the same line as the second-innings figure, and a one-line note attached that says both first-innings victims were tailenders. That single sentence — both victims tailenders — is the difference between a workmanlike first-innings contribution and a misleading first-innings headline.
The match haul is also the number that survives a format change. A five-for is a first-class figure. A match haul of seven translates directly into the wickets-per-match language an app uses, and the reader who tracks the match haul across a stint will see the volume number move in a way the headline figure cannot show. The discipline of writing the match haul below the headline is the discipline of carrying the volume number, not just the milestone.
The stint summary line: 11 wickets at 28.09 across two games
The third line on the card is the stint summary: 11 wickets at 28.09 across the two County Championship matches contracted with Warwickshire. The stint summary sits in a different position from the match haul. The match haul is the volume of one game; the stint summary is the volume of the whole trip. The denominator of 28.09 is the average cost per wicket across the trip, and the reader who puts 28.09 on the card without a denominator line is making the same error as the reader who puts 5/100 on the card without a date. The line should read 11 wickets at 28.09 across two first-class matches, with the breakdown of the two matches attached: 4 wickets versus Yorkshire on the County debut (two in each innings), and 7 versus Somerset at Taunton (2/50 and 5/100). The breakdown is the part that lets the reader know whether the stint number is reliable, or whether it is sitting on a small sample.
The two-match stint is a small sample. That is not a criticism of the figure; it is a description of the figure. A card that prints 11 wickets at 28.09 as if it were a season average will mislead a reader who prices the bowler against a five-match season. The card should be honest about the sample size. Two matches is the verified length of the stint, and the card that says so is the card that an app reader can actually price against a larger sample later, when more data lands.
The 28 with the bat: a card line most app readers forget
The fourth line on the card is the batting contribution: 28 from number eight or nine, with three fours and two sixes, in Warwickshire’s first innings of 330. The batting line is the line most app readers forget, because the player card on most apps leads with the bowling and the batting sits one row below. The 28 with three fours and two sixes is a non-trivial lower-order contribution. A spinner who can hit a length bowler over the top and a spinner over the top is a spinner who can add 20–30 runs in a tail-wagging stand, and the reader who keeps that figure on the card will not be surprised by the next time the bowler turns a game with the bat. The reader who leaves the batting line off the card will be surprised, and will misread the next card update.
The card discipline is to record the batting contribution on the same line as the bowling, with a note about the batting position. Twenty-eight from the top of the order is a different data point from twenty-eight from number eight; the same number with different position context is a different record. The reader who writes both the number and the position into the card is the reader who holds the bowler correctly when the next card update lands.
What the card should not carry, and why
A clean player card is a card that knows what to leave off. Three pieces of data the verified record supplies should not be written onto the Suthar card. The first is the ten-wicket Test haul against Afghanistan. The Test debut is a credential, not a stint, and writing it onto the County card collapses two surfaces into one. The second is the 4/23 by Beau Webster in Somerset’s first innings, which is a Somerset bowling figure, not a Suthar card input. The third is the Warwickshire first-innings total of 330, which is a team total, not a player card input. Each of these numbers is verified, useful context, and on the wrong side of the player card line. The reader who copies all three onto the card will produce a record that is harder to read, not richer.
The discipline of knowing what to leave off is the discipline of knowing what the card is for. A player card on the app is a record of one player’s verified input across a stint. It is not a match report, it is not a fixture note, and it is not a comparison with another bowler. The reader who treats the card as a match report will over-write the bowler’s line; the reader who treats it as a comparison will under-write the bowler’s surface profile. The middle path is the cleanest card.
A card template the reader can copy verbatim
For app readers who want a starting structure, the desk’s standing player-card template for a verified red-ball stint is below. It is built to be edited, not admired; replace the brackets with the verified record, and the card will read correctly against the next match window.
Player card — Manav Suthar (verified, County Championship 2026)
Reference template · last verified 22 Jun 2026| Line | Field | Verified value |
|---|---|---|
| 1 | Stint dates | Two-match stint, June 2026 |
| 2 | Headline 5/100 | Somerset 2nd innings, 46.5 overs (maiden first-class fifer) |
| 3 | Match haul | 7 wickets — 2/50 + 5/100, both 1st-innings victims tailenders |
| 4 | Stint summary | 11 wickets at 28.09 across 2 matches (Yorkshire + Somerset) |
| 5 | Batting input | 28 (3×4, 2×6) in Warwickshire 1st innings of 330 |
| 6 | Match outcome | Draw at Taunton, 22 Jun 2026 |
| 7 | Surface caveat | Flat early-June track; slow turn readable in 2nd innings |
| 8 | Role caveat | Second spinner, four-pronged attack |
| 9 | Do not copy | 10-wkt Test haul vs Afghanistan; Webster 4/23; team total 330 |
How the app reader keeps the card honest across updates
A player card is not a one-time entry. Every verified match the bowler plays will rewrite part of the record, and the reader who built the original card should treat the next match as a revision event, not a replacement. The discipline is to add a new line under the existing lines, never to overwrite the older lines, so that the card carries a history of the verified record rather than a single snapshot. A Suthar card built on 23 June 2026 with a 5/100 line should still carry the 2/50 first-innings line, the 4-wicket Yorkshire line, and the 28 with the bat, even after a later match updates the stint summary. The card that drops the older lines every time a new line lands is a card that loses its own provenance.
There are three checkpoints the desk applies every time it revises a card. The first is the date check: is every line on the card dated, so a future reader can sort the lines by match? The second is the source check: is every line traceable to a verified scorecard, a verified match report, or a verified broadcast summary? The third is the role check: has the bowler’s role changed in a way that the older lines no longer represent? A card that fails one of the three checks is a card to revise before the next contest window. A card that fails two of the three is a card to retire and rebuild.
Questions app readers ask about the Suthar card
Is the 5/100 the most important number on the card?
No — it is the most visible number, and the most quoted number, but the most important number is the match haul of seven, because the match haul is what the app reader will compare against the next match. The 5/100 belongs on the card as a milestone; the seven belongs on the card as the working number.
Should the 10-wicket Test haul be on the County card?
No. The Test debut is a credential for the bowler, not a stint data point, and writing it onto the County card collapses two surfaces into one. The credential belongs in a separate “other” line, or in the bowler’s bio, but not on the County card itself.
What about the 4/23 by Beau Webster?
That is a Somerset bowling figure, not a Suthar card input. It belongs in a match report or a Somerset card, not on the Suthar card. The reader who copies it across will produce a record that mixes two different bowlers’ stints into one card.
Does the 28.09 average change the read of the five-for?
Marginally, in the direction the reader would expect: a bowler averaging under 30 across a multi-match stint has done more than the single five-for would suggest, and the reader who puts 5/100 on the card without the 28.09 average will under-rate the volume. The discipline is to write both numbers on the card and let the next match decide which is the more important figure.
What goes on the card when the next match lands?
Add a new verified line under the existing lines, dated and traceable. Do not overwrite the older lines; the card is a verified record, not a single snapshot, and dropping older lines is the fastest way to lose the bowler’s provenance.
For the verified original event and the surrounding match context, the desk points readers to the Sportstar report of 22 June 2026, which remains the primary source for every number on the card above. App readers who want a working player-card workflow can compare the structure against the desk’s standing App Guide, and the next match that the bowler plays will be the next revision event for the card.