The Review Clock Tax: How VAR Resets a Match's Pulse After Two Minutes

In a match last season, a review began in the 67th minute. The stadium was still thick with the hum of a goal. The big screen flashed “CHECKING.” By habit I started a stopwatch — since 2026 I have logged every review's duration, the team that called it, and the outcome in a column. That review took 3 minutes 40 seconds.

The real number, though, was elsewhere. In the ten minutes after the review ended, the two teams produced just 2 shots combined; in the ten minutes before, they had produced 9. The noise did not come back — a hollow silence did. At first I thought it was coincidence. Then I opened the log. The spreadsheet remembered what the stadium forgot.

My review log began in 2026, at the Russia World Cup. Across all 64 matches I logged PPDA and xG, and alongside them I noted the duration of every VAR check — I logged every Russia 2026 match until the noise became a signal. Since then, Euro 2026, the ISL, the IPL and assorted bilateral series have brought the review dataset to 340 matches.

For each review I measure four things: the time from call to decision (in seconds), the calling team, whether the decision was overturned, and the combined xG of both teams in the ten minutes after. Those four columns are the spine of my data dictionary. In a match report I do not write “desire” or “passion” — I write strike rate, PPDA and shot maps.

Let me be explicit: this is not a broadcast-corrected dataset; it is my own hand-logged record. For what the broadcast never shows — the hush of the dugout, the tone between referee and captain, the crowd's patience in that moment — I keep a separate column. I keep a column for what the broadcast never shows. In this piece I will stay alert to everything outside that column.

The question is simple: does review duration relate to a match's rhythm? First, the distribution. Across 340 reviews the median duration is 78 seconds, the mean 96 — a few long reviews are dragging the average up. Ninety percent of reviews finish under two minutes. The remaining ten percent — those that cross two minutes — are where the story hides.

I split the reviews into two groups: under two minutes (n=306) and over two minutes (n=34). Then I looked at the combined xG of the following ten minutes.

• Combined xG after reviews under two minutes: 0.29 (per ten minutes)
• Combined xG after reviews over two minutes: 0.14

In other words, in the ten minutes after a long review, a match's attacking output roughly halves. But I am suspicious of the sample size — 34 long reviews is not a large sample, and the confidence interval is wide. So I will not claim flatly that “long reviews stop goals.” I will say: the two-minute line is an observable signal, not a fixed rule.

By competition the picture sharpens. At the 2026 World Cup the median review time was 84 seconds; at Euro 2026, 91; in the ISL, 72; and in the IPL, DRS has a median of about 65. The bigger the budget and the more cameras, the more time — not accuracy, but hesitation.

Now the cross-code comparison, my favourite test. VAR in football and DRS in cricket are both technology-driven reviews, but their effect on rhythm differs. Football review durations scatter widely: some end in 40 seconds, some stretch past four minutes. Cricket's DRS is generally faster — ball-tracking and UltraEdge running together cut the time. But in cricket the review arrives exactly when a big innings is gathering pace.

Across the last three IPL seasons I have seen one pattern: reviews tend to arrive in the very over when strike rate peaks. The signal, then, is probably not the review's fault but the timing of the review's use. I want to separate that from coincidence.

Seen through PPDA, another layer opens. In the ten minutes after a review longer than two minutes, pressing intensity — the combined PPDA of both teams — rises by roughly 1.4 points on average. Attacks fall, pressing rises. Who benefits? The defence. The team that loses a review often loses its rhythm for the next ten minutes; the team that wins it gets an artificial breather. In the ISL 2026-21 season, in empty stadiums, the pattern was sharper — without crowd noise, momentum took longer to return after a review break.

One more thing I tried to measure: the caller's decision. A match produces about 2.1 reviews on average; roughly 38 percent overturn the decision. But success does not rise with time — the opposite: reviews taking more than two minutes overturn only about 31 percent of the time. More time does not mean more accuracy; more time usually means more doubt.

That doubt is the rhythm tax. And rhythm is hard to restore, because football and cricket have both become games of moments, where a break changes three things at once — the advertising, the breathing, and the morale.

Here a question surfaces, debated in both worlds: should a hard cap sit on the review clock? Several leagues have trialled shot clocks or time limits, and my log suggests the rhythm cost is lowest below two minutes. But this is not a technology question; it is a policy one.

Now it is time to stand against my own model. Is the pattern I am showing really caused by the review, or do reviews simply arrive in moments that are already slow? This is the classic confusion — correlation is not causation.

Consider: a review often arrives when a match is tight, attacks are few, the defence is set. Then the low post-review xG may not be the review's result but the continuation of that situation. My log cannot fully capture that distinction, because I do not measure a match's “expected rhythm” — only its actual rhythm.

Second, my dataset cannot see many things: player fatigue, injuries, dugout instructions, a relationship with the referee, even the weather. The empty-stadium ISL data taught me that when the environment changes, the meaning of the same match changes. The eye test is a hypothesis, not a verdict — and so is the log.

Third, an opposite possibility exists: a long break may not favour the defence but refresh a tired team. In a few matches I have seen the weaker side return fresher after a review break. That runs against my thesis, and so I will not hide it.

And one caveat for myself: for the legend that surrounds the review intelligence of captains like Dhoni or Kohli, my log does not hold a sample worth testing. So I pass no verdict there — I only keep the record.

So how well does the two-minute line hold? My answer: the direction holds, the magnitude does not. I will not write policy from 34 long reviews. But one demand I will keep: put the review clock on the pitch, in everyone's sight, visible.

Next season I will watch one number: how many times the ball changes feet in the first ten minutes after a review ends. If that number keeps falling, I will know the problem is not technology but time. And if it does not fall, then perhaps my whole thesis was one large coincidence — which I will admit, without embarrassment.

What do you see? Next time a review starts, start a clock. I will.