The V.League Transfer Window: The 47-Situation Code and the Meters Nobody Buys

The V.League Transfer Window: The 47-Situation Code and the Meters Nobody Buys

One July afternoon, when the full-time whistle had faded and the stands held only rows of quietly folded plastic seats, I stayed behind in the stadium's technical room. On the screen in front of me was a recording of a V.League match, winding back through every phase of play in slow motion. In my hand was the movement data sheet of twenty-two players — fourteen columns of numbers that no spectator outside had ever seen. The away team held 63% of possession, completed more than six hundred passes, yet their shots on target could be counted on one hand. The home team lost. But in the second half, they counter-attacked seven times following exactly one repeating pattern: winning the ball on the right flank in the opponent's half, a diagonal long ball within two seconds, and a striker running into the gap between centre-back and full-back. I marked it in my notebook. Code 23 — counter-attack after losing the ball in the opponent's defensive third. Four days later, I read that a V.League club was negotiating to buy that very striker who had scored twice in that match, at a fee reported as the highest of their mid-season transfer window. I re-opened the tape. They were buying goals. I saw the meters of running behind them.

The transfer window is a season of noise. Across every platform, dozens of names are paired with dozens of clubs every day, most of which go nowhere. Fans wait for a signature, the media waits for a figure, and clubs wait for an excuse to explain why they have not acted. Amid all that noise, one question is rarely asked properly: what does a V.League club actually buy a player based on?

After twenty years with a pen and nearly forty years in the stands, I have learned that most transfer decisions here are made on three things: goals, pre-cut clips, and the memory of the most recent match. All three are deceptive indicators. Goals are the result of a system, not the cause of it. Pre-cut clips remove precisely what needs to be seen. And the memory of the last match is the enemy of every serious scout.

In this transfer window, as V.League teams scramble for players, I decided to sit down with my notebook. Three years ago, while the pandemic shut down football worldwide, I spent six months re-watching recordings of two hundred matches, meticulously noting each repeating pattern. The result is a classification system of forty-seven situations, numbered 01 to 47. I call it the code table. It is not perfect. But it gives me something the media never gives me: a neutral language to describe a match before pricing it.

What I have learned over the years is this: possession percentage is the most deceptive metric in football, because it measures ownership rather than danger. A team can hold 63% of the ball and create six chances, while a team with 37% creates seven — and we still call the first team the one controlling the game. In the V.League, where many sides grind out 60% of possession through meaningless sideways passes in their own half, this confusion causes contracts to be systematically mispriced.

Let me start by opening my notebook and counting.

In that July afternoon match, the away team completed six hundred and nine passes. If you count only the passes that advanced toward the opponent's goal and beat at least one pressing line, the number falls to roughly one hundred and four. The passes into the danger zone — the kind that, if intercepted, could let the opponent counter — come down to forty-one. From those forty-one passes, they produced four shots and one goal. Meanwhile, the home team completed only three hundred and seventy passes, yet had twenty-two passes into the danger zone, producing seven shots and two goals. My code table classifies this clearly: Code 12 is a safe sideways pass, Code 18 is a vertical line-breaking pass, Code 23 is a counter-attack after losing the ball in the opponent's defensive third, Code 35 is an offside trap in midfield, Code 41 is an overlapping combination to create two-on-one. When the whole match is coded, the picture reverses completely against the stat sheet the fans see.

This is why I write this line in every one of my notebooks: a 0.1-second error can change the colour of a trophy, but I still like to measure three times. A surplus run of 0.8 metres in the eighty-ninth minute, when the match has already been decided, appears in no bulletin. But it is what separates a player willing to exceed the limits of the map from one who accepts the map already drawn.

I want to spend most of this article on what the transfer window is forgetting: space, decisions, and the meters of running nobody buys.

First, the problem of the possession player.

In this transfer window, I have been tracking a central midfielder watched by three V.League clubs. He has impressive numbers: an average of seventy-two passes per match, a 91% accuracy rate. Those figures look as handsome as a business card. But when I coded his last ten matches, I found two things. First, most of those passes were sideways or backward. Second, and more seriously, he runs a lot but runs in the wrong places — his total distance was second-highest on the team, but his number of high-speed runs into space to receive the ball ranked third from bottom in the entire league. He moves to look busy, not to create an advantage.

This is the blind spot of GPS stats read without context. Distance says nothing if you do not know where someone runs. I have written before, and I hold the view: GPS does not show you the winner, it shows you the one willing to run one extra metre. A player who runs eleven kilometres but mostly drops back to receive safe passes is entirely different from one who runs nine kilometres but makes fourteen sprints into the danger zone. Both read as eleven kilometres on paper, but one helps the team win, the other helps his own stat sheet.

