The Blank Cell in the Referee's Report: When Officiating Data Returns Zero

The clock on the wall of my Manchester office read 3:47 a.m. On the screen sat a data file pulled from the statistics system of a professional tennis tournament: six rows, four columns, every cell blank. Not a single figure. Not a single officiating code. Not a single error flag. Just empty cells lined up like an incident report nobody had filled in.

A beginner would have closed the laptop and gone to bed, then written one short line in the morning report: "No disciplinary issues recorded." I know that, because nine years ago, on a night much like that one, I nearly wrote exactly that line.

What kept me up until nearly four was a small technical detail: the file had not reported an error. It returned success. It simply returned zero.

In my trade, that is the most dangerous kind of accident. A wrong number invites an argument. A blank cell invites quiet belief.

An empty data table does not mean there is no risk. It only means nobody measured.

Why a discipline reporter sits and counts blank cells

I work in England, writing about tennis for English readers, but I was born in Vietnam. That arrangement forces me to write two layers of explanation for the same event: one for readers who know how ball-tracking systems draw a trajectory, and one for readers hearing the phrase "service line fault" for the first time.

My job is tournament discipline. Cards, cautions, technical violations, conduct violations, time violations, medical-protocol violations, breaches of off-court coaching rules. It sounds dry. But every line in a referee's report is a variable capable of shifting the course of a tournament.

I came to the job by a roundabout route. In 2026, aged eighteen and in my first year studying Movement Science at the University of Manchester, I volunteered as a data-analysis assistant for a local amateur club. In a match in the Northern Premier League, I found two penalty-area fouls the referee had missed that the official statistics system had never recorded. I spent three days rewatching the footage, counting each contact, and building a comparison table between what I saw and what the report said.

The result of those three days was not an article. It was a habit. From then on, everything I wrote had to pass through at least two independent sources — and when two sources agreed, I started suspecting both.

England is a good place to raise that habit. English football went through more than seven years of VAR argument, and across those years I noticed something few people say out loud: most of the arguments were not about the technology. They were about the operators, and about the fact that nobody wanted to document the decision process.

Tennis is entering the same phase. In 2026, Wimbledon was held without line judges for the first time in 147 years, after the organisers announced the switch to electronic line calling in October 2026. ATP events moved to the same model. A generation of fans is growing up having never seen a line judge raise a hand and call "out".

When every ball is adjudicated by an electronic system, the central question of my trade changes. The old question was: did the official see it correctly? The new question is: who checks that the system saw it correctly?

And the answer to that new question, most of the time, lives inside data files. Data files that sometimes return zero.

Layer one: where the number comes from

My verification ritual has three layers. The first is provenance: where did this number come from, who entered it, on what device, and at what time.

That sounds simple. In professional sport, very few numbers have a single origin. A figure for double faults can come from the electronic line-calling system, from the chair umpire tapping a tablet, or from a third-party data provider sitting in a different room watching a different screen. Those three sources can produce three different results for the same point, and none of them considers itself wrong.

I once tracked a case where the official statistics system credited a player with 71 percent of points won on first serve. A second provider recorded 68 percent. The difference came down to three points that one side counted as a first serve and the other as a second, after review showed the ball clipping the line. Three points in a match sounds small. But if those three points fall inside a tiebreak, they can decide a set, and a set can decide a tournament round.

When data contradicts the eye, trust the data — but never forget to check where it came from.

The tennis writer Mike Dickson, whose method I studied, never offered a number without saying where it came from. That is not formal caution. It is the mechanism that lets a reader judge the reliability of the whole piece. If I say a player held 84 percent of second-serve points across a tournament, I must also say: the figure was published by the organisers, updated after the semifinal, and excludes qualifying.

Without that part, the number is just an assertion.

Layer two: the historical context of the rule

Layer two places the number inside the legislative history of the rule. A sanction read in a vacuum always looks absurd. Placed on the timeline of rule revisions, it usually becomes understandable to the point of boredom.

Tennis amends its rules slowly and documents them carefully. The 25-second serve clock was introduced at major events from 2026, and since then every time violation can be measured against a countdown clock displayed publicly on court. That means this category of violation has no room for emotional dispute. Either the clock hit zero or it did not.

Even there, a gap remains. When does the clock start? From the moment the umpire calls the score, from the moment the crowd stops applauding, or from the moment the player touches the ball to prepare? Each reading produces a different number from the same situation.

