FPL pre-season roundup, 4–5 August: Bournemouth score ten and City win

The pre-season verdict

The latest batch covers matches played on 4 and 5 August. On 4 August, Bournemouth beat Genoa 10-1 behind closed doors, Ipswich beat Le Havre 1-0, Aston Villa beat BG Pathum United 3-1 and Coventry drew 1-1 with West Bromwich Albion. On 5 August, Manchester City beat the K-League All-Stars 3-1, Brentford beat Wycombe 4-1, Arsenal lost 3-1 to Real Betis and Chelsea lost 1-0 to Juventus.

These are final results from 4 and 5 August, taken from the Premier League's official friendly hub when it was accessed on 6 August. The access date is not the match date. The results describe team outcomes, not FPL recommendations: opponent strength, split squads, substitutions and training loads vary widely in pre-season.

Pre-season scorelines are most useful as routing signals. A large win tells the editor which club report and lineup deserve inspection, not which attacker must enter an FPL squad. The next layer is scorer and assister identity, followed by position, opponent quality, minutes and whether the first-choice group was on the pitch. Without those layers the responsible conclusion stops at the team result.

Results and key moments

Across their first three listed matches Bournemouth have scored 19 goals, while Arsenal have scored eight and conceded four. Manchester United's first three results contain seven goals for and two against; Manchester City have four for and two against from two games. Those totals are descriptive only and the chart deliberately avoids converting them into expected league goals.

The official hub creates a consistent results spine while linked club reports supply detail. Preserve both links because a club may later update its report or publish highlights. When an article refreshes, store the previous access time and update the summary, chart and social copy together; a homepage card must not keep an old score after the body changes.

• 5 August: Arsenal 1-3 Real Betis.
• 5 August: Chelsea 0-1 Juventus.
• 5 August: Brentford 4-1 Wycombe.
• 5 August: K-League All-Stars 1-3 Manchester City.
• 4 August: Ipswich 1-0 Le Havre.
• 4 August: Genoa 1-10 Bournemouth.
• 4 August: West Bromwich Albion 1-1 Coventry.
• 4 August: BG Pathum United 1-3 Aston Villa.

Minutes and starting roles

The Premier League hub verifies fixtures and results but does not provide a complete common minute log for every player. Player-level role conclusions therefore require the linked official club reports and lineups. A start in one friendly is evidence of involvement, not confirmation for Gameweek 1; repeated starts with first-choice teammates are stronger but remain a likely-starter signal.

Record starts, halftime changes, substitution times, position and set-piece involvement in the minutes tracker. When clubs split squads or play behind closed doors, mark missing detail rather than estimating it. This article will not claim a player led a role unless the source record supports it.

Minute patterns should be compared across at least two meaningful appearances where possible. A player completing 75 minutes after two 45-minute outings may be building load; a substitute used with the first team may still be closer to the XI than a starter in a separate squad. The tracker should describe the pattern and let the editor assign confidence rather than turn it into certainty.

Injuries and availability

An unexplained absence is not an injury. Cross-check club reports with the Premier League injury hub and official FPL player status, then preserve the source's wording. The roundup should mention only players whose absence or return is material to the matches covered and supported by an exact current source.

Availability reporting has a deliberately higher evidence bar than results. A final score is objective; the reason for an absence may not be public. If a club report says only that a player missed the match, repeat no more than that. If a manager names an injury or workload plan, attribute it and retain the date because return expectations can change quickly.

What changes for FPL

Bournemouth's attacking output earns attention for the final friendly against Real Betis, not an automatic triple-up. City's win reinforces the need to monitor the high-upside midfield rotation, while Arsenal's defeat does not erase their strong modelled opening defensive route. The practical changes are watchlist changes: verify who produced the output, who shared minutes and whether the same role persists.

Refresh this daily roundup after official final results. New matches should update the chart and body together, preserve the access time, and replace rather than append duplicate descriptions. Never publish a provisional score as final.

For FPL, the most actionable pre-season change is often expected minutes rather than a points forecast. A stable starting role can move a budget player onto the bench shortlist, while a shared position can lower an expensive player's floor. Feed those changes into the model only after verification, then explain which part of the projection changed and why.

The next edition should begin from a new official-results fetch, then reconcile additions against this dated record. Preserve corrections visibly when a venue, opponent or behind-closed-doors status changes. This keeps a daily article useful as an audit trail instead of turning one URL into an undated mixture of several different evidence windows.