# Predicting Every Round of 32 Shock and an England vs. Congo Preview Page: https://stenobird.com/podcast/the-ripple-effect-with-james-lawrence-allcott-6016968/predicting-every-round-of-32-shock-and-an-england-vs-congo-preview Text version: https://stenobird.com/podcast/the-ripple-effect-with-james-lawrence-allcott-6016968/predicting-every-round-of-32-shock-and-an-england-vs-congo-preview.md Podcast: [The Ripple Effect with James Lawrence Allcott](https://stenobird.com/podcast/the-ripple-effect-with-james-lawrence-allcott-6016968) Published: 2026-07-01T08:46:00+00:00 Episode link: https://traffic.megaphone.fm/GLT9996323643.mp3 Audio file: https://traffic.megaphone.fm/GLT9996323643.mp3 Processing state: not_requested JSON: https://stenobird.com/v1/public/podcasts/the-ripple-effect-with-james-lawrence-allcott-6016968/episodes/predicting-every-round-of-32-shock-and-an-england-vs-congo-preview Duration seconds: 3640 ## Resource With the group stage complete, James and Joe look back on their (at times woeful) pretournament predictions, predict the shocks to come in the round of 32, and give a preview of England's next game against Congo. They also discuss some potential transfer rumours and done deals from the past couple of weeks.Host: James AllcottGuest: Joe ThomlinsonProducer: Cai JonesEditor: Finn McSkimmingAdditional Production: Patris Gordon Learn more about your ad choices. Visit podcastchoices.com/adchoices ## Actions - request_transcript: `POST https://stenobird.com/v1/public/podcasts/the-ripple-effect-with-james-lawrence-allcott-6016968/episodes/predicting-every-round-of-32-shock-and-an-england-vs-congo-preview/transcription-requests` — Idempotently request low-priority transcript generation for this episode. - read_markdown: `GET https://stenobird.com/podcast/the-ripple-effect-with-james-lawrence-allcott-6016968/predicting-every-round-of-32-shock-and-an-england-vs-congo-preview.md` — Read the agent-friendly Markdown representation of this episode resource. A page view does not enqueue transcription. Agents should invoke `request_transcript` explicitly when they need this episode processed. ## Transcript Full transcripts are not published on public pages unless there is a clear rights basis.