That is why I spent six weeks of 2026 memorising the card system and logging 189 card incidents from a football World Cup. It sounds off-topic for a tennis reporter. But the structural logic is identical: a rule only means something when it is applied consistently, and consistency is only measurable if you hold a reference dataset large enough to test it.

A tournament is a system. Each refereeing decision is a variable. My job is simply the test.

In tennis, that reference set is even richer. Off-court coaching was once banned outright, then trialled, then legitimised. Toilet-break rules once allowed a long window, then were narrowed after the majors recognised that some players used it as a tactical interruption. Medical rules allow three minutes of treatment, and inside those three minutes a match can turn completely.

If you do not know the revision history of those rules, you will read a decision made this year with the eyes of 2026. And you will reach the wrong conclusion.

Layer three: deviation from the norm

Layer three is the one I enjoy most and the one that costs me the most time: comparing a figure with the average for the tournament, the surface, and the phase of the season.

A player called for twelve service faults in a match sounds like a lot. But if the tournament average is nine with a standard deviation of three, twelve is exactly one standard deviation out. Not worth writing.

By contrast, a player called only five times when the average is eleven on comparable sample size — that is where the story is. Perhaps the player changed the toss. Perhaps the chair umpire that day has a reputation for leniency on service faults. Perhaps the ball-tracking system on that court was not recalibrated after a damp night.

I call those three competing hypotheses, and my rule is never to publish while I have eliminated only one of three.

This is where I must confess something about my own limits. For years I leaned absolutely toward data. I treated the viewer's feel as secondary. That is right most of the time, but it becomes a blind spot when the dataset in my own hands is the broken thing.

A corrupt data file does not accuse itself. It sits there, tidy, correctly formatted, with the right column headers, waiting to be believed.

Ball tracking and the question nobody wants to ask

In tennis, electronic line calling is the most trusted technology in any sport that uses technology. People rarely argue about it the way they argue about video review in football. The reason is straightforward: a tennis ball's trajectory is a relatively contained physics problem, and the system has enough data to reconstruct the path even in the portion after the bounce.

But there is a figure rarely mentioned in broadcast conversation. Every measurement system has a margin of error, and that margin does not disappear when the system is installed in a centre court holding fifteen thousand people.

So my question is never "is ball tracking correct". My question is "when was ball tracking calibrated, by whom, and under what procedure".

Ball tracking is not wrong. The person who calibrates ball tracking is wrong. And that is where my work begins.

I spent weeks reading technical documentation on line-calling systems, and what caught my attention was not the algorithm. It was the operations. Before every tournament the equipment must be checked, the coordinate frame rebuilt, the cameras aligned to a fixed datum. If one camera sits a few millimetres off its reference position, every trajectory near the sideline shifts in one direction.

That does not produce random error. It produces systematic error. And systematic error is the hardest kind to detect, because it repeats identically in every situation, which makes it look like truth.

I log every card, every minute of added time. Because a wrong number repeated three times becomes a fact in the end-of-season report.

When Wimbledon moved fully to electronic calling from 2026, I wrote a short piece on the calibration procedure, and several colleagues asked why I cared about that when the tournament was clearly running smoothly. My answer was: running smoothly in week one proves nothing about week two, and a calibration fault in a semifinal gets no chance to be corrected.

The card filed in the wrong place

In 2026, as a second-year student, I was assigned to report a derby between the University of Manchester and the University of Liverpool. In the piece I wrote that the referee had shown a yellow card to a defender in the 23rd minute.

In fact, the card went to his teammate.

I was severely reprimanded by my editor and had to write a letter of apology. But my lesson was not about the player's name. It was that I had taken an event from a single source and moved it straight into copy without asking one further question. I had seen the card on screen and assumed the recipient was the player closest to the ball.

A card filed in the wrong place can change the course of a season. I was once the person who wrote it wrong.

In a disciplinary record, assigning a sanction to the wrong subject produces three cascading effects. First, the wrongly named player is labelled a disciplinary problem, and that enters his long-term statistics. Second, the player who actually received the card is not counted, and if he sat near a suspension threshold, that threshold is miscalculated for the next match. Third, the opposing team's analysis staff prepare a plan built on false data.

One wrong sentence about one card can affect one team. One wrong dataset about one season can affect an entire system.

