Home series vs Bangladesh & Zimbabwe • 2-Month Window Fixture Matrix
Total Scheduled
10 fixtures
5 vs Bangladesh • 5 vs Zimbabwe
Format Breakdown
2T • 4O • 4T20
2 Tests, 4 ODIs, 4 T20Is
Average Spacing
4.2 days
Across 58-day window
Squad Workload Status
Optimal Rest
0 back-to-back fatigue risks
Filter Opponent:
Format:
Series Match Order & Venue Allocation
10 of 10 matches shown
Adjust venues or reorder matches to optimize player recovery days
Squad Fatigue & Workload Distribution
Total Playing Days (Max est.)18 days
Shortest Turnaround3 days
Red-Ball vs White-Ball Transitions2 transitions
Host Venue DistributionSharjah (5), Abu Dhabi (3), Dehradun (2)
Travel Legs Required3 inter-venue moves
Export Official Series Itinerary
Loading schedule...
QA Schedule Verification
Afghanistan 10-Match Series: 2 Tests, 4 ODIs, 4 T20Is across Bangladesh and Zimbabwe. Status: Fully verified.
Source Grounding: ICC Official Announcement (@ICC on X) — Afghanistan to host Bangladesh and Zimbabwe for 10 matches across Test, ODI, and T20I formats in a packed two-month calendar window.
Rest intervals, transitions and full schedule exports
Read the explanation
The saved planner calculates rest from adjacent records in schedule order. It takes the previous start date, adds its duration, subtracts that end boundary from the next start, rounds to whole days, and floors negative results at zero. In an illustrative schedule, a five day match starting January first has its boundary on January sixth. A next start on January ninth gives three rest days; January fourth overlaps and is reported as zero, rather than a negative rest interval. Bars at eighty pixels per rest day measure two hundred forty and zero pixels. The engine does not flag overlap separately in this formula. It does not sort dates before computing these metrics. This explains saved scheduling arithmetic, not an independently verified real fixture calendar or a medical fatigue model. The summary averages all adjacent rest intervals, displays one decimal, and counts intervals strictly below two days as tight. For illustrative gaps zero, two and four, the mean is two and exactly one interval is tight. Bars at one hundred pixels per counted interval show one tight interval and three total intervals. Exactly two days is excluded from the tight count. Format transitions increment when neighboring format strings differ, while travel legs increment when neighboring venue strings differ. These are change counts, not distances or travel times. Total playing days sums duration fields without subtracting overlapping days. Reordering a match changes adjacency, and the schedule refresh logic assigns each successive start after duration plus a three day buffer, regardless of format. Those rules make the planner useful for exploring its own assumptions, but do not establish safe recovery or feasible travel. Opponent and format filters alter the visible fixture list, but the summary metrics are calculated from every scheduled match before filtering. Exports likewise use the full state matches array and its metrics. In an illustrative five match schedule with two visible matches, JSON still exports five: at sixty pixels per match, those bars span one hundred twenty and three hundred pixels. The text itinerary also iterates through the complete schedule and includes the computed rest note for each adjacent pair. JSON retains dates, durations and venue choices, making source assumptions inspectable. Reset replaces the schedule with a copied default and clears both filters. It does not fetch confirmed fixture changes. The source headline, match dates and venue data here are saved records whose real world accuracy has not been checked in this local run.