President's Trophy Grade-I: MIT Solutions' win is explained less by 412 and more by PTV's 394

One match, one team, two scores: 64 and 394. In round seven of the President's Trophy Grade-I, Pakistan Television (PTV) were bundled out for 64 in their first innings and then, following on, batted 110 overs to make 394. At the Diamond Cricket Ground on Wednesday, MIT (Markhor IT) Solutions had posted 412 in 88.4 overs for a 348-run lead, and eventually knocked off a 47-run target.

The scorecard's straight sentence is this: MIT won. What the scorecard does not say comes in two parts. First, the real story of this win is not the 412 but the 394 that PTV made after the result was already decided. Second, the report's own headline is tangled with itself — it says six-wicket victory in one place and four-wicket victory in another. The first lesson I learned on a sofa in Hyderabad at 2:30 a.m. was this: when a scorecard disagrees with its own arithmetic, check the arithmetic first and the story later.

Set the context properly, because this match cannot be read through a T20 or ODI lens. The President's Trophy Grade-I is Pakistan's domestic first-class competition, played by departmental and company-backed sides — MIT Solutions and PTV are products of that structure, not franchises. It is a two-innings, multi-day, attritional format. In that cricket the decisive force is not only runs but overs: whose fast bowler can carry the load, whose spinner can still get purchase in the second innings.

This match had exactly one strategic lever: the follow-on. A 348-run lead sits far above the traditional 200-run first-class threshold, so sending PTV back in was the textbook call. But textbook calls carry a bill — a tiring pace attack, a flattening pitch, and a batting side with nothing left to lose. PTV batted 110 overs and made 394. The second half of this match belonged to PTV, not MIT. The margin looks large on the board; on the ground it was not.

Now the first innings that actually won it. Mohammad Farooq made 130 off 101 balls — 15 fours, 7 sixes, a strike rate of roughly 128.7. That is the single most anomalous number in the entire report. A first-class centurion normally strikes at 45 to 60; 128.7 means Farooq did not bat like a red-ball player but like a T20 one. Only three honest conclusions follow — either the pitch was extremely flat, or the boundary dimensions were small, or his approach is short-format-trained and he applies the same intent to the red ball. Calling any of that a 'next big thing' headline would be premature.

Add Tariq's 98, Nadeem's 49 and Atiq's 39. MIT's first-innings strength was not Farooq's hundred but the collective top order — 412 at 4.65 an over in 88.4 overs, with four batters passing 39. That is what separated them from PTV, whose second-highest first-innings score was 17. One team had four contributors, the other had one. In first-class cricket that difference becomes a 348-run lead.

With the ball, Salman Aslam's 6/18 in nine overs is the shiniest figure in the report and also the most misleading. An economy of 2.0 and a strike rate of nine balls per wicket is excellent at any level. But 6/18 is only half the truth until you note that the opposition were collapsing to 64 and their next-best score was 17 — a large share of that haul belongs to collective batting failure, not individual mastery. The more informative detail is the three wickets in the second innings. Taking wickets across two different conditions inside one match suggests repeatability rather than a one-off spike.

That first-innings new-ball spell deserves separate attention. PTV's bowlers did not return empty-handed — Kashif Ali took three, Khalil Ahmed three and Ali Usman two, which tells you MIT were losing wickets even inside their 412. The reading is clear: the ball was moving on the first morning, both seam attacks got help, and the difference was simply that MIT's batters scored through that help while PTV's did not.

The second innings tells its own pitch story through numbers. Waqar Hussain made 171 off 245 balls (strike rate about 69.8) and Mohammad Taimur Khan 151 off 244 (about 61.9). The gap between Farooq's 128.7 and those two at 62–70 is not a gap in talent but a gap in pitch phase and team mandate. MIT needed fast runs in the first innings; PTV needed to bat time in the second. Placing those three innings side by side to rank the batters would be dishonest.

Khalid Usman's 4/90 from 33 overs is the figure that unsettles me most. Thirty-three overs in an innings looks routine in first-class cricket, yet it says one of two things — either he is MIT's long-term spin option, or the side had no other trustworthy choice. Either way it is a workload question, and over the coming rounds that over count will decide his availability.

And then that 47-run chase, where MIT lost four wickets inside ten overs. Farooq made 25 off 20 there, the same aggressive intent. A 47-run target and four wickets down tells you the pitch still did something in the final hour, and that small detail breaks the 'comfortable win' frame around this match. A side that wobbles chasing 47 after leading by 348 invites fair questions about its second-innings bowling.

This is where I should doubt myself. First doubt: was enforcing the follow-on itself the error? Many coaches bat again in that position, resting the seamers and letting the pitch flatten further. MIT did the opposite and spent 110 overs in the field. If their fast bowlers look heavy in the next round, that decision will come back to ask questions.

Second doubt: are PTV's 394 evidence of real strength, or 'scoreboard-pressure-free' runs? First-class cricket has a documented pattern here — batters play freely once the match is gone because the burden of the result is lifted. I read that 394 as psychological relief, not a quality upgrade.

Third and most important doubt: perhaps Farooq's 128.7 describes a flat pitch rather than a special batter. If so, the same player will make 40 off 100 when the ball moves, and we will all file him away as a T20 player. One match's data cannot say more than that. The most useful thing I learned from that 158-impression video was this — the thing that can be measured is often not the thing we want to measure.

One thing in this report is plainly broken: the winning margin. The headline and closing paragraph say four wickets, while the body says six and describes a chase in which four wickets fell inside ten overs — meaning six were in hand. The arithmetic leans toward a six-wicket win. This is not a harmless typo; it is a question of scorecard-verification habit — and when the counting itself is unreliable in domestic reporting, using that same report to settle a player's future becomes dangerous.

What to watch next is clear. For Farooq the question is not how fast he scores but whether he can bat 100-plus balls when the ball is moving. For Aslam it is where his pace sits next week after nine-plus overs in one match. And Khalid Usman's 33 overs reveal that MIT's bowling plan rests heavily on one shoulder. Until the official PCB scorecard confirms this report, keep those three names on a 'to be watched' list rather than a 'next big find' list. Seeing a side that made 394 get bowled out for 64 next time would surprise nobody — and that is the most honest truth of this format.