Football Manager Data Insights: What They Are and How to Turn Them into Transfer and Squad Decisions

Football Manager data insights are the step between raw numbers and a decision: you take player attributes, match statistics, role suitability and development trends, interpret them against your tactic and budget, and end up with a defensible choice about who to buy, sell or start. They are useful when you have a specific question (e.g., "who covers my left-sided pressing role if my starter is injured?") and a way to check the answer against scouting and finances. They are not useful as a single score that "proves" a player is good.

What counts as a data insight in FM

FM gives you several layers of information. Keeping them separate stops you from treating one number as the whole picture.

An insight is a claim you can act on, such as "this 21-year-old is a cheaper, younger alternative for my backup striker role, and his output per 90 is close enough to justify the drop in finishing." A raw number is just an input to that claim.

Turning insights into transfer decisions

Work from the role outward, not from the best-rated player inward.

1. Define the role first. Write down what the position must do in your tactic — for example, a defensive midfielder who covers ground, wins the ball and plays simple passes under pressure. This becomes your filter.
2. Set hard constraints. Budget, wage room, age range, squad status and homegrown or registration rules. These eliminate candidates before you compare quality.
3. Shortlist by role fit. Use attributes and role suitability to cut the list, then check match statistics for players who actually get minutes. A player with strong attributes but no recent playing time is a question mark, not a bargain.
4. Compare candidates on the same dimensions. Put two or three shortlisted players side by side on the attributes your role needs, output per 90 minutes, age and cost. If one wins on everything, the decision is easy; if not, decide which trade-off your squad can absorb.
5. Verify with scouting and context. Scout reports, personality, injury history and the level the player has performed at are the check on your data read. Data tells you what a player has done; scouting tells you whether it will transfer to your league and dressing room.
6. Record the hypothesis. Before you sign, note in one line why: "Bought as rotation for the left pressing role; expected to cover 15–20 starts." This is what makes later review possible.

A worked example

Suppose your first-choice left winger is injured for two months and you have a limited budget. You filter for wingers aged 20–26 whose attributes fit an inside-forward duty, then compare three candidates on goals and assists per 90, minutes played, age and price. One has the best output but has played only a handful of matches; another has solid output over a full season at a lower level; the third is expensive and only marginally better. The insight is not "sign the best numbers" — it is "the full-season performer at the lower level is the lowest-risk cover for a short-term gap, and the small-sample player is worth scouting for next season." That is a decision the data supports without overclaiming.

Using insights for squad decisions

The same logic applies inside your own squad, where you have more data and fewer unknowns.

• Rotation and minutes: compare output per 90 rather than totals, so a substitute with limited minutes is judged fairly against a starter.
• Role补强 (role reinforcement): identify the attribute your system depends on most and check whether the backup drops off sharply there. A small drop in finishing is tolerable; a large drop in work rate may break the press.
• Sell decisions: a player whose value is rising but whose minutes are blocked is a candidate to sell, provided the replacement is already identified and affordable.
• Overfitting check: a hot streak over five matches is not a trend. Ask whether the underlying numbers (shots, chances created, defensive actions) support the output, or whether the player is converting an unsustainable share of chances.

Common pitfalls

• Treating one rating as a verdict. Average rating depends on team performance and role; use it as a signal, not a ranking.
• Ignoring sample size. Ten matches of excellent output is a lead to scout, not proof.
• Forgetting the tactic. A player who is excellent in one system can be average in yours; the role definition is what makes the comparison meaningful.
• Skipping the budget check. The best data insight is useless if the wages break your structure or the fee leaves no room for the other gap in your squad.
• Not reviewing. After a window, compare what you expected with what happened. That feedback loop is where data insights actually improve.

Quick checklist before you act

• The role and its key attributes are written down.
• Budget, age and registration constraints are applied first.
• Candidates are compared on the same dimensions, using per-90 numbers where minutes differ.
• Scouting and injury history confirm the data read.
• The decision and its expected outcome are recorded for later review.

Used this way, Football Manager data insights are a discipline rather than a shortcut: they narrow the field, expose trade-offs and make your transfer and squad calls explainable — to yourself, after the season, when it matters.