That error also explains why I hate blank cells as much as I do. A blank cell in a "card recipient" column is not neutral information. It is a silence the reader will fill with a guess.

Morocco, 87 tactical fouls, and the 32 percent

In 2026, working as a discipline reporter for a football site in Manchester, I was assigned to track Morocco after they reached a World Cup semifinal. I spent four weeks analysing twelve of their matches, counting 87 tactical fouls in total, and finding something the quick bulletins had entirely skipped.

Morocco's defensive system was built on cutting off the player without the ball, not on direct duels. They let opponents receive, then blocked the next pass. That is why the team cleared the ball more than most European sides while collecting cards at a rate roughly 32 percent below average.

That 32 percent was not a pretty coincidence. It had a technical cause. A direct duel usually ends in a tackle and a card. A blocking action usually ends in a misplaced pass and no card at all.

Reading only the summary table, you would write: "Morocco defend physically." Reading the summary table and then rewatching twelve matches, you would write: "Morocco defend by choosing not to contest."

Those two sentences lead to completely different tactical conclusions. The first leads to the recommendation "control your emotions". The second leads to "break the passing-lane structure".

This is the point I always press with interns: data does not generate insight on its own. Data generates insight when you go looking for the mechanism behind it. And that mechanism only appears when you rewatch the footage, count, and benchmark against the average.

It is also where I built my standard question: why is this number higher or lower than the norm? Without that question, all analysis is description.

Portugal, 41 percent, and 23 matches

In 2026 I was promoted to senior discipline reporter after a finding I initially assumed was a data-entry error.

I was reviewing the disciplinary data of a national team in international matches and noticed an unusual pattern: their card rate ran about 41 percent higher in matches officiated by referee teams from one particular country.

My first reaction was to doubt myself. A pattern like that is easily produced by a small sample, by a badly chosen window, or by an error in the source table.

I spent weeks rechecking. I analysed 23 matches between 2026 and 2026, combined the figures with historical head-to-head data, and wrote an investigation of roughly 3,500 words. In that piece I did not conclude bias. I presented the pattern, presented the competing hypotheses that might explain it, and stated clearly which hypothesis I had not eliminated.

The article was later used by a refereeing researcher as reference material when assessing the consistency of referee teams at a major tournament.

What I learned from that case was not how to write an investigation. It was how to say "I do not know yet". In this trade, "I do not know yet" is a professional answer. It is entirely different from "there is nothing to know".

And that is why a blank cell in a data table bothers me more than a disputed number. A disputed number invites me to check. A blank cell invites me to skip.

Effort metrics and the wasted run

There is another kind of data I always view with suspicion: effort data.

In sports that lean on movement metrics, distance covered and sprint counts are usually packaged into a single effort index and presented as a measure of fighting spirit. The player who ran the most is praised for leaving everything on court. The footballer who covered the most ground is praised for never giving up.

But distance covered cannot distinguish between running that works and running that does not. A player dragged across the court because of poor positioning will post a very high distance figure, and that figure will be recorded as a positive signal. Meanwhile a player who stands in the right place, reads the ball early and needs two steps will post a low figure and be judged as lacking effort.

Running a lot is not running well. An effort index does not measure effort. It measures distance.

This is the most dangerous family of data trap, because it is not technically wrong. The number is perfectly accurate. Only the interpretation is wrong.

For my trade, this has a direct consequence. When a match is described as "tense, full of contact", I always check whether the number of contacts corresponds to the number of fouls recorded. Very often the two figures do not match. And when they do not match there are always two possibilities: either the official missed something, or the system classified something incorrectly.

Both possibilities are worth an article. Only one of them is a human error.

The blank cell in the risk table

Back to that night in Manchester.

When I opened the file and saw six blank rows, my first reaction was to check the connection, then the access permissions, then to pull the same data from another source. All three attempts returned the same result: success, with empty content.

That was the moment I realised I was looking at a very specific occupational accident. Not an accident of data. An accident of process.

In any analytical system, a risk table is designed to answer one question: what are we facing. Each row maps to a risk category, each column to an attribute of that risk — level, probability, impact, mitigation.

When every cell is blank, that table stops being a risk table. It becomes a mirror. Whoever reads it sees what they want to see.

The optimist reads: no risk. The pessimist reads: nobody controls anything. Both are wrong, and both may act on a wrong conclusion.

