Bangladesh face T20 World Cup exit after ICC rejects venue shift request, sets 21 January 2026 replacement path

What the ICC board actually decided on 21 January 2026

The headline from the ICC board meeting on Wednesday 21 January 2026 was that the Men's T20 World Cup would proceed as scheduled, with Bangladesh's group matches to be played in India. The board also told the BCB to convey to the Bangladesh government that failure to travel would result in Bangladesh being replaced at the tournament, a position backed by a majority vote at the board meeting. The board further warned that changing the venue absent a credible security threat would "jeopardise the sanctity of future ICC events and undermine its neutrality as a global governing body," a line the ICC has rarely used in writing on a venue dispute.

The board was working from independent security reviews submitted to it ahead of the vote. Those reviews found no credible threat to Bangladesh players, media, officials or fans at any tournament venue in India. The BCB was given one additional day to confirm its final stance on playing matches in India. That 24-hour window — the practical deadline the Bangladesh government had to overrule the BCB — is the most consequential single data point in the entire episode for fantasy managers planning around the post-tournament bilateral calendar.

The decision is retrospective for FPL11 readers six months on, but its procedural anatomy is worth recording cleanly. The ICC did not pre-emptively expel Bangladesh; it set a condition and a clock. The condition was travel to the Indian venues as scheduled. The clock was the additional day, plus the broader window for the BCB to comply before replacement was triggered. That structure is what made Scotland — not a higher-ranked side like Zimbabwe or Nepal — the next team in line for Group C if Bangladesh ultimately did not travel.

What Bangladesh had asked for, and what the alternatives looked like

Bangladesh's formal ask, as reported on 21 January 2026, was to be excused from playing its group fixtures scheduled in Kolkata and Mumbai. The two proposed alternatives were a relocation of those fixtures to co-host Sri Lanka, or a group reshuffle that kept the team entirely outside India for the group stage. The first option would have shifted matches between venues that are already covered by the existing ICC co-hosting arrangement with Sri Lanka through 2027; the second would have required a pool redraw that the ICC argued would have set a precedent it could not afford on neutrality grounds.

Co-hosting with Sri Lanka is not an abstract provision. Sri Lanka is set to host select matches, including the India–Pakistan fixture, under the existing ICC arrangement that runs through 2027, and that arrangement was the structural reason a Sri Lanka relocation was technically feasible. The arrangement also explains why the ICC board was prepared to entertain venue questions at all: cross-border movement of matches was within the published tournament architecture, even if the Bangladesh request would have used it in a way no previous edition had.

The board's eventual position was that the venue request was not supported by a credible security finding. That distinction matters for the broader ICC tournament framework, because a venue change driven by political or governmental instruction — rather than by an independent security review — is exactly the case the board said it could not allow. The Times of India write-up of the meeting captured the framing: the sanctity-of-events line was the language the board chose to make the precedent explicit.

The Mustafizur Rahman IPL removal and the BCB–BCCI standoff

The trigger for the venue request was not security, and it was not a sudden diplomatic breakdown in the bilateral relationship. It was the BCCI instructing the removal of Bangladesh pacer Mustafizur Rahman from the 2026 Indian Premier League roster, citing unspecified "developments all around." The Times of India report on the 21 January 2026 ICC meeting carried that trigger as the documented cause, and the framing matters: this was a contractual decision by the BCCI about a single overseas player, escalated by Bangladesh into a tournament-wide venue dispute.

Bangladesh's response was layered. The BCB banned the broadcast of the IPL in the country and informed the ICC it would not send its team to India for the World Cup. The broadcast ban is the second operative fact for fantasy managers, because it cut off the live IPL coverage that Indian and Bangladeshi fans had consumed through the same distribution partners since at least the 2015 World Cup. For Dream11 and My11Circle managers running IPL-style contests during the T20 World Cup window, the absence of a Bangladeshi broadcast mirror is the single most concrete consequence of the standoff.

The escalation pattern is worth recording in the order it actually happened. First the BCCI removed a single overseas player from the IPL roster. Then the BCB banned the broadcast of the IPL. Then the BCB filed the venue shift request with the ICC. Only after all three did the ICC board convene the 21 January vote. A retrospective reader looking for the "first cause" should weight the IPL removal first, the broadcast ban second and the venue request third; the ICC vote is downstream of all three.

Why Scotland, and what the replacement path actually looks like

