14 min read

One Club. Two Teams. Is Wednesday Ready for WSL2?

After several test seasons, database tweaks and a second year with the full Sheffield Wednesday squad, I finally had a clearer picture of what the team could achieve and what I'll need to sort when taking charge in FM27.

The plan for my FM27 save is to bring Sheffield Wednesday's men's and women's teams together, give them one shared identity and build towards two ambitions.

In One Club. Two Teams. A Whole Lot of Wednesday, I introduced the save, the challenge of bringing both sides of the club together and what I wanted to achieve. Before taking charge, though, there was some work to do behind the scenes.

The biggest question was whether the women's team was ready for WSL2. I needed to build the squad, get the database into shape and see how Wednesday would perform before committing to the save.

In Part 2, I covered the research behind building Sheffield Wednesday Ladies in the database: looking into the players, setting their abilities and attributes, and giving the team a place within the wider club. With that work done, the next step was to see how the team would actually perform.

I didn't want to make the team artificially strong just to get a good first season. Equally, there was no point sending Wednesday into a division where survival looked impossible. I wanted a believable starting point: a team that could compete, had clear areas to improve and still had room to grow.

I ran a series of test seasons to see how the squad performed and identify anything that needed changing. Once I was happy with the database, I let the final version run for a second season to see how the team developed.

These weren't controlled, identical tests. I made adjustments along the way, so the results are best viewed as a record of the process rather than a strict comparison.

Average points23.4Across the first-season tests
Average finish9thIn WSL2
Best finish4th35 points
Second season6th32 points in season two

Getting Wednesday ready for WSL2

Before looking at the results, it's worth explaining what I was trying to build. I used existing WSL2 clubs and players as benchmarks, looking at Current Ability (CA), Potential Ability (PA), individual attributes and the resources available across the division. The aim was to create a squad with a mix of experience, young players with room to grow and enough depth for a full season.

The early runs gave me plenty to think about.The first two test seasons both ended in 12th place, with 16 and 15 points respectively. That was a pretty clear warning that the original setup needed attention. Rather than simply increasing everyone's CA, I started looking more closely at the players themselves and asking whether their attributes suited the positions they were playing.

A player can have a decent overall rating and still have a weakness that causes problems on the pitch. A centre-back might look fine on paper but lack pace, strength or concentration. A goalkeeper might have a reasonable CA but not the reflexes or handling needed to perform consistently at this level. I wanted to look beyond the headline number.

The player research also helped me think about how the squad would work as a whole. I wanted a mix of experience, different strengths and weaknesses, and players with room to develop. The aim was to build a believable team, not a cheat code.

Testing and refining the database

The early test seasons helped me spot a few things that needed attention with the club. I adjusted the club's facilities and, after realising I'd forgotten to enable FM's option to automatically add key staff during the initial setup, corrected that too. I also reviewed the squad's player ratings.

Some players received upgrades to their Current Ability (CA), while I also tweaked individual attributes where I felt their profiles needed another look. The aim wasn't to keep boosting Wednesday until they started winning. I wanted to get the club and squad into a place I was happy with before starting the actual save.

Because I made these changes along the way, the results aren't a perfect like-for-like comparison. They're still useful, though. They show what Wednesday were capable of at different stages of the database work and helped me identify the areas that need the most attention.

A shared home and a proper club setup

The project was never just about adding a women's team to a league. I wanted both sides to share the same identity, stadium and facilities. The men's and women's teams will play at Hillsborough Stadium and use Middlewood Training Ground, giving the women's side a clear place within the wider club.

Club setupStarting pointBased on
StadiumHillsborough StadiumMen's team
Training groundMiddlewood Training GroundMen's team
Attendance figure1,495WSL2 average
Minimum attendance668WSL2 average
Training Facilities13Men's team
Youth Coaching11Men's team
Youth Facilities13Men's team
Youth Recruitment12Men's team
Youth Importance11Men's team
Corporate Facilities15Men's team
Club Reputation6600WSL2 average
Starting transfer budget£75,000WSL2 average

The idea was to give the women's team the same foundations as the men's side, rather than creating an entirely separate club. The stadium, training ground and facility ratings all match the men's setup, while the attendance figures, club reputation and starting transfer budget are based on WSL2 averages.

What did the results look like?

