President's Trophy Final: A 51-Run Margin, a 20-Run Morning, and the One Run Missing from the Scorecard

There is one run missing from the scorecard.

On the final morning at Bagh-e-Jinnah, Lahore, Markhor IT (MIT Solutions) beat State Bank of Pakistan by 51 runs to take the President's Trophy Grade-I title. The report says SBP were chasing 237 and were bowled out for 185. Subtract 185 from 237 and you get 52, not 51. The same slippage appears on day three: SBP closed at 165/7, described as 147 for 7 plus an unbeaten 17-run stand between Mubashir Khan and Mohammad Abbas. Add 147 and 17 and you get 164, not 165. Two different places, one run, the same direction.

Nobody corrected it, because nobody needed to. Fifty-one or fifty-two: the trophy stayed in Lahore either way.

I care. I write about the decision nobody officiated rather than the one everybody shouted about. The rulebook said one thing; the replay said another — I went looking for the third answer. This time the replay was not fourteen frames but five days, and the third answer was hiding in the twenty runs of the final morning.

Context: the world this match was played in

The President's Trophy Grade-I is Pakistan's departmental-corporate first-class tournament, and nothing here makes sense without it. In 2026 the PCB reorganised the domestic structure into six provincial sides and pushed the departments out. They returned a few seasons later, and the President's Trophy became their platform. State Bank of Pakistan belong to that older tradition where a bank job and a cricket contract sit on the same sheet of paper. It is the home of a Test bowler like Mohammad Abbas. Markhor IT are the newer kind of team — built on corporate sponsorship, limited lineage, unfamiliar names. The final was therefore also a collision of two systems: one where careers are built out of stability, one where performance is the only contract.

The ground carries its own history. Bagh-e-Jinnah has hosted exactly one Test match, against India in January 2026. The first-class cricket played there has a recognisable temperament: a slow surface, low bounce, and by the fourth and fifth day an indifference that frustrates fast bowlers long before the second new ball. A five-day final, no reserve day. The result had to be settled somewhere between the last hour of day four and the first session of day five.

I have stood in KSCA league matches on the B ground at M. Chinnaswamy Stadium for years. I have watched the moment on a fourth-day evening when a captain decides whether he is winning or surviving — and that decision is usually taken in the dressing room, not in the middle. The biggest mistake in this final was not made in the middle.

Core: the actual arithmetic of the match

A 59-run first-innings lead, and a 110-run swing. The report does not carry SBP's first-innings total. That is a large hole, but arithmetic does not leave holes. MIT batted first, made 296 in their second innings, and set SBP 237. Subtract 237 from 296 and MIT were 59 runs behind on the first innings. Which means SBP led by 59 and lost the final by 51. From the first-innings position to the result, the swing is 110 runs.

That is the real architecture of this final, and it is the architecture that will not survive into the next day's headlines. A 51-run margin reads like a comfortable win. It was not. The side that led by 59 on the first innings conceded 296 in the second and then failed to chase 237. That is a description of a defeat, not of a victory.

The window between overs forty and forty-one. The report says that after Kamran Ghulam's dismissal for 16, SBP lost five wickets quickly and slid to 147 for 7. Work the given numbers. Hasan Raza and Abdullah Fazal opened with 49; Fazal went in the 20th over for 25 off 68. Hasan then shared partnerships with Faham-ul-Haq (13) and Kamran Ghulam (16). Add those three stands and you reach roughly 90. The five wickets that fell on the way to 147 therefore spread across a window of about 55 to 65 runs — inside a session, inside one spell, against one sustained mode of bowling.

Aamer Jamal took Ghulam in the 41st over. That wicket will be filed as the start of the collapse, which is true and incomplete. The better question is what MIT's captain was doing at that moment that SBP's was not. The answer sits in Khalid Usman's figures.

The second new ball never arrived. In first-class cricket the second new ball becomes available after 80 overs. SBP were bowled out for 185; the seventh wicket fell in the 41st over, and the innings never reached eighty. Which means those five wickets fell to the old ball, not to new-ball bounce. That is the technical centre of this innings and the point nobody will publish.

People will say the fifth-day surface did the work. It did not. The surface did nothing at all, and that is the most important thing about it. When a pitch does nothing on day five, a collapse is a batting decision rather than a pitch event. An old ball, low bounce, and a batting order that had already accepted it needed time rather than runs — those three things make wickets.

Khalid Usman's 16.5 overs, which means he bowled the last ball. Sixteen point five overs is 101 deliveries, and the .5 means the final ball of the innings was his. Kashif Bhatti, two, was the wicket, and the match ended there. The figures are 4 for 38: 38 runs in 101 balls, an economy of 2.25 and roughly 25 balls per wicket.

There are two ways to read that. The first, which everybody will write: the spinner won the match. The second, which matters: a left-arm spinner was given a continuous seventeen-over spell while the fast bowlers rotated at the other end. That is a captaincy decision, not a bowling one. It means MIT held one end with spin and attacked with seam at the other. The five SBP wickets fell inside that structure.

Read the numbers closely: four to Khalid Usman, two to Mohammad Ismaeel, one each to Aamer Jamal and Salman Aslam. That is eight. Ten wickets fell. Two wickets are unaccounted for in this report — either run-outs, or a bowler whose name is recorded nowhere. I mark this as a limit of the available material: I do not have the full scorecard page, so I cannot tell you who took those two wickets. What I can tell you is that two anonymous wickets in the record of a final is itself a comment.

Twenty runs on the final morning. SBP resumed at 165 for 7. The target was 237. Seventy-two runs needed, three wickets in hand, a full session available. They added twenty and lost all three.

