UAE's Notebook of a Loss: Squad Depth, the Labour Calendar and the Ledger of One Overthrow

The ball rolled towards third man off the last delivery of the sixteenth over, and I wrote one line in the notebook: “Nobody is warming up.” The evening light had dropped over the Dubai galleries, seven men stood in the UAE fielding ring, and the one man who sprints to cut the ball off near the boundary rope was not there. The next over returned the bill. Two boundaries, one overthrow, six runs on the board — exactly the margin the match ended on. Before I left the press box I wrote two things down separately: the scoreline of the defeat, and its cause. The news cycle will spend itself on the first. My notebook has kept a page for the second.

This Asia Cup qualifying fixture was one the UAE needed on the table, not just on the scoreboard. Net run rate, head-to-head, the schedule of the remaining group games — I checked those three columns three times the night before, because in a qualifier the points table is never only a win-loss ledger. But the number written most often in my notebook by the end of the match was not a batsman's score. It was twenty. Twenty days — between the last franchise league fixture and the start of the national camp.

To read that number properly you have to walk into the administrative frame of UAE cricket. ICC central allocations for Associate members, Asian Cricket Council tournament slots, and the qualifying calendar — those three layers together decide who plays where in which month. The UAE's problem has never been a shortage of talent; it is the gap in time between those layers. There is a separate line for Associate members in the ICC funding cycle, but that line cannot run an injury protocol for a fast bowler's back.

Look at the squad. There is a Muhammad Waseem at the top, a left-arm spinner like Aayan Afzal Khan through the middle overs, and experienced hands such as Rohan Mustafa or Basil Hameed. That list was not assembled by accident. In the UAE, eligibility outside birth runs on a residency clock — a rule that widens the pool on one side and injects uncertainty into a player's life on the other. A cricketer here carries two calendars at once: the calendar of his club or franchise contract, and the calendar of his visa and residency. When those two collide in the same week, nobody sprints to third man.

UAE's squad-depth problem is really a fifth-bowler problem, and the fifth-bowler problem is a calendar problem. That became clear as the innings wore on. Two seamers carried the first ten overs; a spin pairing bought some control through the middle. But the man needed from the seventeenth over onward had arrived from seven franchise matches inside that twenty-day gap, and his workload paperwork sits on a club desk, not a national one.

I logged the next ten overs ball by ball. Across four overs the two seamers conceded twenty-eight, not a single wide, and not a single yorker. The left-arm spinner bowled two overs for six and was then taken off — because three more matches are coming and the squad has no depth to absorb an injury. That is not a captaincy error. It is the arithmetic of squad planning. A side with five dependable bowlers can never extend a short spell; a side without them can never hide an over.

Batting showed the same picture. The UAE top order moves slowly in a chase because it is not permitted to take run-rate risk — the experience deficit in the middle order is covered by reducing strike rotation. Between the fourteenth and eighteenth overs there were four dot balls, and three of them were not deliveries but decisions. Those decisions do not come from the coaching board. They come from the table. In a qualifier you slow the batting tempo to protect net run rate — and the run rate you protected does not come back to you in the next match.

The fielding number speaks loudest to me. I counted six tracking points inside the boundary in this match; on every one of them the first step landed late. This is not a fitness failure. It is the invisible price of workload management. A player who has spent two straight months across three cities — Dubai, Sharjah, Abu Dhabi — will naturally put his first step down half a second late. That half-second stops at the boundary rope and comes back as six runs.

The third umpire has become the match editor, and in this game a slice of that editing changed the result directly. The front-foot no-ball and the UltraEdge review stopped play for roughly four minutes. My objection is not to the time; it is to the scale of the decision. Being given out on a millimetre line tells a batsman: you were not wrong, you were only late. The decision to play an attacking shot then becomes a penalty decision. A batsman who knows that two millimetres of his striking pad can send him back will change the shot. I watched that change through the middle overs of this innings.

Another ledger walks in from outside the match. Franchise cricket now runs a retainer-plus-appearance structure for free agents, a payment shape that never appears inside the cap. That money flow is not audited the way a transfer fee would be, because there is no fee — only small clauses in a contract. My old rule: money that never hits a server quietly rewrites selection. A player who collected a franchise retainer in November does not have the importance of a February national camp written on paper — only on his calendar.

The outside reading is easier. Two sentences are circulating after this defeat. One: UAE's batting is weak. Two: the captain cannot handle pressure. The first is wrong on the table. The second is unjust on the merits. The UAE were in the chase until the eighteenth over; reaching that point is the players' credit. And if blame belongs anywhere, it belongs to the three layers sitting above the table — the franchise window, the national camp timeline, and the qualifying schedule. Asian Associates choose between those three, and that choice decides their fortune, not their talent.

In 2026 I filed forty-one dispatches across thirty-two days in Russia, and learned there that distance is measured in dispatches, not kilometres. This Dubai match is the small version of that. Social media had written “UAE are finished” within nine minutes of the last ball. In my notebook those minutes hold six fielding tracking points, four overs of the fifth bowler, and one column of the franchise calendar. The locker room remembers what the broadcast edits out.

I know someone will read this and say it is an excuse. I am not writing an excuse, I am writing a ledger. The day injury protocol, workload paperwork and visa timelines are planned at the same desk, the story of UAE's squad depth changes. Until then, every win is personal credit and every defeat is structural debt. The schedule for the remaining qualifiers is due next week. Beside it I will add another column by hand: how many days ago each player last played four straight matches. If two names light up in that column for two consecutive weeks, then how many of them turn up at the next UAE camp will no longer be a question of talent.

One thing is worth remembering. The locker room was empty after play because press access was withdrawn under a board rule issued in January. But an empty locker room still has a pulse. The workload sheet left in the physio room, the Dubai dust on the soles of the shoes, and a roll of tape lying on the floor told me three things: the squad is tired, and the squad is not broken. That difference is the arithmetic of the next match.

So who receives the question now? Not the coach, not the selector. It goes to the administration, where the franchise window and the national camp dates are still copied into two different diaries instead of one. I wrote the same line in my notebook again, because it is still true: “Nobody is warming up.” The next time I write it, either I will have been proved wrong, or UAE's structure will have changed.