Empty Cells, Empty Space: The Two Lies That Read the Same

One February morning a club analyst in Barishal sent me a single-page match report. Twelve columns, eleven filled. The twelfth was headed defensive actions in the left half-space. The cell was empty.

Over morning tea the coach flipped through it and said, nothing went wrong on the left. I asked how he knew. He said, look, there is no data there.

Here is what we keep walking past. An empty cell has at least two causes. Either nothing happened in that zone, or the tracker never recorded it — the camera panned away, the software crashed, the operator left for a coffee. On the monitor the two look identical. The same blank cell. The same white patch of pitch.

And the coach made a decision on that white patch.

Context: seven links in the chain

Football's information supply chain now runs through seven links. A tracker in the stand. A data provider. A central database. The club dashboard. The analyst. The coach. The journalist. The supporter.

At every link there is a chance the system returns an empty payload while the schema shell still looks perfectly valid — the container built to carry information stands upright, and inside there is nothing.

Software engineers call this a null-handling problem. Football has no name for it, because we never think about it. We assume that data existing means truth existing.

On 16 May 2026, when the Bundesliga returned to empty grounds, I watched nine matches with the crowd track muted. I counted defensive-line verbal exchanges by hand — 148 per match, against 210 in the same fixtures before the hiatus. Pressing triggers in the first fifteen minutes fell away sharply. The essay The Quiet Pitch came out of that log.

One thing from those weeks has stayed with me. One channel in my headphones was dead. For thirty minutes I thought a defensive unit had stopped talking to itself. It had not. The microphone was loose.

A dead microphone and a silent back four produce the same audio file.

This is not only a technology story. In the summer of 2026 I watched two tournaments at once — Euro 2026 and the Tokyo Olympic football tournament. Midway I noticed something uncomfortable: the two data sets carried the same kind of zero, but the zero meant different things. In one place a zero meant this never happened here. In the other it meant we never tracked this. One symbol, two languages.

That was when I started reading about handball's 7-on-6 attack and futsal's pivot, and built a twenty-two term translation glossary. The point was to read football's blanks in another sport's grammar.

Core: the empty space in disguise

My title holds two things — the empty cell and the empty space. As a tactical analyst I have spent most of my life chasing the second. I now think the first is the second in disguise.

When I started The Half-Space from a Barishal rooftop, the whole method came down to one question: where does the space appear before the pass? The pass is the last event, not the first. Half a second before the ball rolls, which way has the defender turned his shoulder, which midfielder has glanced back, who is standing in shadow — that is where the story is.

The method hides a lovely property I did not understand at first. The half-space is the lowest-touch zone in almost every data set. The ball rarely goes there, nobody stands there, and on a heat map it shows up white. That white patch carries the most information on the sheet.

Because nobody being there does not mean the zone is unimportant. It means somebody's absence was a decision. The back four left that space open on purpose, or left it open by mistake. Both are information. Telling them apart is the job.

Barishal's grounds are narrow. At one Divisional league pitch I measured the distance between the two touchlines and found it ten to twelve yards tighter than a typical European ground. The half-space almost stops existing. The fight for that territory migrates somewhere else — the channel between full-back and centre-back.

When I try to drop European half-space theory onto our pitches it breaks. That break is what teaches me where the theory works and where it does not. Constraint is my laboratory.

The same disease in a spreadsheet

Now move the argument into the spreadsheet.

A large share of the match reports that reach me carry the same illness. A column is empty, and it gets read as nothing happened. But an empty cell is a question, not an answer. The question is: did nothing happen there, or did nobody see it?

Those two possibilities lead in opposite directions.

Say a team's PPDA row is blank. The analyst can decide two things. If he concludes the team did not press, he adds pressing drills to the week. If he concludes the tracking data was lost, he sits down with the video. One empty cell. Two contradictory training sessions. And the empty cell will never tell him which.

I have watched this mistake many times, and made it myself. On 11 July 2026, England led Croatia 1-0 in the World Cup semi-final. Within four minutes of the whistle I filed a half-time note: Croatia would shift to a 4-1-4-1, Perišić would pin high, the right channel would flip. Croatia won 2-1 in extra time.

That night people called me a magician. Honestly, it was not prophecy. It was a listening habit. At half-time I stopped reading the score and started reading the gaps — the space opening on England's right.

The gap was visible to me because I had no empty cell in my eye.

An analyst who only reads the dashboard struggles with this. The dashboard does not show him the space. It shows him the absence of the space. And absence never testifies.

My own logs hold a strange pattern. Through May and June 2026 I kept two kinds of note. One was a pitch map — where the ball went, who pressed. The other was an audio log — what the defensive line said to itself.

In one match the two logs refused to agree. The pitch map said the line was standing high and pressing. The audio log said two of the four defenders were not calling to each other at all.

Which was true? Both. The team pressed physically but without coordination. Uncoordinated pressing means a corridor ten metres wide. You do not see that corridor on video, because empty space has no colour.

The default-value trap