If Bangladesh does not travel, Scotland are expected to replace them in Group C. Scotland are next in line based on rankings after failing to qualify via the European Qualifiers behind the Netherlands, Italy and Jersey. The qualification order is what makes the choice automatic rather than discretionary, and that is also what makes it the single most consequential procedural point for fantasy readers: a team six places below Bangladesh in the ICC T20I rankings enters the tournament without a play-off, on the basis of a bureaucratic ordering rather than a sporting decision.

The Group C structure that Scotland would inherit is the same one Bangladesh would have played. Bangladesh's group-stage opponents under the published tournament format were drawn from the teams placed in Group C; that pool is unchanged whether Bangladesh or Scotland occupies the Bangladesh slot. The captain math, the venue log and the Fantasy points model do not change. The team sheet does, and with it the differential-pick math for managers building sides on the tournament window.

For India fantasy managers specifically, Scotland entering Group C moves the most-owned Bangladesh picks — Mustafizur Rahman, Shakib Al Hasan, Towhid Hridoy, Mahmudullah — out of the captain pool and into the "withdrawn from tournament" category. The corresponding ownership migration is onto the Scotland roster, which is a thin squad at T20I level but contains a handful of County Championship players who are available for selection in February if the BCB does not travel.

The Sri Lanka co-hosting arrangement and why the India–Pakistan fixture mattered

Sri Lanka is set to host select matches under an existing ICC arrangement that runs through 2027, and the India–Pakistan fixture is one of the matches already on the published schedule for that arrangement. The 21 January 2026 vote did not touch that schedule — the India–Pakistan fixture was always going to be in Sri Lanka, not in India — but the Bangladesh request would have used the same co-hosting mechanism to move additional fixtures onto Sri Lankan venues. The board's structural concern was not the India–Pakistan fixture specifically but the precedent of moving fixtures into that arrangement on a non-security basis.

The Sri Lankan venues are R. Premadasa in Colombo and Pallekele in Kandy, both of which have hosted World Cup fixtures in the previous two editions. For India fantasy managers running captain pools across both host countries, the Sri Lankan leg has historically produced different surface conditions than the Indian leg — slower turn in Colombo, more variable bounce in Kandy — and the captain math on a Bangladesh-relocated fixture would have run on those surfaces rather than on the flat Indian wickets the tournament was originally designed around.

The ICC's published arrangement runs through 2027, which means the co-hosting provision is not a one-off accommodation for this dispute. It is a structural feature of the next two T20 World Cups. Bangladesh's request to use it for a political-resolution venue change was, in effect, a request to redefine what the provision is for. The board's vote on 21 January 2026 was the formal answer: the provision is for the published schedule, not for venue changes driven by non-security grounds.

What the timeline means for India fantasy managers on the bilateral ODI calendar

Six months on, the cleanest read of the 21 January 2026 vote for India fantasy managers is procedural rather than sporting. The ICC did not change the tournament; it confirmed the schedule, confirmed the security review and confirmed the replacement path. The sporting outcome — whether Bangladesh actually travels or whether Scotland enters Group C — was decided in the 24 hours after the additional deadline the BCB was given. The retrospective read is therefore about precedent-setting, not about a specific result.

For Dream11 and My11Circle managers running tournament-window contests, the practical implications of the 21 January vote are three. First, the Bangladesh roster is a captain-pool pick only if the BCB confirms travel within the 24-hour window — the fantasy exposure should track that window, not the longer board vote. Second, the Sri Lankan venues already on the published schedule remain the source of any captain picks placed on India–Pakistan or other co-hosted fixtures, and those picks are independent of the Bangladesh dispute. Third, the IPL broadcast ban in Bangladesh is a market-level change that does not affect India-based fantasy managers directly but does affect cross-border promotional formats that rely on simultaneous broadcast windows.

For FPL11 readers tracking the broader 2026 cricket calendar beyond the tournament window, the 21 January 2026 vote is also the first ICC board decision of the post-2025 reset cycle. The procedural language — "jeopardise the sanctity of future ICC events" — has not been used at this level since the 2021 cricket governance review, and the precedent it sets is that venue requests grounded in non-security causes will not move ICC events even when co-hosting arrangements exist. The retrospective reading is that the board chose precedent over accommodation, and that choice shapes every ICC tournament venue question for the rest of the 2025-2027 cycle.

Frequently asked questions