That is how I use the FPL Demon Expected Points page. I open the board before deadline, scan the next run of gameweeks, then use the filters to find players who fit the problem I am actually trying to solve.
The page is not just a list of names. It is the starting point for my whole week: I find the player pool on Expected Points, check the detail in the player breakdown, compare the shortlist, then bring the best names back into the Planner, Good Pick and Draft Compare.
My First Rule: Do Not Treat xPts Like A Prediction
Expected points is not a promise. It is a way of asking: if I had to judge this player from fixtures, minutes, role and scoring routes, what would I expect before the match starts?
That matters because FPL managers are emotional. We overreact to last week's goal, a clip on social media, or one fixture that looks easy. xPts gives me a calmer starting point.
| Question | Why it matters | What I check |
|---|---|---|
| Who projects best this week? | Sometimes I only need a short-term transfer or captain read. | I sort the next GW column. |
| Who has the best run? | A transfer should usually survive more than one deadline. | I look across GW1-GW10 and the Total column. |
| Who is good value? | A cheaper player with strong xPts can unlock a better squad. | I compare price, xPts and value in the breakdown/shortlist. |
| Who has haul upside? | Mini-leagues are won by catching spikes, not only safe returns. | I open the breakdown and check haul, floor and ceiling. |
| Who is a minutes trap? | A great per-minute player can still be a bad FPL pick if he does not play. | I check xMins and edit my assumption if I disagree. |
Step 1: Start With The Full Board, Not One Player
When I open Expected Points, I try not to search for one name straight away. I start with the board. The reason is simple: if I only search the player I already like, I am not really using the tool. I am just looking for confirmation.
The board shows every player across the gameweek run. I can see the expected points for each GW, the total across the horizon and the minutes assumption underneath the number. That small xMins number is important. A 6.5 xPts player at 88 minutes is a very different pick from a 6.5 xPts player at 55 minutes.
I use the Total column when I am judging a player I might hold. I use the single GW columns when I am planning a one-week move, a captaincy decision or a chip week.
Step 2: Use Filters To Make The Board Answer One Question
The worst way to use a big table is to stare at it and hope the answer appears. I always filter it down to the decision I am making.
If I need a defender, I filter defenders. If I have 6.0m, I use the price filter. If I only want players from teams I trust, I use the team filter. If I want a differential, I look at ownership. If I want reliable starters, I pay attention to xMins.
| Filter | How I use it | Example decision |
|---|---|---|
| Search | I use it after I already understand the player pool. | Check one player quickly, then compare him against the board. |
| Position | I filter by GK, DEF, MID or FWD when I know the squad slot. | Find the best defender replacement under my budget. |
| Team | I use it to inspect a club run or avoid overloading one side. | Compare Arsenal defenders, Liverpool attackers or promoted-team punts. |
| Price | I set the budget before I fall in love with a player I cannot afford. | Find the best midfielder at 7.5m or below. |
| Ownership | I use it when I want to see template picks or lower-owned alternatives. | Check whether a differential actually projects well. |
| Minutes | I use it to separate starters from rotation names. | Avoid a high-upside attacker who is only projected for short minutes. |
| Sort | I sort by the gameweek or total that matches my plan. | GW1 for a punt, Total for a longer hold. |
Step 3: Click Any xPts Cell For The Gameweek Breakdown
This is the part I use the most. I do not just look at a player's total and move on. I click the xPts number for the gameweek I care about.
If I click Haaland in GW6, I want the GW6 breakdown, not a generic player profile. The breakdown shows where the projection is coming from: appearance, goals, assists, clean sheet points where relevant, saves for goalkeepers, bonus, DefCon and deductions.
That helps me understand the type of pick. A forward with most of his projection coming from goals is a different risk from a defender with clean-sheet route, appearance points and DefCon. A goalkeeper with save volume can be useful even when the clean sheet is not perfect.
- Appearance tells me whether the model expects real minutes.
- Goals and assists show the attacking route.
- Clean sheet and saves matter for defenders and goalkeepers.
- Bonus helps me spot players who can turn returns into bigger scores.
- DefCon matters because some defenders can score without attacking returns.
- Deductions remind me that cards and own goals are part of the projection too.
Step 4: Read The Projection Profile Under The Breakdown
After the points breakdown, I scroll to the Projection Profile. This is where I check the shape of the outcome, not just the average.
The profile gives me blank percentage, return percentage, haul percentage, floor and ceiling. That is huge for captaincy, punts and chip weeks.
| Metric | What it means to me | How I use it |
|---|---|---|
| Blank % | How often the player gives me little or nothing. | I avoid high blank risk when I need safety. |
| Return % | How often the player gets a useful score. | Good for steady transfers and captain shortlists. |
| Haul % | How often the player can spike. | Important for captaincy, differentials and upside picks. |
| Floor | The bad-but-realistic outcome. | Useful when I cannot afford a disaster. |
| Ceiling | The upside outcome. | Useful when chasing rank or planning a chip. |
This is why I do not only sort by total xPts. Two players can both project for 6.0, but one might be safer while the other has the bigger haul chance. Depending on my team, I might want either one.
Step 5: Use Player Profiles When You Need More Context
The Expected Points board gives me the shortlist. The player profile gives me context. If I am serious about a pick, I open the profile and look at the wider player story: price, ownership, position, team, minutes and the stats that explain the projection.
For defenders, I care about clean sheets, defensive contribution route and whether there is any attacking threat. For midfielders, I care about xG, xA and how much of the projection depends on minutes. For forwards, I care about goal threat and whether the fixture run gives captaincy upside.
That is where the board becomes more than a spreadsheet. I am not just asking who has the highest number. I am asking whether I believe the route behind the number.
Step 6: Compare Players Before You Bring Them Into The Planner
Once I have two or three names, I compare them properly. I do not want to make transfers from memory. I want to see the next run, price, ownership, xMins and scoring route side by side.
This is especially useful when the popular pick is not obviously the best pick. Sometimes the template player has higher ownership but weaker value. Sometimes the cheaper alternative loses one week but wins the next five. Sometimes the expensive player is worth it because he gives captaincy security.
| Comparison | What I am trying to learn |
|---|---|
| xPts by GW | Which player wins the exact week I am buying for. |
| Total xPts | Who wins over the hold period. |
| xMins | Who has the safer route to starts. |
| Price | Whether the extra money is buying enough points. |
| Ownership | Whether I am taking template safety or differential risk. |
| Breakdown | Whether the points come from goals, assists, clean sheets, saves, bonus or DefCon. |
Step 7: Edit xMins When My Information Is Better
This is one of the most powerful parts of FPL Demon for me. If I disagree with the minutes, I can edit the xMins assumption.
Maybe a player has just become first choice because of an injury. Maybe a winger is a rotation risk after Europe. Maybe a striker is coming back from injury and I only expect 60 minutes. I change the minutes and the expected points adjusts.
The best bit is that the xMins assumption syncs with the rest of the tools in the session. If I change a player's minutes on Expected Points, I can use that assumption when I go into the Planner, Good Pick and Draft Compare. That makes the workflow feel connected rather than random.
- Raise xMins when a player looks more nailed than the default.
- Lower xMins when I think a player is a rotation risk.
- Test one specific gameweek instead of changing the whole player opinion.
- Use the updated xPts in the Planner before saving a draft.
Step 8: Bring The Shortlist Into The Planner
Expected Points is where I find players. The Planner is where I decide whether they fit my team.
A player can look brilliant on the board and still be awkward in my squad. He might block a future transfer, use too much budget, create a benching problem or leave me short of a captain in GW3. That is why I take the shortlist back into the Planner.
In the Planner, I put the player into the actual team, flip through the gameweeks, check the bank, check captaincy and see how the route feels. If I am unsure, I click the player and ask Good Pick.
Step 9: Use Good Pick For The Awkward Calls
When I have a player in the Planner and I still do not fully trust the move, I use Good Pick. That is the bridge between the board and the decision.
Expected Points tells me who projects well. Good Pick tells me whether that player makes sense from the gameweek, budget, value, xMins, fixtures and alternatives. It is useful because it forces the comparison I might avoid if I already like the player.
If Good Pick says an alternative is close or stronger, I go back to the board and check the profile. Then I return to the Planner and test the transfer properly.
Step 10: Save Routes And Compare Drafts
Once I have a serious route, I save the draft. Then I build the alternative and use Draft Compare.
This is where Expected Points becomes part of a proper planning process. I might find a cheaper defender on xPts, test him with Good Pick, build a new draft around the saving, then compare that route against my original draft.
Draft Compare tells me whether the new structure actually wins across gameweeks, captains, chips, transfers and xMins. Expected Points starts the question. Draft Compare finishes it.
| Tool | My job for it |
|---|---|
| Expected Points | Find the strongest player pool and inspect exact GW breakdowns. |
| Player profiles | Understand why the projection exists. |
| Planner | Test whether the player fits my squad and route. |
| Good Pick | Check the awkward player decision against alternatives. |
| Draft Compare | Choose between two saved routes before deadline. |
My Expected Points Routine
- I open Expected Points before I touch transfers.
- I filter by the position and price range I need.
- I sort by the gameweek or total that matches my plan.
- I click the xPts cell for the exact GW I care about.
- I read the points breakdown and projection profile.
- I open player profiles for the names I am seriously considering.
- I edit xMins if I disagree with the default minutes.
- I bring the shortlist into the Planner.
- I use Good Pick on the awkward calls.
- I save routes and use Draft Compare before deadline.
That is how I use the Expected Points page as a top-10k manager. I do not use it to outsource the decision. I use it to make sure I have checked the right things before I make the decision.
The edge is not just seeing who has the biggest number. The edge is understanding why the number is there, whether the minutes are right, whether the player fits your squad and whether the route still works after the next deadline.
