01
Find the requirement that prevents the next upgrade
A Sanctuary upgrade can look like a single goal while depending on several smaller tasks. The useful question is: which unmet condition can you change next? Answering that is more actionable than choosing a random building to improve or spending a speed-up on whichever timer is closest to finishing.
This guide uses v1ne1c's March 29, 2026 beginner video, particularly 01:00–01:45 and 08:12–08:35. Its public Russian captions describe a prerequisite-and-waiting routine, but no client version was verified. Treat the recording as dated player advice. The diagnostic process below is our editorial framework; current costs, unlock levels, and exact timers must come from your own client.
02
Read the destination before starting another task
Open the next Sanctuary upgrade and inspect what it asks for. Keep the intended destination in view: a required building is useful because it removes a particular condition, not merely because raising buildings feels like progress.
Make a short record of the unmet requirements. Use the game's current names and amounts when you do this for yourself. Separate requirements that are already satisfied from those that still need action, and distinguish a process that has started from one that has actually finished.
In the 01:00–01:45 sequence, the creator checks what the next Sanctuary level requires and starts the necessary construction. The transferable idea is to begin at the desired upgrade and work backward. This guide does not substitute a historical building list for the requirements displayed on your server.
03
Diagnose the kind of obstacle
The following categories are a reading aid, not a claim about every possible requirement in the game. Use the ones that match what your client actually displays.
| What you find | What to establish | Useful next decision |
|---|---|---|
| A required building is below the stated condition | Its own unmet prerequisites | Trace that building's next actionable requirement |
| A required process is still running | Whether its completion removes the condition | Use the wait for other available tasks |
| Resources are insufficient | Which specific material prevents the action | Plan for that shortage before unrelated spending |
| The required building or task is unavailable | What progress leads to access | Inspect the relevant progression task |
| The reason remains unclear | The exact requirement wording | Read it again before committing resources |
Avoid treating all of these as timer problems. Finishing an unrelated process cannot remove a different unmet condition simply because it also contributes to settlement growth.
04
Work backward to an action you can take
Suppose the Sanctuary needs a building improvement, and that improvement has its own prerequisite. That is a dependency chain. Your immediate task is the earliest unfinished step you can act on, while the Sanctuary remains the destination.
Use this sequence:
- Read the blocked Sanctuary condition.
- Inspect the required building or task.
- Read any prerequisite that blocks that requirement.
- Continue until you reach an available action.
- Start that action and remember which later condition it serves.
This prevents a common planning mistake: collecting enough resources for the final upgrade while leaving its prerequisite construction untouched. It also helps you recognize optional upgrades. An improvement can be valuable without belonging to the immediate chain you are trying to complete.
For broader choices about what to build between required steps, use the building order guide. This page stays focused on removing the next Sanctuary obstacle.
05
Check Doctor's Path when access is the problem
At 08:12–08:35, v1ne1c connects further Sanctuary progress with buildings made available through Doctor's Path. That gives you a specific connection to investigate if a requirement points toward something you cannot yet access.
Read the progression task alongside the building requirement. Is there an available activity that moves that task forward? Does completing it address the missing access, or are you assuming a connection without checking? Follow what your current client shows rather than assigning an unlock level from memory.
The official game description includes sanctuary management and treating patients. It does not provide a complete Doctor's Path unlock map. The useful habit is therefore to check the relationship between progression and access, while avoiding a claim that every building follows the same route.
06
Let necessary construction run while you do active tasks
The creator's 01:00–01:45 workflow uses construction time for clinic activity and Doctor's Path progress. This helps separate two questions: what needs elapsed time, and what can you actively complete while that time passes?
Once the required construction is running, review the available tasks that do not depend on its completion. Choose something useful you can actually do now. You are not looking for an additional construction slot or assuming that every activity can run simultaneously; you are using active play to occupy an existing wait.
If your intended action is still blocked, identify whether you have reached the same prerequisite again. Repeatedly reopening an unavailable upgrade is a signal to change tasks or wait, rather than to spend on an unrelated system just to keep clicking.
07
Decide what a speed-up would change
Before accelerating a process, state the result you expect: “Finishing this requirement will let me attempt the next step.” Then inspect whether other unmet conditions would still prevent that step.
If another required building is unavailable or a resource shortage remains unresolved, completing one timer may leave the overall objective blocked. That does not make the item worthless; it means you should understand what it accomplishes before using it.
The dated video recommends exhausting available settlement actions before accelerating construction. Use that as a prompt to compare waiting with active play, rather than a universal command to save every speed-up. Alliance assistance can also affect a waiting decision, but verify what help is actually available to you; the alliance guide covers that cooperation separately.
08
Return to the original requirement after each completed step
When a prerequisite finishes, reopen the Sanctuary upgrade and reassess it. Confirm that the expected condition changed, then identify what remains. Do this before continuing along an assumed sequence of upgrades.
If two goals compete for the same resources, give each a purpose. One may remove the immediate Sanctuary obstacle; another may improve a different system you also value. Choose deliberately rather than describing every optional improvement as mandatory preparation.
A compact plan can contain four notes: the desired upgrade, the current obstacle, the next actionable prerequisite, and what you will do while waiting. Update those notes after completion. For the surrounding systems, return to the beginner guide; for research choices, use the research guide. Keeping those decisions separate makes the Sanctuary requirement easier to diagnose.
Common questions
Before you continue
Where should I check Sanctuary upgrade requirements?
Use the requirements displayed for the next Sanctuary upgrade in your current client. Record each unmet condition rather than assuming a historical guide's building levels or resource costs still apply.
Why can I still be blocked after upgrading a required building?
Reopen the original upgrade and inspect the remaining requirements. The completed building may have removed one condition while another resource, prerequisite, or unfinished process still needs attention.
Should I upgrade every building before the Sanctuary?
This guide does not establish that as a requirement. Trace the actual prerequisite chain for your chosen objective and distinguish required construction from optional improvements.
Does this page include a complete level-by-level cost table?
No. Current numerical costs, timers, and unlock levels have not been verified. The guide teaches a prerequisite-checking workflow supported by dated creator advice instead of inventing a table.