"My team is better than his" is not a strategy. It is a feeling, and feelings do not win FPL mini-leagues or head-to-head battles. The actual work of beating a specific rival — a colleague, a sibling, the person you have genuine bragging rights riding on — requires understanding precisely where your two squads diverge, what that divergence means for your relative points trajectory, and what to do about it. This is a step-by-step framework for running that comparison properly, whether you are doing it manually or using a dedicated tool to do the heavy lifting.
Why a Vague Sense of "Who's Better" Isn't Useful
Two squads with similar overall quality can have wildly different relative-movement dynamics depending purely on where their differences sit. If you and your rival share 12 of your 15 players, your points totals will move together most weeks — the battle is entirely decided by the 3 slots where you differ. A squad comparison that just totals up "my team's expected points" versus "his team's expected points" misses this completely. What actually matters is the differential slots, not the shared ones.
This is the same underlying logic covered in our template vs differential guide, applied specifically to a one-on-one comparison rather than the gamewide field. Shared players are strategically irrelevant to the head-to-head outcome. Only the differences matter.
Step 1: Identify the Shared Core
Start by listing every player you and your rival both own. This is your shared core — mathematically irrelevant to your relative outcome, because whatever they score, you both score equally from that slot. Do not spend analytical energy here. The temptation is to review your whole squad top to bottom, but the shared core is the one part of the comparison that tells you nothing about who will win.
Step 2: Isolate the Differential Slots
Everything that matters lives in the players you own that they do not, and the players they own that you do not. List these two groups separately. This is your actual battlefield — typically 3 to 6 slots out of 15, depending on how similar your squads are.
For each of your unique players, note their recent expected points, upcoming fixture quality, and rotation risk. Do the same for each of their unique players — you will need to estimate this from public data since you do not have inside knowledge of their reasoning, but recent form, price trend, and fixture run are all visible signals.
Step 3: Compare Captaincy Specifically
Captaincy deserves its own dedicated comparison step because of the doubling effect. If you and your rival share the same captain, this slot is also mathematically neutral to your head-to-head battle regardless of how good or bad the pick turns out to be. If you captain differently, this single decision is disproportionately powerful — a captaincy divergence is worth twice the swing of a normal ownership divergence, because of the multiplier.
Apply the full captaincy framework from our captaincy decision guide specifically to this comparison: whose captain has the stronger expected points case this week, and critically, whose captain choice is the "safer" pick that tracks the wider field versus whose is the differential. If you are behind your rival and considering a captaincy swing to catch up, the effective ownership concept applies here too — but scoped to just the two of you, not the whole game.
Step 4: Weight by Fixture Timing, Not Just This Week
A single-gameweek comparison is useful but incomplete. The differential slots you identified in Step 2 should also be evaluated across the next 3 to 4 gameweeks, not just the immediate one — because a transfer or captaincy decision you make today plays out over the following weeks, not in isolation. A rival's unique player with a brutal upcoming fixture run is a smaller ongoing threat than one entering a favourable run, even if their most recent single-gameweek score looks similar.
Step 5: Translate the Comparison Into a Decision
The whole point of running this comparison is to produce an actual decision, not just an interesting spreadsheet. Once you have isolated the differential slots and weighted them by near-term fixtures, ask three questions: Is there a transfer that would neutralise a threat from one of their unique players by bringing in a comparable or better option? Is there a captaincy change that would either extend your lead or start closing their gap, based on the doubled-impact analysis from Step 3? And critically — given your specific gap and the gameweeks remaining, should your posture be defensive (mirror their strongest unique asset to neutralise it) or aggressive (find your own unique differentiator to create separation)? This last question connects directly to the chasing-versus-defending logic covered in our mini-league strategy guide, applied here to a single specific rival rather than a whole league table.
Doing This Manually vs Automatically
Running this five-step process manually for one rival, once, is manageable — maybe 20 minutes with both team pages open side by side. Doing it consistently, every week, for your most important rival (or several rivals in a mini-league) is where almost everyone stops bothering, simply because of the time cost. That is exactly the gap a dedicated comparison tool closes.
FPL Oracle's Squad Comparison tool runs this exact framework automatically in Manager Comparison mode — enter your rival's team ID (see our guide to finding an FPL team ID if you need to locate it) and Oracle surfaces the shared core, the differential slots, the captaincy comparison, and the near-term fixture weighting automatically, refreshed every gameweek.
Comparing two FPL squads is not about who has the better team overall. It is about isolating the small number of slots where the two squads actually differ, because that is the only place the outcome between you is actually decided. Everything else is noise you both share equally.
The Oracle Takeaway
A genuinely useful squad comparison ignores the players you share with your rival entirely and focuses analytical effort exclusively on the differential slots and the captaincy choice — because those are the only places the head-to-head outcome is actually determined. Weighting those differences by near-term fixtures, not just the current gameweek, turns the comparison into an actual forward-looking decision rather than a backward-looking scoreboard read.
Three actions to take right now: pick your most important rival — the one you actually care about beating — and list out your shared core versus your differential slots. Check specifically whether you share a captain or diverge, since that single decision carries double weight. And use that comparison to make one concrete decision this week, whether that is a transfer, a captaincy change, or a deliberate choice to hold and let a favourable fixture run play out.
Run a full comparison against any rival with FPL Oracle — enter their team ID and get the shared core, differential slots, and captaincy analysis automatically, without the 20 minutes of manual cross-referencing.
Who's the one FPL rival you'd most want a head-to-head breakdown against right now? 👇