The code table helps me separate them. Code 18 — the vertical line-breaking pass — is only counted when the ball beats at least one pressing line toward the opponent's goal. Code 27 — movement to create space — is only counted when a player leaves his position to drag a defender away, opening room for a teammate. Code 44 — the run into space behind the defensive line — is counted separately. When I count these three codes, I see the player the stat sheet does not.

Among the central midfielders I watched in the V.League this season, three have total distances outside the league's top ten, yet their counts of Code 18 and Code 44 sit inside the top five. Those are the players who create real value. They are also the players with the cheapest transfer prices. This paradox is not accidental. It is the direct consequence of a scouting culture that reads goals instead of space.

I re-watched two hundred matches just to find one moment nobody saw. That moment is usually not a goal. It is the run that created the space for a goal — the run the camera does not follow and the commentator does not mention.

Now let us talk about the striker problem — the thing the transfer window is most obsessed with.

In this transfer window, V.League clubs are pouring money into finishers. That is a natural reflex: weak teams lack goals, strong teams want more. But the striker is the most mispriced position, because goals are an outcome metric that depends more on the surrounding system than on the scorer himself.

Imagine a striker who scores fifteen goals in a season. It sounds excellent. But if I tell you that eight of them came from situations where teammates had already created chances from under eleven metres, and he converted only two of twelve difficult chances, the picture changes. A good striker is not only someone who scores easy chances; he is someone who scores difficult ones, and who creates chances for others by stretching the defence.

The code table gives me three metrics that goals conceal. Code 05 — the run to stretch the defensive line before receiving the ball. Code 09 — the aerial duel in the opponent's half to hold the ball for the second line. Code 31 — pressing the opponent's centre-back when your team loses the ball. These three codes measure a striker's contribution to the system, not just to the scoreline.

In that July afternoon match, the striker the club wanted to buy scored twice. But he performed Code 31 — pressing after losing the ball — exactly twice in ninety minutes. The opposing striker, who scored nothing, performed Code 31 eleven times and Code 05 fourteen times. One is bought for two goals. The other is overlooked for scoring none. If I were a sporting director, I would pay more for the second — not because I dismiss goals, but because goals are something I can buy cheaper elsewhere.

This is where I want to pause, because there is a great temptation in every transfer window: buying a player based on his most recent match.

There is a phenomenon I call the panic premium. When a club loses three matches in a row, the coaching staff feels the pressure and the board wants an action to reassure the fans. That action is usually a contract — any contract — made in haste. The fee gets inflated because the selling side knows the buyer is desperate. I once witnessed a V.League deal where a club paid thirty percent above market value simply because they needed a name before the next round. That player played seven matches and lost his place.

The panic premium is the enemy of every long-term plan. It turns the transfer window from a squad-building exercise into a psychological reaction. And it explains why many expensive V.League signings fail — not because the players are poor, but because they were bought for the wrong need at the wrong time.

When I interviewed several V.League assistant coaches recently, one told me something I wrote down verbatim: "We are not short of good players. We are short of time to know who is good." Time is what the transfer window gives nobody. And because time is short, people buy on instinct — something I, after many mistakes, no longer trust absolutely.

So what is the right way?

I have built myself a four-layer analytical framework, and I use it for every player assessment: data, space, decision, person. The first layer is raw data — distance, passes, shots. The second is space — which spaces the player occupies and creates. The third is decisions — what he chooses in moments of pressure. The fourth is the person — whether he runs one extra metre when the match is already decided.

The first three layers can be measured with data. The fourth cannot. And the fourth is the most important.

That is why I never recommend buying a player before watching him play at least three full matches. Three, not one. One match can be an accident. Two can be luck. Three begins to reveal a pattern. The fourth onward only confirms or denies it.

In this transfer window, I produced a list of seven V.League players I consider undervalued. I will not name them here, because I have committed never to name a player whose pronunciation I have not verified and whom I have not watched in three full matches. But I can describe their profiles: three are central midfielders with a high Code 18 count but average distance, two are full-backs with a high overlapping count (Code 41) but unremarkable in attack, one is a striker with a high Code 31 but few goals, and one is a goalkeeper with a high long-pass accuracy rate — an ability of enormous importance in a counter-attacking style that is almost never factored into price negotiations.