Now the part that stays with me. Mohammad Abbas: thirty balls, six runs, one boundary. A Test bowler batting at nine who faced thirty deliveries and took no risk at all. Mubashir Khan: fifty-six balls, thirty-two runs, three fours. From the first ball of the morning until Abbas was out, the intent was not to score. It was to consume.

That was not wrong. It was rational. The only question is rational for what. If a drawn final shares the trophy, their approach was exactly right; blocking out seventy overs beats chasing 72. If the first-innings lead decides it, they already held that lead and had nothing to lose by batting on. In both cases SBP's approach was defensible.

So whose defeat was it?

Laws & Officiating

This is where the letter of the law is easy and the spirit of the law is where careers get decided. The playing conditions for a five-day final ought to state plainly what happens on a draw — shared trophy, first-innings lead, toss. I cannot confirm from the available material what this competition's conditions actually say, and I will not write it as though I can. But I will say this much: if a side batting in the fourth innings does not know precisely what a draw gives it, that is a failure of the conditions of contest, not of the batting.

The second thing nobody noticed: the match was effectively over in the middle of day four. Over rates, slow play, shortage of time — none of it shaped the result. When a match finishes early, everyone assumes the machinery worked. That is a bad inference. Time did not steal the result; that does not mean nothing else did.

The third thing is contractual. After this final, the next six months of twenty players get decided — central contracts, departmental promotions, NOCs for overseas leagues. Those decisions will be taken in a room where nobody watched the match, only the scorecard. And that scorecard has a run missing, two nameless wickets, and no first-innings total for SBP.

There is a threshold, and most arguments are really about where it sits. Here the threshold is this: is a domestic final's scorecard an auditable document, or an advertisement? I did not re-watch the phase forty times, because there was no footage to re-watch. I re-read the five-day scorecard until I could hold it in my head, so that you would only have to read it once. What I found is a document with the right result and an incomplete route to it.

Core, part two: Jamal's load, and Abbas's 5 for 70

Aamer Jamal did two jobs in this match: seven wickets in the first innings and 55 off 81 balls with seven fours in the second. An all-rounder turning a first-class final with the ball and then holding the tail together with the bat. The number looks large; its meaning is larger.

In Pakistan's domestic structure an all-rounder is valued above a specialist because he fills two places, and in the politics of contracting one name does the work of two roles. Jamal took six wickets on Test debut in Perth in December 2026 — the identity was already established. The question is whether a player who takes seven wickets and bats eighty-one balls in a domestic final is being preserved for the national side or spent on it. The scorecard does not answer that. The training calendar and the workload plan do, and that calendar will remain just as invisible after this final.

On the other side, Mohammad Abbas: eighteen overs, seventy runs, five wickets. That spell is the most unheard fact of this match precisely because it belongs to the losing side. 296 in 74.5 overs is nearly four an over, while one bowler went at 3.89 with five wickets in eighteen. What that means is that most of MIT's 296 came off the other bowlers, and Abbas held one end so tightly that nothing came out of it.

Here is the contradiction worth underlining. On the final day a left-arm spinner took four; in the first innings a right-arm seamer took five. Same ground, roughly the same air, two different outcomes. Nobody should claim the surface helped the spinners — if it had, a seamer would not have taken five in eighteen overs. The surface was identical for both; the difference was in the batters' intent.

The contrarian angle: the 51-run margin is a lie, and the praise for Hasan Raza's 73 is incomplete

The first thing that will be written, and the thing I think is wrong: "won by 51 runs." The number is correct and nothing follows from it. The number that matters is that on the final morning 72 were needed, three wickets remained, and two hours were available. The moment Abbas was out, the match was over; the remaining 51 runs were procedural. A final in which the last four wickets fall for 38 runs has a margin of fifty or a margin of five — that is a language of record-keeping, not of cricket.

Second: Hasan Raza's 73 off 136 with eight fours will be called a fighting innings. Fine. Calling it a match-saving innings is false. He was part of the slide that took SBP to 147 for 7. The batter who was at the crease while five wickets fell did not arrest the fall — that is the plainest fact of the innings and the least written.

Third, and this is my actual position: SBP reached the fifth day because their batting order had already collapsed — the three wickets on the final morning were the sound of that collapse, not its cause. Mubashir making 32 at seven, Abbas eating thirty balls at eight, Kashif Bhatti at nine: that card tells you the real batters had already gone. When your most reliable blocker is a Test fast bowler, your match is already lost.

And fourth, the part that irritates me most: nobody appealed this match. No clear and obvious error appeared. No third umpire was summoned. No match referee was called. A final whose scorecard slips by a run, whose two wickets have no name attached, and whose first-innings total was never recorded, was quietly accepted — because no side lost anything by the mistake. That is domestic cricket's largest problem: we investigate only the errors somebody claims.

Forward

This final reminded me of something I wrote in 2026, after a one-run final, when I broke down a third-umpire run-out into fourteen frames. The question then was whether the ball had touched the bat. This time the question is the same question, moved from the pitch to the paper: did that one run exist?

Before the first ball of the next President's Trophy Grade-I final, I am registering this so it can be held against me later: if this tournament's calendar and playing conditions stay as they are, the next final will again be settled in a single fourth-innings session, and its true margin will again be under twenty runs, whatever the headline says about fifty. I would rather be wrong, because being wrong would mean somebody changed a batting intent.

The question is not how Markhor IT won. The question is who explained to State Bank of Pakistan — a side with a 59-run first-innings lead and a Test bowler — that blocking seventy overs was wiser than chasing 237, and whether anyone told them what a draw would actually have paid them.

Until that answer lives in a written condition, on the last day of every domestic final we will not know whether a team is playing cricket or paperwork.