Expected points explained

Past points tell you what a player did. Expected points tell you what he's likely to do next. In a game decided by the future, that's the number that should drive most of your decisions — and it's what our planner is built around.

This guide explains what expected points and expected minutes mean, and how to use them without being misled.

What expected points is

Expected points (xPts) is a forecast of how many Fantasy Premier League points a player will score in an upcoming Gameweek. It's a single number that rolls together everything from the scoring table:

how likely he is to play, and for how long;
his chance of scoring or assisting, given his role and his team's attacking strength;
his chance of a clean sheet and defensive-contribution points, given the fixture;
the smaller stuff — bonus, saves, cards.

Each of those is estimated, weighted by the fixture, and added up. A striker at home to a weak defence will show a high xPts because his goal probability is high that week; the same striker away at a top side the following week will show less. It's the fixture-aware, forward-looking version of "how good is this player right now".

Why minutes come first

The single most important input is expected minutes (xMins) — how long we think a player will actually be on the pitch.

It sounds mundane, but minutes are the multiplier on everything else. A player can't score, assist or keep a clean sheet from the bench. A brilliant forward who only plays 55 minutes loses the second appearance point and has less time to return. A rotation risk in a deep squad might start one week and sit the next, halving his real output regardless of talent.

So xMins does two jobs:

It scales the attacking and defensive estimates — more expected minutes, more expected return.
It flags risk. Two players with similar raw talent can have very different expected points purely because one is nailed on for 90 and the other isn't.

When our model doesn't yet have a confident minutes read on a player — early in a season, or a new signing — you'll see xMins shown as a dash rather than a guessed number. We'd rather show nothing than invent it.

How the planner uses it

Everywhere you see an expected-points figure in the hub, it's this same projection, re-based to the Gameweek you're looking at:

In the player pool, it's the default way to rank and compare players for the weeks ahead.
On a player's page, it drives the fixture-by-fixture outlook.
In the planner, it powers the "optimise" suggestions and the projected points for your team, so you can see how a transfer or a captain change moves your total before you commit.

The captaincy use is the most direct: over a season, captaining your highest expected-points player each week is a strong, low-effort baseline. You'll deviate for a Triple Captain ceiling play or a hunch, but xPts is the sensible default.

How to use it well — and its limits

Expected points is a guide, not gospel. A few habits keep you on the right side of it:

Think in runs, not single weeks. One Gameweek is noisy — a great player can blank, a cheap one can haul. The projection is most trustworthy summed over several weeks. That's why the planner lets you set a horizon.
Pair it with fixtures. xPts already accounts for the fixture, but eyeballing the difficulty grid helps you understand why a number is high or low.
Respect the dash. A missing xMins means genuine uncertainty — a differential punt, not a safe pick. Size your risk accordingly.
Don't chase decimals. A 0.1 difference between two players is noise. Use xPts to sort players into tiers, then let fixtures, price and your own read decide within a tier.

Used this way, expected points turns a wall of stats into a single, comparable ranking — and frees you to spend your thinking on the calls that are genuinely close. Start with the player pool sorted by xPts, then build a side in the planner.

What expected points is

how likely he is to play, and for how long;

his chance of scoring or assisting, given his role and his team's attacking strength;

his chance of a clean sheet and defensive-contribution points, given the fixture;

the smaller stuff — bonus, saves, cards.

Why minutes come first

The single most important input is expected minutes (xMins) — how long we think a player will actually be on the pitch.

So xMins does two jobs:

It scales the attacking and defensive estimates — more expected minutes, more expected return.

It flags risk. Two players with similar raw talent can have very different expected points purely because one is nailed on for 90 and the other isn't.

How the planner uses it

Everywhere you see an expected-points figure in the hub, it's this same projection, re-based to the Gameweek you're looking at:

In the player pool, it's the default way to rank and compare players for the weeks ahead.

On a player's page, it drives the fixture-by-fixture outlook.

In the planner, it powers the "optimise" suggestions and the projected points for your team, so you can see how a transfer or a captain change moves your total before you commit.

How to use it well — and its limits

Expected points is a guide, not gospel. A few habits keep you on the right side of it:

Think in runs, not single weeks. One Gameweek is noisy — a great player can blank, a cheap one can haul. The projection is most trustworthy summed over several weeks. That's why the planner lets you set a horizon.

Pair it with fixtures. xPts already accounts for the fixture, but eyeballing the difficulty grid helps you understand why a number is high or low.

Respect the dash. A missing xMins means genuine uncertainty — a differential punt, not a safe pick. Size your risk accordingly.

Don't chase decimals. A 0.1 difference between two players is noise. Use xPts to sort players into tiers, then let fixtures, price and your own read decide within a tier.