The Nine-Section Scouting Report With Nothing Inside, and the Trap of an Overly Complete Framework

In February 2026, Busan hosted the World Team Table Tennis Championships. Four months later, a nine-section file appeared on my desk. Every section had a heading, a table, a bolded conclusion line, a source note. And every section opened with the same phrase: insufficient information.

The technical assessment table had four rows, all four empty. The head-to-head table had five columns, all five empty. The risk matrix had six categories, all six empty. The only field in the entire file carrying real information was the domain label, two words long: table tennis. That was all the raw material I had to work with.

I sat still for a long while. What bothered me most was the familiarity. I had held reports that looked exactly like this one, except they contained numbers.

My trade runs on two tiers. The first tier reads an article and extracts information points: who, which event, what score, who said it, under what circumstances. The second tier takes that list and looks at it through nine familiar table tennis lenses — technique and equipment, player data and head-to-head records, event system and ranking points, the balance between China and the rest of the world, rules and governance, coaching staff and the talent pipeline, the risk surface, the public narrative, the industry transmission chain.

Each lens has its own anchor. To talk about form, I need results from the last 52 weeks, because the WTT ranking runs on a rolling window and old points drop off the ledger by themselves. To talk about durability, I need the win rate against opponents from other associations. To talk about pressure, I need to know how many points a player is defending over the next three months.

In table tennis, two rule changes have reshaped how a young player should be read: the 40mm plastic ball replaced celluloid from 2026, and the 11-point format came in from 2026. Each change devalues one generation of skill and revalues another. A scout who ignores those two markers will misread an entire cohort.

The file in front of me contained nothing. No title, no source, no date, no names. The nine lenses were still fully assembled, aimed into empty space.

The place I stopped longest was the overall risk assessment. It had been left blank, and the writer had added a line that was exactly right: blank does not mean low risk. An empty input does not produce a safe conclusion; it produces an unmeasured blank.

I kept that spirit and stretched it beyond the boundaries of one document. When I watch footage of a sixteen-year-old and cannot find serve data, I am not allowed to write in the report that she serves safely. I am only allowed to write that nobody has counted. Those two sentences differ in nature, and in scouting they differ in consequence.

The second thing worth naming is how emptiness hides. Nine sections, each with tables, order, a conclusion line, a confidence note. Formally, it looked tidier than many real reports I have read. It had rhythm, it ended with a recommendations section. A lay reader picking it up would assume the document was finished. The fuller the framework, the easier empty content hides.

I once fell into exactly that trap. In 2026 I wrote about an eighteen-year-old midfielder with a 92 percent pass completion rate and skipped the fact that he won only 38 percent of his duels. The piece was tidy, the numbers were complete, the argument was coherent. Three months later he was completely shut down in the final and the team lost 0-2. My editor made me rewatch five matches. Only then did I understand that I had built a beautiful frame on a missing fact.

Three years later I submitted a nineteen-page report on a young striker and it was thrown down on the table in the meeting. 19 pages were swept off the desk, but the truth is never swept out of time. I rewatched, rewrote, and the second version was accepted.

There is one more error, and it belongs to process. In that template, the "entities involved" field carried an instruction: identify them from the information points above. There were no information points above. It was a loop leaning on itself. Identifying who the subject is must be an output of the reading tier; it cannot be the work of the analysis tier. Doing it the other way round is like asking a video analyst who appears in footage he has never seen.

The most dangerous report in scouting is the one that reads too smoothly.

An empty report gets sent back. It is annoying, it wastes time, it forces the pipeline to rerun from the start. A smooth report gets approved. It enters meeting minutes, it becomes a line in a capability file, and six months later nobody remembers what it was built on.

There is a very real professional pressure behind this. People pay for opinions. A file that concludes with "not enough data" helps nobody decide, and does not help the writer be remembered. The natural instinct is to fill the gap. Fill it with general background, fill it with pre-existing knowledge of the event, fill it with sentences that are true of every player alive.

I fight that instinct with a control question: did what I just wrote come from the footage, or from my memory of a different player? If it is the second, I delete it.

Raw stone never speaks for itself; the archaeologist has to know how to listen. But listening to silence is also a technical movement, and it is harder than hearing the ball bounce off the table.

A failed report today can be tomorrow's winning formula. That nine-section file will never enter any of my minutes. It has just taught me something fourteen years of watching footage had not fully taught: the blank is data too, and the only person who can read it is the one willing to write down that they do not yet know. We do not read the future; we simply read the past more carefully than everyone else.