FPL Transfer Planner: How to Plan Transfers Across Multiple Gameweeks

I built FPL Copilot's transfer solver because I kept taking hits I didn't need to. The solver plans transfers across multiple gameweeks and finds the path that maximises expected points after accounting for hits.

After watching hundreds of squads go through it, the same lessons keep coming up.

Why Multi-GW Planning Wins

The FPL transfer planner looks 5 gameweeks ahead because that's where the biggest gains are. You can see fixture swings coming and prepare for blanks, doubles, and form changes before they happen.

Every -4 hit needs to earn back 4+ points just to break even. When I look at the solver output, most knee-jerk transfers don't clear that bar over 3 GWs. The player you panic-buy often returns less than the player you already had.

What I Learned Building the Solver

Staggering beats bulk. The solver rarely recommends making 3 transfers in one week. It spreads moves across gameweeks to avoid hits and keep flexibility. Two free transfers in hand is worth more than a marginal upgrade now.

Cumulative xPts matter more than this week. The solver compares total expected points across the full planning horizon. A player with 4.5 xPts this week but 2.1 next week loses to one with 3.8 + 4.2. Fixture runs matter more than any single GW.

The best transfer is often no transfer. If your squad is set for the next 3 GWs, banking the FT is the optimal move. The solver recommends "roll" more often than most managers expect.

When the Solver Takes Hits

The optimizer does take hits when the math is clear. Before a Wildcard (you're resetting anyway), when a premium is out long-term, or when the expected gain over the planning window clearly exceeds the -4 cost. It's not anti-hit. It's anti-bad-hit.

Creator's Tip

After the solver gives you a transfer path, use the pitch view to cycle through each gameweek. You'll see the exact lineup and xPts for every GW in your plan. If a specific week looks weak, ask the Copilot chat about it - it can explain why the solver chose that path and suggest alternatives.