Preserve each part’s programme identity
Wolf Entertainment’s February 27, 2026 retrospective explicitly maps the 2025 event: Fire’s In the Trenches: Part I, Med’s Part II and P.D.’s Part III. Its description identifies a gas explosion that brings the first responders together. That publisher map establishes the sequence without needing to reconstruct the plot from recaps.
Write each entry with all four fields: programme, season, episode and part title. The part suffix alone is too broad for a large franchise, while “episode 11” leaves out the different season numbers. This also keeps a screenshot or shared viewing note usable outside the provider where it was made.
Read visible metadata rather than the URL slug
The inspected Peacock Fire result displays S13 E11 for Part I even though its URL contains “episode-12.” That discrepancy is a practical reason to use the visible episode record and cross-check the producer’s map instead of deriving an episode number from a path string.
If a service presents a different ordinal, preserve its displayed title and duration and compare them with the event map. An internal slug, collection position and broadcast episode number can describe different indexing choices. Do not silently overwrite a correct title because a URL appears to contain another number.
Do not reuse this sequence mechanically for another year
The same Wolf retrospective maps the 2019 Infection event to Fire S8E4, Med S5E4 and P.D. S7E4. Its 2016 event instead uses Fire S4E10, Med S1E5 and P.D. S3E10, with different episode titles. These examples show why matching episode numbers is not a universal crossover rule.
For a different event, start again from the event’s name and year. Avoid a search for “all episode 11s” or an assumption that a normal weekly channel order supplies the story order. A verified event list is both shorter and more accurate than a guessed all-franchise chronology.
Check the handoff between programmes
After Part I, confirm that the next item belongs to Med and carries Part II. Autoplay can remain within Fire’s season and open an ordinary next episode. Repeat the identity check before Part III. If one part is absent, record the missing programme/title rather than describing the whole crossover as unavailable.
The publisher map and Peacock metadata establish story order and episode identity. They do not establish Canadian subscription access across the three programmes. Confirm the exact local inventories before inviting others to a complete-event session, and avoid reading full recaps if you want to preserve case outcomes.
Sources and scope
Scope notes distinguish published documentation, supplied information and editorial methods. They do not report a hands-on service test.
- Wolf Entertainment: One Chicago crossover retrospective, February 27,2026 — Explicit 2025, 2019 and 2016 programme/season/episode maps; story outcomes not used. Primary official indexed excerpts or explicitly read page sections reviewed; programme playback and Canadian account availability not tested.
- Peacock: Chicago Fire In the Trenches PartI record — Visible S13E11 despite episode-12 path slug; metadata inspected, no stream played. Primary official indexed excerpts or explicitly read page sections reviewed; programme playback and Canadian account availability not tested.
