Unscreened vs Cleared: The Verification Gap in Indian Esports Reporting

A report landed on my desk with nine sections. Every section had a table, every table had coloured indicators, and every single cell carried the same answer — N/A. Patch impact N/A, tournament format N/A, roster strength N/A, financial risk N/A, governance compliance N/A. Below it all was a line that has been stuck to my desk since 2026: what was never screened is not the same as cleared.

This was not an audit of an organisation. It was an audit of the process that runs among us every week — pull facts from a source, then judge those facts. That week the source arrived empty. And a system that demands one transfer story every Sunday was handed a document that said, plainly, I have nothing.

Indian esports has no institutional press corps. That means more than a shortage of stories. It means there is no external guarantor of credibility — no ombudsman, no ratings agency, no league-mandated disclosure format. What survives is the chain of sources and the habit of showing that chain in public.

In 2026 I walked out of a Delhi FM station's 9 p.m. sports slot and started The Window — a twelve-minute daily transfer podcast and a WhatsApp broadcast with 400 subscribers. That October, watching eight FIFA U-17 World Cup matches at Jawaharlal Nehru Stadium, I tested a method: an ISL club had split a loanee's wages 70-30 while its press release called it a straight loan. I had the agent's message trail and the club's own release, and they were cutting each other. The club amended the release in three days.

On 2 September 2026, PUBG Mobile was banned under Section 69A. Over nine days I spoke to fourteen organisations and forty-one players. One nineteen-year-old was owed three months' stipend on a contract whose force-majeure clause had been written for a different sport. In "No Game, Still Signed" I read that clause on air with his permission — Tuesday, 8:40 p.m., line by line. The first call came that same night, and it was not from a club. It was from another player asking, "My contract has the same clause. Can I read it too?"

Back to the empty report. An empty payload is not a minor technical glitch; it is a conclusion in itself.

Without a game title, even the category of analysis cannot be fixed. The first question in patch analysis is always this — is the change numerical, a mechanic rework, or a map rotation? The three behave differently. A numerical tweak reshuffles roster depth, a mechanic rework moves the skill floor, a map rotation lifts or sinks spawn-dependent teams. Without a title and a patch number, that choice cannot be made at all. In India the distinction matters because the BGMI and Valorant patch cycles run at completely different speeds; forcing both into one frame is a category error.

And here is the real issue: in a risk register, "no flags raised" and "no risk found" are not the same thing. If a report reaches a decision-maker with six risk categories marked N/A because nothing was ever checked, a reader can mistake it for "all clear." In Indian esports that mistake is expensive. A Tier-2 organisation that has not paid stipends for three months looks healthy in coverage — because nobody asked. That is a coverage gap, not a clearance of risk. The absence of a signal in an empty document is not evidence of financial health.

An empty payload has three distinct causes, and each needs a different fix. Extraction failed; the handoff got truncated; or the source genuinely had no esports substance. For the first two, re-extraction is enough. The third is where the real media problem surfaces — content that looks like esports but contains no name, no date, no number.

That is why, after 2026, I reversed my interview order: the contract question first, the feelings second. I keep a private contract database — start date, stipend, buyout, exit clause, force-majeure wording. In 2026, amid the BGIS ₹1 crore prize pool, I reported the first buyout figure in Indian mobile esports: a nineteen-year-old fragger moving from Tier-2 to Tier-1 for ₹6 lakh, on a two-year deal with a ₹9 lakh release clause. Two rival orgs called to argue about the number. That was when I knew it was right — the people arguing were not offering their own number, only disputing mine.

That same year I retired the word "joins." Every roster story now carries fee, contract length, buyout, and who pays the transfer fee — org or player. And beside the signing runs the ratio I ask every org for: how many players on written contracts, how many on verbal promises. The answer is usually the one that never makes a press release.

Here is the contrarian angle the industry cannot stomach: the empty report is the most valuable document in this market. The damage is not the blank space; the damage is the rush to fill that space with whatever narrative fits. One Discord screenshot, one "sources say," and the story is done.

My rule is simple: name sources by role — agent, club official, league registrar — never by name. And wait for the second source, and write openly that you are waiting. In 2026, Nikhil "Forsaken" Kumawat was caught at the eXTREMESLAND Asia finals in Shanghai and OpTic India collapsed overnight. The media at the time made it a story about character. I framed it as the structural failure of unaudited qualifiers, and gave three CS:GO players an unedited segment to describe what those qualifiers actually were. "Who cheated" and "who was never screened" are different questions, and the second one is the one that holds.

The next time an org writes "parted ways by mutual consent," or the next ban wave forces every desk to publish something the same night — the question will not be who had it first. It will be which desk had the nerve to write N/A, and which one filled that space with a name it will have to retract next week. That line is still stuck to my desk. What is on yours?