Fans love the underdog because an upset story draws traffic. But I, who follow weak teams all year, know the price paid for every miracle. A bottom-of-the-table win over the leaders is not a miracle; it is the result of a well-prepared defensive system, a disciplined pressing plan, and three or four moments when a player dares to do what the analytical sheet did not predict. The media calls it a surprise. I call it mathematics not yet fully read.

Here I must speak about the part I once opposed but now must accept.

For years, I held a prejudice against transfers based on rotation models and fitness management by algorithm. I once thought it destroyed football's soul. But in a recent international season, watching a big club win after seven matches in sixteen days by rotating twenty-three players on machine-learning data, I had to rewrite my view. I once hated change, but I learned to respect it with data.

For the V.League, this lesson applies to the transfer window in a concrete way. A club competing on three fronts — the domestic league, the national cup, and the continental stage — cannot buy players just to start eleven men. They need a twenty-three-man squad that can substitute for one another without collapsing in quality. The transfer window is not a race to buy stars; it is a squad-depth optimisation problem.

Squad depth is the concept I value most in the transfer window. It is not the total number of signings, but the number of players at each position who can enter the pitch without degrading the system. When I analyse a club, I draw a table: how many acceptable players at each position. At most V.League clubs, I find severe imbalance — two positions with four players, three others with only one. When injury strikes, the system collapses not because the team is weak, but because its structure is fragile.

This is what I argue about with many in the industry. When a club boasts that it has three good strikers, I ask: how many of them can play in your system when the team has to defend? The V.League does not lack flashy attacking signings; it is empty at the transition-defence position — the position I consider pivotal.

Transition is the moment the match is decided. In my code table, codes 20 to 29 describe the entire transition chain: from losing the ball to reorganising the defence, and from winning the ball to counter-attacking. A team strong in transition will beat teams stronger in possession. That is mathematics, not inspiration.

I remember a coach once told me that football is a game of twenty-two people running and one ball, and the winner is the one who understands better why the ball goes where it goes. I agree. But I add: the winner is the one who understands better why people run where they run.

That is my entire scouting philosophy. Buy the right runner, not the frequent runner.

In this transfer window, I propose that V.League clubs apply three steps. First, code the last three matches of every target using a fixed system, not emotion. Second, measure transition contribution, not just attacking contribution. Third, and most importantly, examine the current squad structure before examining the individual player. A good signing for this team can be a disaster for another.

I know this proposal sounds dry. But after years of being corrected by data, after one mispronunciation that made me build a three-step verification process for every name, I believe dryness is a form of honesty. The code table does not need to remember; it remembers the one who created it. And I want that code table to remember even the players who never had a pre-cut clip.

There is a counter-intuitive angle I want to place on the table before I finish. People believe the transfer window is where big clubs win because they have money. That is true, but only in the short term. In the long term, the transfer window is where the club that reads data better wins — and at this point, small clubs hold an underrated advantage: they are forced to be precise, because they have no money to fix mistakes.

The blind spot of the V.League system lies here. Big clubs buy expensively to solve short-term problems and pay with bloated wage bills. Small clubs buy cheaply, and sometimes buy correctly, but then sell because they need money before the player matures. No one builds a system patient enough to keep and upgrade a player across three seasons. This is a bigger failure than any individual transfer mistake.

The truth is that most of the value in the transfer window lies not in whom you buy, but in whom you keep. A club that keeps the right players and develops young ones properly will not need to spend much in the transfer window. But keeping people is harder than buying people, because keeping requires long-term vision, and long-term vision draws no traffic.

I place the data on the table and let it plead its own case. No goal in that July afternoon match made me believe the club should buy that two-goal striker. No possession metric made me believe the away team was stronger. Only my code table said one thing: they bought a name, and forgot a system.

The transfer window will close, as every transfer window does. The signings will be announced, the photos taken, and the numbers presented like promises. I will sit in the technical room, open the tape, and count. Not counting goals. Counting the meters of running that will later decide who was right.

When the next round begins, notice one small thing. When a newly signed striker runs toward the opponent's goal in a counter-attack, watch the defender running after him. Do not watch the ball. Watch the space the two of them leave behind. That is where the match is truly written, and that is also where the next transfer window begins.

As for me, I will still be here, with my notebook and my code table, measuring three times before I speak. A match is a problem, and the code table is how I write the solution. I do not need anyone to agree with my solution. I only need it to be right.

But there is one thing I ask myself, looking at the numbers on the screen late at night: if a V.League club read this notebook and bought the right player that nobody saw, would we know to praise it, or would we still wait for the goals to arrive before calling it genius scouting?