THE SHORT VERSION

Identify the specific falling need, then check that a customer can reach and use its service before changing several systems at once.

The steps below are editorial suggestions to test in your own save.

Name the symptom precisely

Start with the specific need or warning shown in your game. Record when it began and the last substantial change you made. A new district, a rebuilt route and a newly unlocked service give you different places to investigate.

Read available citizen feedback alongside broader trends. One unhappy visitor is useful evidence about that journey; it does not by itself explain the entire city. Look for a repeated pattern before committing to a large rebuild.

Trace access before adding duplicates

Follow a customer toward the relevant service. Can they approach, use it and leave? Then inspect any visible operating or supply warning. A building's presence is not enough to show that it is solving the need you are watching.

  • Confirm the service matches the need you are investigating.
  • Observe the approach and exit as well as the service itself.
  • Check for supply interruptions where applicable.
  • Compare the trend after one targeted change.

Recheck your plan after an unlock

Treat each progression step as a review point. Look through the game's newly available options and current objectives instead of assuming your earlier service mix remains sufficient.

Our planning suggestion is to leave flexible space near a growing district. Reserve room for a route adjustment or a future service, then decide what belongs there from the needs actually visible in your save.

Test prices separately from access

If you want to experiment with prices, first establish a reasonably stable service setup. Record the price, the observed trend and the length of your observation. Make a small, reversible change and compare like with like.

There is no verified universal profitable price in this guide. Scenario, progression and updates may change the result. A useful finding is one you can reproduce with the same conditions, not simply the highest number a screenshot happens to show.

Choose a check from the feedback

A warning is your starting point, not a complete diagnosis. Match the need mentioned in feedback to an observed journey and make one change only after that observation.

  • A particular need remains unmet → identify its matching service and inspect any operating warning; follow one customer toward it.
  • A service exists but customers wait → inspect the approach and departure. If the route stalls, test one connection before adding another service.
  • Several needs worsen after an unlock → review the newly available options and current feedback. Address one repeated unmet need, then compare its trend.
  • Feedback changes after a price adjustment → record the price and conditions; if the change is reversible, compare with the earlier price before changing roads or services.
  • One visitor complains while broader trends look stable → observe additional journeys before treating that individual experience as a site-wide failure.

Use one need as your before-and-after check

Record the exact feedback, the service you inspected and the trend available in your version. Keep a brief note of the observation period so the later comparison uses similar activity.

Make a single change that addresses what you saw: restore a warned-about service, revise the approach or test a price separately. Watch customers use the service again and recheck the same need.

An improved overall impression is weaker evidence than a repeated journey that now completes and the same need improving. If the warning remains, record that result and inspect the next hypothesis rather than declaring the fix successful.

READY FOR THE NEXT CHANGE?

Your quick checklist

Tick these off while you inspect your save. Checks are temporary.

Sources & limits

Guide updated 12 Oct 2026. Source review dates appear above. Pre-release descriptions can change. These suggestions have not been tested in a played save. Full editorial policy.