Worse, in many publishing workflows a blank table passes editorial review without being stopped. Because review systems are built to catch wrong data, not missing data. Wrong data has a strange format. Missing data has a perfect one.

I used to think this was a technical problem for data departments. Reading deep analytical reports on sport, I realised it is an editorial problem. A reporter who receives an empty file and writes one line saying "no issues recorded" has, without meaning to, made a claim about reality for which he had no basis whatsoever.

The tool and the operator

In football I am always asked the same question: has video review made football worse.

My answer has not changed in years: the tool does not adjudicate. The operator adjudicates. Every video-review controversy I have followed, traced to the end, terminates at one of three points: which frame was chosen, which moment was chosen, and how the law was interpreted.

The system is not wrong. The operator of the system is wrong. And that is where my work begins.

Tennis is walking the same road, about a decade behind. When electronic line calling replaced line judges, the volume of on-court disputes fell sharply. But disputes did not vanish. They moved up a level: disputes about process.

Who checks the cameras before a match? Who decides a system is ready? When the system calls a ball out, is there a record of the full sensor data from that instant, and how long is that record kept?

Without answers to those three questions, people fall back to the old position: trust the screen. And trusting the screen is an act of faith, not an act of verification.

Major-tournament pressure and the compression of emotion

I am writing this during a major-tournament cycle. That is the phase when everything compresses: more matches, more decisions, more disputes and less time to verify any of them.

At a major, an official may work many consecutive days, on different courts, with different crews. A player may play five sets over four hours, then play again three days later. A decision in the 200th minute of a match may be taken by someone who has already worked eleven hours that day.

No data table measures the fatigue of a decision-maker. And that is the largest blank cell in every analysis I produce.

I can count how often an official was overturned. I can count how often a ball-call was contested by a player. I cannot count how often a person made a wrong decision because they were exhausted.

That is why I always write about officiating errors with a line about working conditions. Not to excuse. To make readers understand that a decision is the output of a chain of conditions, not of a single instant.

The counter-argument: when emotion and law disagree

Here I have to argue against myself.

There is a position I hear constantly from spectators, and I understand it: if the replay shows the ball touching the line, there is nothing left to discuss. If the system calls it out, it is out. Emotion has no place in the control room.

That position is correct, but only up to a point. It is correct at the level of the verdict and wrong at the level of the process.

A verdict can be accurate while the process that produced it is flawed. That is what most sports argument skips, because people only see the final result on the big screen. Nobody sees the calibration test at seven in the morning. Nobody sees the system log. Nobody sees the technician who worked until two.

I once fell into the opposite trap. In my early years I believed that if the process was right the outcome was right, and that anyone disputing the outcome simply misunderstood the law. That stance made me fast, confident and wrong.

My first mistake was not the red card shown to the wrong player. It was believing I would never show one to the wrong player.

So when readers tell me they do not trust the numbers, I do not wave them away. I ask what they do trust. Very often the answer is: what they see. And what they see is one frame from one camera angle, chosen by a system.

What I still cannot verify

An article about verification that does not state its own limits is unfinished.

I have no access to the raw data of line-calling systems. I only have processed data, published after the match. Which means my entire job happens on the second floor, not the first.

Nor can I verify certain personnel questions: who performs the calibration, how that person was trained, how shifts are handed over. These are real blanks in my trade, and they can persist for years without fans knowing.

And I know that some blank tables are genuinely, honestly blank. Not because a system failed, but because nothing happened worth recording. Telling those two situations apart is the whole of my job.

The difference comes down to one question: was the system running, and is there evidence that it ran?

If the answer is yes, a blank cell is information. If the answer is no, a blank cell is just a blank cell.

A thought pointing forward

The next phase of professional sport will not be decided by who owns the best technology. It will be decided by who keeps the best verification log.

When every ball is called by machine, when every card is digitised, when every decision leaves a trace, what creates the difference is the ability to prove the system ran correctly — and the ability to say "I have not verified this yet" without it being read as weakness.

In the coming decades, an empty dataset may generate more controversy than a wrong one. A wrong file has someone accountable for it. An empty file lets everyone claim they followed the correct procedure.

I am not writing this to accuse anyone. I am writing it because at 3:47 that morning, if I had gone back to sleep, I could have written one line that would have made readers believe there was nothing to worry about.

And if there is a single lesson from all the other lessons of the past nine years, it is this: the blank cell is not a place to rest. It is a place to start making phone calls.