Squad updates, likely XI, and last-minute changes
Per-match squad updates for the next fixture window. Each row carries a data-provenance note so the reader can tell which item is confirmed, which is reported, and which is speculative.
Next fixture window
| Team | Player | Status | Source |
|---|---|---|---|
| Team A | Top-order anchor | Likely XI | Pre-match press note, 2026-08-17 |
| Team A | Seam-bowling all-rounder | Hamstring, late fitness test | Pre-match press note, 2026-08-17 |
| Team B | Lead wrist-spinner | Likely XI | Pre-match press note, 2026-08-17 |
| Team B | Finisher | Rotation risk (3-format schedule) | Reported, 2026-08-16 |
How the desk sources each row
- Pre-match press note: the team's own media release, typically 24 hours before the toss.
- Pre-match press conference: the captain's or coach's media briefing, typically 12 hours before the toss.
- Reported: carried by a credible outlet but not confirmed by the team. Treat as speculative until confirmed.
- Speculative: based on form and rotation patterns only. Not a confirmation; treat as low confidence.
What to do before lock
Read the latest press note 30 minutes before the toss
The press note can move a player from Likely XI to Hamstring or vice versa.
Update your XI under 100 credits
A late change can drop a player below the XI threshold; swap to the next-best in-role alternative.
Lock the team before the toss
Late changes are not possible after the toss lands.
Related pages
- /pitch-report/: pitch type and weather for the same window.
- /player-stats/: credit, form, and likely XI for the squad.
- /captain-picks/: apply the 50/30/20 weight to the confirmed XI.
- : the writers's dated update feed.
How the data-provenance note is the only durable marker
Team news on this product is a squad-level feed: likely XI, injury status, last-minute changes, and the data-provenance note per item. The provenance note is the only durable marker; the items themselves shift between fixtures and between squads. The reader should treat the items as snapshots at the verification timestamp and the provenance note as the source pointer.
Likely XI is the squad-availability input. A player listed as Likely is in the named squad for the next fixture; Doubtful means in the squad but may not play; Out means not in the squad. The status updates on the day of the fixture; the table reflects the latest status at the verification timestamp.
Injury status is the squad-availability input for medical reasons. A player listed as Injured is in the squad but unavailable for selection; a player listed as Recovering may return for the next fixture. The injury status comes from the squad's official media release; the writers mirrors the release with the timestamp.
Last-minute changes are the squad-availability input for tactical reasons. A player listed as Rested is being rotated; a player listed as Tactical Substitution is being replaced for matchup reasons. Last-minute changes happen within 24 hours of the fixture; the desk updates the table as the changes surface.
Data-provenance note: each item on this guide is followed by a one-line source pointer (the squad media release, the operator's app, the curator's pitch report). The source pointer is the canonical record; the item is a snapshot at the timestamp. If a source updates, the desk updates the table to mirror the source.
What remains stable across team news: the four status categories (Likely, Doubtful, Out, Injured), the data-provenance note per item, and the verification timestamp. The status of individual players shifts between fixtures; the framework does not.
Editorial methodology for the squad-updates desk
The team-news hub is a per-match squad update page. The desk publishes a likely XI and an injury status for the upcoming fixture, with a verification timestamp on every record. The methodology is the same as every other page on myteam11play.com: name the source, name the verification timestamp, and do not invent a number.
For likely XI, the source is the in-app transmission of the squad-list status (Confirmed, Likely, Doubtful), combined with the named broadcaster's pre-match note. The in-app status is the canonical reference; the broadcaster note is a sanity check. If the two sources disagree, the in-app status wins and the guide notes the disagreement.
For injury status, the source is the franchise's or board's official announcement, plus the in-app Help tab if the player has a formal update. Rumour-based injury reports are not published. The desk does not paraphrase social-media updates from unverified accounts.
For last-minute changes (a toss-time swap, a replacement player), the source is the in-app squad list once the toss concludes. The guide is updated when the in-app squad list changes; the prediction is replaced with the verification.
For fantasy impact, the source is the in-app credit value of the named player plus the player-stats reference on /player-stats/. The desk does not hand-craft a "this player is a must-pick" line; the impact is a credit-value-plus-recent-form calculation, and the guide links to the source rather than restating it.
For what to watch next, the source is the in-app schedule's next fixture plus the named broadcaster's preview. The desk does not predict a winner; the desk flags the names worth watching and the inputs that move the captain-pick decision.
Update cadence: this guide is reviewed on the day of every match in the fixture window, and twice on match day (pre-toss and post-toss). The review date is in the footer of every page in this guide.
What this desk does not publish
The team-news hub does not publish a rumour-based injury report, does not publish a social-media update from an unverified account, and does not publish a "will play / will not play" projection before the in-app squad list confirms. The desk ranks zero players. The desk predicts zero matches. The desk publishes references the reader can reproduce in the in-app squad list.
The desk does not publish a likely-XI status that the in-app squad list does not surface. The desk does not publish a player impact claim that the in-app credit value does not support. The desk does not publish a "must-pick" line that the in-app player picker cannot produce.
The desk's role is the editorial coverage. The franchise's role is the operational coverage. The two roles are separate; the desk does not overlap with the franchise's official squad announcement, the broadcaster's pre-match note, or the in-app live scoring. The desk waits for the in-app squad list to update.
How to verify the squad update yourself
Open the myteam11 app and navigate to the squad list. The squad list should show the confirmed, likely, or doubtful status for each player. Compare the squad list with the squad update below; the squad list should match the editorial team's reading.
For the likely-XI, the in-app squad list should show eleven players per team. The likely-XI below should match the in-app squad list. The reader can verify the likely-XI inside the in-app squad list.
For the injury status, the in-app squad list should show a confirmed, likely, or doubtful flag. The injury status below should match the in-app squad list. The reader can verify the injury status inside the in-app squad list.
For the last-minute changes, the in-app squad list should be updated after the toss. The last-minute change below should be the change recorded in the in-app squad list. The reader can verify the last-minute change inside the in-app squad list.
For the fantasy impact, the in-app player picker should show the credit value and the recent-form average for the impacted player. The fantasy impact below should be the credit value plus the recent-form average. The reader can verify the fantasy impact inside the in-app player picker.
For what to do if the in-app squad list contradicts the guide's squad update, the answer is the in-app squad list is the canonical reference. The guide is updated next time the editorial team reviews the squad update; the reader can verify the squad update inside the in-app squad list at any time.