Jangoo's T20I Call-Up: Form From One Format, Arithmetic From Another

On the evening of the third ODI at New Chandigarh, the scoreboard carried the words 'record successful chase.' Dust rose under the floodlights, and in one corner of the dugout a wicketkeeper-batter was slowly pulling off his gloves. Nobody imagined then that his name would be attached to another squad list within days, a series where the ball would be bowled in twenty overs and the arithmetic would be entirely different. Amir Jangoo, a 29-year-old wicketkeeper-batter, made 58 not out, 114 and 67 in that ODI series, 239 runs across three innings. The number dazzles, and that is exactly where my referee's eye pauses. Those 239 runs were written in the language of ODI cricket, while the five-match T20I series ahead speaks an entirely different language. The frame before the frame is where the truth usually hides. The earlier frame here is ODI cricket, a fifty-over game of patience where the craft of building an innings and preserving wickets carries weight. The later frame is T20I cricket, a twenty-over game where patience is traded for explosion. Merge the two frames and the walk toward a wrong call has already begun. Let me set the context. West Indies have just finished a three-match ODI series on this India tour, and a five-match T20I series waits across Lucknow, Ranchi, Indore, Hyderabad and Bengaluru. Five different venues, five different surfaces, and the question of evening dew in India. Across a series this long, a squad is tested in its depth, not only in its first eleven. Jangoo's call-up arrived with a clear reason attached: a finger injury to Jewel Andrew. The X-ray shows no fracture, but Andrew remains under observation. He has not yet been ruled out. Jangoo has therefore not walked in to claim a first-choice place; he has walked in to stay ready for a possible situation. This is where a quiet corner of the selection process surfaces. The word 'cover' works much like an on-field review for a referee: the decision is provisional, not final. If the incumbent is passed fit, the place itself may vanish. Jangoo's current status is a temporary presence, not a settled promotion. The format distinction matters. In ODI cricket, success is measured by average and the ability to build an innings; fifty overs grant time, and keeping wickets in hand has value. In T20I cricket, success is measured by strike rate, runs per hundred balls. Modern T20I expectation for a top-order or middle-order batter generally sits in the 130-to-145 band, and above 150 for finishers. The expectation for a wicketkeeper-batter is no lower, because the keeper-batter is a scarce and expensive commodity in the modern game. Open that second page and the picture shifts. Look again at the three innings. In the first match he made 58 not out, surviving to the end of a chase. In the second he made 114, the largest individual innings of the series. In the third he made 67, in the match that produced the 'record successful chase.' His 239 runs placed him third among run-scorers from both sides, behind only Shubman Gill and Shai Hope. I replayed those innings frame by frame eleven times before I trusted my own eyes. Honestly, the runs are real. The consistency is real too: not a single flash, but three separate contributions. The question is not the truth of the runs; the question is the nature of the soil. A 'record successful chase' at New Chandigarh tells us the pitch was batting-friendly, the ball came onto the bat, scoring was easy. On such a pitch 239 runs can arrive, but their readability drops; the same runs on a seaming track would weigh far more. Consistency is not in doubt. But consistency in which format is the question. Three contributions in three innings means the player's rhythm is good, valuable information for a selector. Yet the rhythm belongs to one format while the demand belongs to another. The patience that builds an ODI innings is not the courage that takes risk from the first ball in a T20I. The same batter can look like two different players in two roles, an old truth of cricket. Now the second page, almost absent from the headline. Jangoo's T20I record: seven matches, 163 runs, a strike rate of 120.74. That sits below modern expectation for a T20I top-order or keeper-batter. A strike rate in the 120s means a shade above six runs an over, not enough to match T20I tempo across twenty overs. An honest caution is necessary here, or I become guilty of the very error I hunt in others. Seven matches, 163 runs: the sample is small. In a small sample the error bars around a strike rate are wide, and one good series could lift the number quickly. So 120.74 is not a verdict; it is a caution flag. But ignoring a caution flag and shouting 'stunning form' is equally wrong. Age hides in the background too. He is 29, with an international debut in December 2026. Set those two facts together and the picture clarifies: Jangoo is not a young prospect but a mature domestic performer who knocked on the international door late. That weakens the 'development upside' story while raising short-term reliability, and that subtle difference is precisely what the 'stunning form' headline conceals. The largest fact hidden in the background is this: Jangoo has been called up primarily as a keeper. Andrew's finger injury means the team's glove depth is thin. Jangoo's primary duty is glovework; batting is his secondary argument. The headline tells the batting story because the batting story sells. My own working method applies directly here. In 2026, analysing the first VAR penalty at the Russia World Cup, I watched France against Australia: Griezmann's penalty, a review that ran 75 seconds. That day I learned that the rulebook mattered less than seeing a man's hands tremble. Here the opposite is needed. What is needed is not the trembling-hands headline but arithmetic that respects the format's own law. Same event, different game, different law: this is the central error of cross-format contamination. Another example from my own past. In 2026, when I started 'Referee's Eye' from Sylhet, I judged a 92nd-minute offside wrongly by 1.2 metres in an Abahani against Mohammedan match. Two hundred comments called me blind. After three weeks of watching every camera angle I understood that a wrong call had taught me how to be right. That lesson applies directly. The error is judging one game's events by another game's law. Proving T20I value with ODI runs is that same error. I carry another old habit: suspecting a single number. In football, xG is now widely abused; one figure is asked to explain match decisions, player form, even refereeing standards. Cricket has the same condition with strike rate. Strike rate matters, but strike rate alone cannot explain Jangoo's role: whether he bats top-order or as a finisher, the situation he enters, the balls he faces. Without those, 120.74 cannot be called conclusive proof. The number is a signal, not a verdict. Five venues: Lucknow, Ranchi, Indore, Hyderabad, Bengaluru. In India, evening matches bring dew; the ball turns damp and heavy, and spinners lose grip. For a keeper these five matches are a test of physical labour: staying low, taking catches with a wet ball, staying alert behind every delivery. Here keeping quality can directly change a result, yet the headline never mentions keeping. Toss and dew in Indian evenings change a match's course. The side batting second often gains an advantage because the ball skids on and spinners lose grip. For a keeper the condition doubles the difficulty: a wet ball to catch, low takes, the fear of the ball slipping at the moment of a stumping. Across a five-match series these small moments can settle results, and the scorecard carries no trace of them. One more thing must not be forgotten: the whole tour is away for West Indies, on Indian soil, before Indian crowds, on Indian pitches. Any assessment of individual performance has to fold in the away factor. The 'stunning form' headline does not carry that weight. From the team's side a structural signal emerges. One keeper's injury forces a mid-tour call-up, which means the keeper pipeline lacks extra depth. Leading sides usually keep two or three usable keepers on hand. West Indies' obligation is itself a squad-structure signal, and it is a pattern, not a one-day event. Andrew is 'under observation,' 'not ruled out.' Uncertainty lives inside those two phrases. If he recovers quickly, Jangoo may sit on the bench and never play. If the injury drags, Jangoo may suddenly become first-choice keeper. One man's whole series hangs on another man's finger. A familiar pattern of news framing is also at work. The headline lifts the favourable ODI data, 239 runs and stunning form, and buries the unfavourable T20I data, the 120.74 strike rate. This is no conspiracy; it is ordinary journalism holding a reader's attention. The analyst's job sits precisely here: to bring forward the fact the headline left out. I will also state plainly what would change my doubt. If Jangoo gets regular top-order chances across five matches and holds a strike rate above 130, my caution will be proved wrong, and I will say so. If he keeps regularly and bats slowly, the question becomes one of role rather than format. That is where analytical honesty lives: naming in advance the evidence that would move my own view. I want to raise a reverse question here, because I do not hunt for guilt; I hunt for the angle nobody chose. Everyone asks: his strike rate is so low, so why the T20I call-up? My view is that the real question should be reversed. Jangoo was called up not for batting but for keeping. So why are we spending so much time on his batting strike rate? The real blind spot, to my eye, is this: we have turned the right question the wrong way. Searching for a replacement for an injured keeper, we suddenly argue about a batter's form. It resembles mistaking a goalkeeper's long kicking for his value: the real job fades into the background while a flashy skill sets the price. A goalkeeper's worth is in his hands stopping the ball, not his feet; a keeper's worth is in his gloves, not his bat. Yet this reverse argument has a limit. If Andrew is passed fit and Jangoo never plays, the batting debate stays a headline and nothing more. If he does play, his strike rate becomes relevant, because even a keeper must score with the bat. Both possibilities remain open, and so patience is the only option before a final verdict. The whistle decides the match, the replay decides the whistle, and here the replay is still pending. In a market like Bangladesh this news travels fast, because the youth market here runs on emotion. A 29-year-old hard-working keeper earning a late call-up becomes a story of inspiration. That emotion has value; it keeps the audience and the game alive. But emotion and analysis are two separate layers, and a writer's job is to keep the two layers apart. Finally, one word at the centre of this news: 'form.' In cricket, form means the recent run of performance. But form is never format-neutral. A batter's ODI form and T20I form are pictures of two different skills: one allows time, the other does not. When the phrase 'stunning form' is used, the question matters: whose form, in which game. Looking forward, my eye is fixed on three places. Andrew's fitness will decide whether Jangoo sits on the bench or takes the field. Whether Jangoo's strike rate climbs toward 130 across five matches, or stays near 120, will say whether ODI rhythm converts in T20I cricket. And whether West Indies keep leaving this gap in keeper depth after the series. The current beneath the table is what headlines usually miss. I will close with one suggestion. If West Indies keep playing long series like this five-match assignment, the time has come to think about keeper depth in advance, so that one man's finger injury does not alter a whole team's arithmetic. And a request to the reader: next time someone explains a call-up with 'stunning form,' ask once, form in which format, arithmetic in which format.