Manager
Man Utd had planned to sack Carrick this week but could not agree on a replacement
United sources confirmed Carrick will take charge at Chelsea on Saturday after the club failed to settle on a successor.
Golviva NewsroomUpdated

Manchester United had intended to sack Michael Carrick before Saturday's Premier League trip to Chelsea but pulled back after failing to agree on a replacement, according to The Sun. United sources confirmed on Tuesday that Carrick will remain in charge for the away fixture at Stamford Bridge.
Carrick's position had already been under pressure following recent poor results, and the club's hierarchy had deliberated seriously over removing him. However, the inability to identify and agree terms with a successor granted him what multiple outlets are describing as a stay of execution.
Sky Sports, BBC Sport and journalist Simon Stone all reported earlier in the day that Carrick would stay in charge for the Chelsea game, though The Sun's report adds the significant detail that a sacking had been actively planned. United insiders stressed that Carrick and the players will continue preparations as normal for Saturday's match.
Sources
This article is based on reports by:
- The Athletic — Michael Carrick to be given more time to turn Manchester United form around
- Laurie Whitwell (@lauriewhitwell) — 🚨 Michael Carrick will be given chance to turn results around.
- Ben Jacobs (@JacobsBen) — BREAKING: Michael Carrick set to be given time to turn things in around.
- BBC Sport — Carrick to stay in charge of Man Utd for Chelsea game
- Sky Sports — Carrick to remain in charge of Man Utd for Chelsea trip
- Simon Stone (@sistoney67) — Michael Carrick set to be in charge for @ManUtd game at Chelsea on Saturday.
- Mirror — The four decisions Michael Carrick must make NOW as Man Utd boss gets stay of execution
- The Sun — Man Utd had planned to SACK Michael Carrick before Chelsea clash but failed to agree on replacement
Written by the Golviva newsroom from the reports below, with figures from Golviva’s own database. Spotted a mistake? Tell us. · How we report