Across the tests, Wednesday finished between fourth and 12th, averaging 23.4 points over 22 matches. The best return was fourth place with 35 points, while the lowest was 12th with just 15. Ninth place was the most common finish, which gives a useful sense of the team's general level.

Rather than list every test run as though they were identical, here are a few results that show the range of outcomes:

Test resultManagerPositionPointsW-D-LGoals (F-A)GDxPTS
Lowest points returnCarly Davies12th152-9-1122-40-1827.02
Typical mid-table finishCarly Davies9th245-9-821-30-924.13
Strong points returnCarly Davies7th308-6-828-28026.47
Best finishDavies / Karen Hills4th359-8-528-27+129.13
Final full-squad first seasonCarly Davies9th245-9-829-31-225.46

Each test covered 22 league matches. The final full-squad test included the Sheffield Wednesday Ladies youth and reserve players.

Does the manager make a difference?

Most of the test seasons were left to the AI, which repeatedly appointed Carly Davies as manager. I also wanted to see whether changing the manager would have a noticeable effect, so I manually added three different managers in separate test runs.

Sonia Bompastor finished 10th with 26 points, Emma Hayes also finished 10th with 25 points, while Sarina Wiegman finished 11th with 16 points. None of those appointments produced the dramatic improvement I might have expected from such high-profile names.

The most interesting managerial change actually happened without my intervention. In the best-performing run, Carly Davies was sacked in December and replaced by Karen Hills. The team went on to finish fourth with 35 points.

It would be easy to point at Karen Hills and claim that she was the answer, but one test isn't enough to prove that. The squad, recruitment and timing of the change all played a part. What the results did show is that a big-name appointment doesn't automatically guarantee success.

How did the team perform?

The results point towards a side capable of holding its own in WSL2, but not one that can be relied upon to produce the same level every season. Mid-table was the most common outcome, although the lower finishes show that a difficult run could quickly turn into a battle near the bottom.

That's probably the most useful conclusion from the testing. Wednesday have enough about them to compete, but they aren't a finished product - the aim when I take charge will be to raise that general level and make the team more reliable, rather than chasing one exceptional season.

The gap between expected and actual points

The league table tells one part of the story. Expected points add another. Across the first-season tests, Wednesday averaged 23.4 actual points against an expected total of 26.6. That's a gap of around 3.2 points per season, and it is worth keeping an eye on when I take charge.

Some of the lower finishes had a sizeable gap between actual and expected points. Another difficult season ended with just 16 points despite an expected total of 29.29. At the other end, the best finish brought 35 points from an expected total of 29.13, showing that Wednesday could also outperform those numbers.

Actual points vs expected points

Average across the first-season tests

Actual
23.4
Expected
26.6
Average difference-3.2 points per season

Expected points aren't a prediction of where a team should finish, and they don't tell us exactly what is going wrong. However, the repeated gap between the two figures gives me something to investigate. The performances suggested Wednesday could have earned more points than they actually did, so I'll be interested to see whether I can close that gap once I'm in charge.

Goals: scoring isn't the only problem

Looking at the goal difference across the test seasons gives us another useful clue. The team scored between 18 and 30 goals, with the highest-scoring seasons reaching 30. The final full-squad first season also saw Wednesday score 29 goals.

The defensive record is less convincing. Sheffield Wednesday conceded 28 or more goals in most of the test seasons, with the worst season seeing 40 conceded. Only two seasons saw the team concede fewer than 28 goals.

That doesn't mean the defenders are automatically the problem. The goalkeeper, tactical setup, player roles and the quality of the opposition can all affect those numbers. However, it does give me a clear area to investigate when looking at the squad. I want to understand whether the players have the right attributes to defend at WSL2 level, rather than simply increasing their ratings until the results improve.

Recruitment has a big part to play

The AI made plenty of changes to the squad during testing, so these seasons weren't simply a measure of how well my original players performed. Recruitment played a big part in shaping the results, with free agents, loans and permanent deals all used to improve the team.

The main lesson is that the squad won't stand still once the save begins. I'll need to manage the budget carefully, make use of loan opportunities and be prepared for players to leave.

The final version of the database

By the final test, the database included the full Sheffield Wednesday Ladies squad, including youth and reserve players. The wider club setup had been checked, missing staff had been added, facilities had been adjusted where needed and I was happier with the player ratings and attributes. I had also fixed some work permit issues that affected some earlier tests.

