Dugout Explained

How FPL Dugout's Decision Engine Evaluates Transfers and HOLDs

· FPL Dugout · Educational guide

Fantasy football transfer dashboard with player cards, pitch board and analytics arrows

A player ranking asks who looks attractive. A useful fantasy decision asks something harder: does changing your actual squad improve the outcome enough to justify the cost and uncertainty?

Dugout is built around that distinction. Its ledger-first recommendation design uses projections as evidence, considers which moves are legal in your format and compares the value of acting against keeping what you have. This guide explains what those concepts mean, why a good player may not be a good transfer, and why a HOLD result is a legitimate output.

The first filter: can the move actually happen?

An exciting replacement is pointless if the move is not eligible. Eligibility differs by format.

Classic FPL: a transfer must replace a player with another in the same official position, remain within spending power, preserve the limit of three players from one Premier League club and respect the game's squad rules. Transfers beyond your allowance normally cost four points each. The starting squad consists of two goalkeepers, five defenders, five midfielders and three forwards.

Official FPL Draft: a player owned by another manager is not a waiver target. The available player pool and claim procedure matter, while there are no player prices or Classic-style transfer hits. Players belonging to other managers may be potential trade targets only if the league's trade rules permit.

Fantrax: roles, formation and scoring can be configured by each league. A valid suggestion depends on verified roster and scoring context, not assumed Classic rules.

The same player swap can therefore be legal in Classic, impossible on a Draft waiver wire and only conditionally possible in Fantrax.

The second filter: use one consistent projection foundation

Dugout's player expected-points estimates (xPts) are used across its Team, Decisions, Player Compare and Projections experiences. A comparison is most meaningful when outgoing and incoming players use the same data snapshot, scoring system and horizon.

A next-Gameweek expected-points difference and a six-Gameweek total answer different questions. The first may help with captaincy and a short-term emergency. The second can capture value lost by selling a player just before a favourable fixture run. Projections should also reflect expected minutes, availability and the limitations of the current data.

Dugout's research and development included a newer candidate xPts model undergoing additional calibration. A model in evaluation should not be described as the live authoritative model until it is deliberately promoted. The current article describes the production recommendation architecture, not a claim that every experimental projection has been adopted.

The decision ledger and NetGain

In the ledger-first design, the system creates an eligible shortlist, evaluates each plausible move and records evidence that contributes to the decision. The result is intended to reflect NetGain — the expected advantage of making a move after relevant costs and risks rather than merely the difference between two players' headline xPts.

Key considerations can include the incoming player's projected opportunity, the outgoing player's future value, whether a hit is required, availability confidence and the practical difficulty of recovering an asset in Draft. Different formats and decision types require different cost terms.

Worked example: a tempting transfer that is not worth a hit

Entirely illustrative numbers, not generated by the live Dugout model.

AssumptionValue
Incoming midfielder, next three GWs18 xPts
Outgoing midfielder, next three GWs15 xPts
Headline improvement+3 xPts
Extra Classic transfer required−4 points
Simple post-hit gain−1 point

The incoming player looks more attractive, yet the immediate arithmetic does not justify an extra paid transfer. Additional uncertainty or the value of preserving a better medium-term route can further weaken the move. A sensible recommendation may be HOLD, bank a transfer or MONITOR for new information.

Now suppose the incoming player projects six points better over the relevant horizon, the move is legal and one free transfer is available. The case becomes stronger — although probability of minutes, opportunity cost and the rest of the squad still matter. These calculations illustrate the concept and are not the literal full formula used internally by Dugout.

What does retention value mean?

A star player's future value can exceed his next fixture. If you sell him before a favourable run, you may need another transfer to regain him. In Draft, an established premium is scarce: releasing him may allow a rival to acquire him, making recovery impossible without a trade. Retention value helps prevent the engine from turning every one-week fixture swing into a churn recommendation.

This also explains a question managers ask frequently: “Why recommend HOLD when there is a better-projected free agent?” The one-week replacement may score slightly more but be less useful across the chosen horizon or expose your roster to a disproportionate drop risk.

ACT, HOLD and MONITOR are different answers

ACT means the evidence supports an eligible improvement under the current assumptions; it does not mean a player is guaranteed to score.

HOLD means the available move does not clear the decision bar. This can be the highest-value choice when replacing an injured or out-of-form player is too expensive or too weak.

MONITOR means the situation could change as injury status, likely minutes, fixtures or verified availability evolves. It is a prompt to revisit, not a hidden transfer recommendation.

Importantly, an “Urgent Issue” or “Concern” should describe a supported squad risk and not bypass the decision ledger to invent a conflicting transfer. The Team page's risk signals and decision cards are intended to support the same underlying judgement.

A separate metric: the Gameweek Points Forecast

On the Team page, Dugout's newer Gameweek Points Forecast compares two values using two coloured bands, not two needles: projected points for the current team's best supported lineup and projected points for a feasible simulation of actionable Dugout Decisions.

This comparison uses the next Gameweek's lineup projection, not the ledger's multi-week NetGain number. In Classic, known hit costs are deducted from the simulated comparison. If free-transfer information is missing, the simulation can limit itself rather than assume free moves. In Draft and Fantrax, potential additions are conditional on being acquired; they are not guaranteed points.

If no feasible actionable changes exist, both forecasts may match. That can be a sign the current team is already the best supported option under the model, not a product failure. If a reliable fixture or projection is unavailable, Dugout may suppress the comparison.

How to audit a recommendation yourself

  1. Confirm the selected format, current squad and team data are correct.
  2. Verify the eligible incoming player: correct FPL position and affordability, or real Draft/Fantrax availability.
  3. Read the horizon, expected gain, risk and confidence, not just the headline name.
  4. Compare ACT with HOLD. Ask what you would lose by selling and whether the gain survives any hit.
  5. Check official injury news and the relevant Gameweek deadline.
  6. Review what happened later without confusing a good process with a guaranteed one-week result.

Dugout records decision evidence for analysis and calibration; that process is designed to judge recommendation quality over time instead of reacting to one unlucky return. The model can be wrong, and a correct forecast can still produce a blank due to chance.

Frequently asked questions

Is NetGain the same as incoming xPts minus outgoing xPts?

No. That is a useful starting comparison, but NetGain is designed to account for costs, risks, retention and eligibility over the relevant horizon.

Does Dugout always recommend a transfer when a player is injured?

No. It may highlight the injury but favour HOLD or MONITOR if all affordable or available alternatives have poor net value.

Does the Gameweek Forecast use six-week NetGain?

No. It uses a next-Gameweek lineup simulation of feasible Decisions. The two numbers answer different questions.

Can Draft recommendations include players owned by another manager?

They should not appear as actionable free-agent additions. An owned player might be considered a separate trade target, subject to league trade rules. Check actual league ownership before making a claim.

Will Dugout perform the transfer?

No. Dugout is read-only. You must make changes on the official fantasy platform.

Bottom line

Good fantasy advice is not a list of exciting names. It is a reasoned comparison of the squad you have, the squad you could have and the cost of getting there. A confident HOLD is often more useful than a forced transfer.

Explore: Decisions · Team Analyser · Projections · Pricing and access

Related reading: Minutes Risk · Transfer Planning · Six-Gameweek Projections

Official rules: FPL transfers · FPL Draft explanation

Editorial note: This is a public-facing explanation of the recommendation approach, not a disclosure of proprietary coefficient values or a guarantee of performance. Live eligibility and experimental feature deployment may change.