Football repeats a phrase: we make data-driven decisions. It sounds good. But data-driven does not mean data-complete, and there is a trap between the two.

Suppose your tracking system assigns a default value to every player. A player who never came on still gets a number. A zone the ball never entered still gets a zero. The table now looks complete. No empty cells. And part of the information is invented.

That is the most dangerous state of all. An empty cell at least announces itself — I know nothing here. A filled cell holding a wrong or default value hides its own ignorance.

I once saw a club's mid-season review with a completely blank injury column. Green tick. Nobody hurt. A member of the medical department later told me the data had simply not been published that month. Deliberately.

A blank injury column and a fit squad look the same. A coach who cannot tell them apart will believe his whole squad is available, and lose three starters the following weekend.

I will say this plainly, because it is a position I hold. When a player returns from injury and someone says he has to prove himself, that sentence is an extra load. That load sits in no column anywhere, but it shows up on the pitch. Return-to-play data tracks sprints and distance. It does not track pressure. That pressure is another empty cell — everyone knows something is in it, nobody measures it.

The provenance question

This raises a question football has not fully answered.

If we cannot verify where a number came from, the number is better absent than present. Absent, we stay careful. Present, we trust.

One possibility is worth thinking about. A tamper-evident log for match data — every entry stamped with who wrote it and when, and every cell that was never written at all marked as such. Then zero and missing would never again look alike.

This is not a proven method in football, and I am not claiming it is the answer. The question is legitimate because the problem is real. Our systems still cannot separate do not know from zero. And a coach who cannot separate them is working with decoration.

In Bangladesh the problem sharpens. Divisional league grounds are narrow, the turf uneven, the air humid. Placing a tracker here is a compromise — fewer cameras, limited angles. Empty cells are far likelier than in Europe. Yet decisions must be made with the same confidence.

That is why, in our football, the eye still outranks the database. Calling that backward would be wrong. It is mandatory redundancy — two systems running together so that when one fails the other holds.

Empty cells in the referee's book

There is one more place where empty cells speak loudest — the referee's ledger.

We measure referees by cards shown and fouls given. The foul he did not give has no column anywhere. The specific challenge that always escapes punishment in an eighty-thousand-seat stadium under pressure never reaches a table.

There is no need to call it conspiracy. It is far more ordinary than that: stadium aura, camera count, tomorrow's headline. Decisions in big-club matches are discussed more, so an unconscious tendency to avoid the doubtful call appears. In a small club's match that pressure is absent.

Yet in the data both look the same — numbers in the columns, no empty cells. The foul that was waved away does not exist in the database. And nobody writes a report about something that does not exist.

The referee's table looks complete, and is half true.

Three habits

Over the years I have built three habits that keep pulling me out of the empty-cell trap.

Freeze before the pass. Not while the ball is rolling — half a second earlier. In that frame, look for who is not there. Presence is easy to see; absence has to be looked for.

Attach a who-saw-it to every number. When two trackers cover the same match, compare their figures. Where they disagree, an empty cell is hiding — one of them did not see it.

And on any clean table, ask first which column was never filled. The cleaner a table looks, the likelier someone has covered a dirty cell.

I once sat down with a possession line — 63 percent against 37. A clear picture. Then I looked at the pass network and saw the winning side's left-back had no outgoing link at all. The team had kept 63 percent of the ball and left its entire left flank as a black hole.

The next match, the opponent scored twice into that hole. The data did not lie. The data was silent about that zone, and we read silence as consent.

One more note belongs here. Watching Euro 2026 and the Tokyo Olympics side by side in 2026 taught me that the language of zero changes by sport. In handball's 7-on-6 attack, an empty space is a space deliberately emptied. On futsal's pivot, an empty space is a space abandoned by error. In football we paint both the same colour.

So at half-time I now drop the score and start reading gaps. The half-time note was not a prophecy; it was a listening exercise. You can hear a defender's feet, a goalkeeper's instruction, and the space nobody is occupying.

Contrarian angle: the sickness of a clean table

The conventional read is that more data means better decisions. More columns, more metrics, more dashboards. That read collapses in one place.

A fuller table and a fuller understanding are not the same thing.

A table stuffed with defaults is worse than an empty one. The empty table is at least modest — it says, I am incomplete. The full table says, I am complete, while part of it was manufactured.

The real blind spot is not in the analyst's method. It is in the analyst's trust. Someone who confuses completeness with reliability is not trusting the numbers. He is trusting the numbers' existence.

And this is where the supporter's eye becomes essential. A supporter's mind holds no empty cells. He watches all ninety minutes and the whole pitch. He may not know the word PPDA, but he can tell you, they were asleep on the right today. The dashboard will not say that. The dashboard will say, there is no data on the right.

The distance between those two sentences is the whole subject of this piece.

Takeaway

I keep returning to the same question, year after year: where does the space appear before the pass?

Now I carry a second question beside it: did anyone see that space, or did nobody think to look?

Next time you watch a match, try something. Put the scoreboard down. Put the table down too. Just ask which column nobody filled in — and what it is hiding.