Players: workload, role, and risk

Player-level intelligence for fantasy selectors: current role, recent workload, venue fit, matchup notes, and an explicit floor/upside assessment. Not scorecards — assessment.

What the players hub covers

Player pages are assessment, not scorecards. Each page covers the player's current role in the team, recent workload (overs bowled, batting position, finishing role), venue fit, matchup notes, and an explicit floor/upside assessment. The aim is for the selector to know, before locking the player, what they are actually buying.

How a player page is built

A player page opens with a role summary, then walks through the role logs for the last 5-6 matches. The logs are explicit: how many overs bowled, at what stage of the innings, what the batting position was, what the finishing role looked like. The logs are followed by a venue-fit table and a matchup-notes block, and the page ends with a floor/upside call.

Reading the role logs

Role logs are the most important section of a player page. The desk tracks four metrics across the last 5-6 matches: batting position (with finishing role flagged), overs bowled (with stage of innings flagged), field setting where relevant, and any rotation or rest. A consistent pattern across the sample is a settled role; a mixed pattern is a contested role.

Venue and matchup fit

A player's venue fit is not a generic 'good at this ground' note — it is anchored to a specific pattern of venue behaviour over a defined sample. We use the same conditions table the live desk uses, then ask whether the player's role profile benefits or suffers from that pattern.

Floor and upside assessment

Every player page ends with a floor and an upside call. The floor is the expected output if the conditions read is wrong and the role is contested. The upside is the expected output if the conditions read is right and the role is settled. The two numbers are not predictions — they are a defensible working range. Selectors who want to take the player should compare the floor to the credit slot they would be giving up.

Why we do not publish season averages

Season averages hide role shifts. A player with a high average but a contested role in the last two matches is a different fantasy proposition than a player with the same average and a settled role. The role logs make the pattern visible; the floor/upside call names the fantasy relevance. Readers who lean on season averages will consistently pick the player whose role has just shifted and miss the player whose role is settled but whose average is lower.

The desk's working rule is to read the role log before the average, the role log before the form line, and the role log before the credit slot. When all four converge, the player is a working pick. When they diverge, the player is on the watchlist.

Reading the floor and upside call

The floor and upside call on each player page is a defensible working range, not a prediction. The floor is the expected output if the conditions read is wrong and the role is contested. The upside is the expected output if the conditions read is right and the role is settled. The two numbers should bracket the realistic outcomes for the fixture.

Selectors who want to take the player should compare the floor to the credit slot they would be giving up. If the floor is acceptable for the credit, the player is a working pick. If the floor is below the credit slot's expectation, the player is a luxury pick — only justified if the upside case is strong enough.

Why role logs beat averages

A player with a season average of 45 but a contested role in the last two matches is a different proposition from a player with the same average and a settled role. The role logs make the pattern visible. The first player might have played three matches at number three and two matches at number six — the average is the same, the fantasy relevance is not.

Selectors who want to filter on role should read the role logs first, then the conditions table for the fixture, then the floor/upside call. The role logs anchor the read; the conditions table stress-tests it; the floor/upside call names the fantasy relevance.

Reading the conditions table

The conditions table on a player page lists the venue's last five completed fixtures in the same format, with the average powerplay run rate, the average death-over run rate, and the chasing-versus-defending record. The player's role fit is then mapped against that pattern — a powerplay anchor benefits from a flat surface with short square boundaries; a death-overs bowler benefits from a slow surface with heavy square boundaries.

The mapping is not a prediction; it is a working read. The player's actual output on the day depends on the specific conditions in the specific fixture, which can differ from the venue average. The mapping helps the selector decide whether the player is in or out for the fixture.

The role-shift note

The role-shift note on a player page is a short paragraph that names the most recent material change in the player's role and the fixture it happened in. A role shift is different from a role change — a shift is a discrete change in one match that has stuck; a change is a one-off and may revert. The desk tracks shifts because they have a higher probability of persisting.

If the role-shift note names a promotion up the order, the floor framework becomes more favourable for that player — the floor is now anchored to a higher batting position. If the note names a demotion in bowling overs, the ceiling framework becomes less favourable — the ceiling is now anchored to a smaller overs share. The desk's working rule is to read the role-shift note before reading the floor/upside call.

Frequently asked