This was the version I wanted to take into the actual save. It wasn't about chasing the best possible league position; it was about having a complete, believable starting point and knowing which parts of the squad would need my attention.

In that version's first season, Wednesday finished ninth with 24 points, scoring 29 goals and conceding 31. A solid mid-table result, but I wanted to know whether the expanded squad could build on that in year two. So I left the save running.

One final check: Season Two

With the final version of the database in place, I wanted to see what happened if I let the save run for another year. This wasn't part of the first-season averages. Instead, it gave me a chance to see how the full squad developed, how the AI handled recruitment and whether Wednesday could build on their first season.

League finish6thUp from 9th
Points32Eight more than season one
Record9-5-822 league matches
Expected points31.53Expected position: 5th

Wednesday finished sixth, scoring 22 goals and conceding 30. They were just two points behind Ipswich in fifth and five points short of the play-off places. The expected points table also placed them fifth, suggesting their performances were good enough to support a finish around that position.

Season two summaryResult
League position6th
Played22
Wins – Draws – Losses9 - 5 - 8
Goals for22
Goals against30
Goal difference-8
Expected goals (xG)25.98
Expected goals against (xGA)24.11
Expected points (xPTS)31.53
Expected position5th

Managerial changes

There was another change in the dugout during the second season. Carly Davies, who had been in charge since August 2026, left on 19 December 2027. Jo Potter, a former Sheffield Wednesday Ladies player, was appointed on 22 January 2028 and remained in charge until the end of the season.

ManagerJoinedLeftTime at club
Carly Davies15/08/202619/12/20271 year, 126 days
Jo Potter22/01/2028Still in charge-

The second season suggests the squad was moving in the right direction without further database changes. However, 30 goals conceded and only 22 scored show that there is still plenty to improve. Sixth place is encouraging, but it doesn't change the priorities I'll be taking into the save.

What have we actually learnt?

The testing has given me a much better idea of what Sheffield Wednesday need. There's no need to keep changing the database, but there are some clear priorities I'll need to address once I take charge.

Survival comes first

Wednesday have shown they can compete in WSL2, but the lower finishes are a reminder that a difficult season is always possible. I'm not going into this save expecting promotion or a top-four finish. The first target is to establish ourselves, avoid a relegation battle and build some consistency.

The defence needs attention

This is probably the biggest concern from the testing. The team regularly conceded too many goals, and the second season didn't completely solve that problem. I'll need to look at the goalkeeper and back line, but also consider how much protection the midfield provides. Replacing defenders alone might not fix the issue.

Recruit carefully

The AI made regular use of free agents and loan deals, showing how important the transfer market can be at this level. With a starting budget of just £75,000, I'll need to be smart with any money available. Loans can fill gaps, but I don't want the squad to become too dependent on players who might only stay for one season.

Build consistency before chasing promotion

The best results show what Wednesday might be capable of, but I don't want to judge the save by one good season. The bigger challenge is raising the team's usual level and making sure we can compete week after week. If we can do that, the bigger ambitions can follow.

So, what does that mean for my save?

The main priorities are clear: establish Wednesday in WSL2, improve the defence, make better use of the transfer market and build a more consistent team. I'll need to be careful with the limited budget, use loans where they make sense and give the squad time to develop.

I'm happy with the starting point I've created, but the testing has shown that there's plenty of work ahead. Survival comes first. Once we've built a team that can compete week after week, we can start thinking about what comes next.

No more testing. It's time to play.

There's always something else I could check in the pre-game editor - another player rating to review, another database change to try or another season to watch unfold. But at some point, the preparation has to stop. I've reached the point where I'm happy with the starting setup, and the only way to find out what Wednesday can achieve is to start playing.

Now it's my turn to take charge. No more watching Carly Davies or Jo Potter make the decisions, and no more waiting to see what the AI does with the squad. I'll be choosing the tactics, handling recruitment and finding out how far I can take Sheffield Wednesday.

There are plenty of questions to answer. Can we make Hillsborough a difficult place to visit? Which players will step up? How far will that £75,000 starting budget stretch? And can we turn a team capable of finishing sixth into one that can eventually challenge for promotion?

I've spent long enough preparing. The database is ready, the squad is set and the spreadsheets can take a break. It's time to start the save.