The safest Night At The Infirmary protocol is a decision loop, not a memorized string of clicks. Keep one patient active, let the current objective choose the next station, compare independent evidence, and complete either the treatment path or the anomaly response before moving on. This approach remains useful when beta updates change a tool label, treatment branch, or patient count.
Phase 1: establish the active case
Read the objective and identify which patient the game considers active. Current walkthroughs place the patient at an examination bed before many checks and treatments become available. If the patient is waiting elsewhere, follow the visible call, guide, or placement prompt rather than dragging the whole ward into the process.
Once the patient is positioned, pause. Confirm that the objective changed and that the correct case is attached to the bed. Starting diagnostics on the wrong bed or calling another patient too early can create overlapping interactions that look like a bug.
Phase 2: build the baseline
Use the patient form or computer when the task exposes it. Current guides report fields such as a photo, name, age, and injury. Treat them as context to compare with the person and requested care; this page does not claim every field can become anomalous in every update.
Read the injury because it helps explain the treatment branch. A normal-looking identity does not settle the anomaly question, and an unusual injury is not automatically supernatural. Keep identity, injury, measurements, and visible behavior as separate observations until the game asks for a decision.
Phase 3: use diagnostics in a stable order
When available, start with the least ambiguous requested check. Current community sources repeatedly describe heart-rate information and temperature, followed by night vision when more context is needed. The exact device order is not official, but a stable sequence prevents skipped evidence.
Use this practical order:
- Read the form and visible condition.
- Attach or activate the requested heart-rate check.
- Use the temperature tool when the branch exposes it.
- Add night vision only when the objective or uncertainty justifies it.
- Recheck after a major visual change or treatment reveal.
Around 37°C appears as a community-reported normal anchor, not a published pass interval. Likewise, impossible heart-rate behavior is a strong warning, but this guide does not publish a complete safe range. The Diagnostics guide explains what each category can and cannot prove.
Phase 4: choose treatment or anomaly response
If the case remains consistent, continue with the exact treatment task shown. Directly relevant guides mention steps around preparation, monitoring, limb care, and casts, but branch order can vary. Complete one named action, watch the task update, then proceed. Do not place every reported supply on every patient.
If evidence becomes impossible or the game explicitly exposes an anomaly response, stop ordinary treatment. Current community guides identify the crucifix as the response tool in the treatment-room flow. Pick it up and follow the available interaction rather than guessing a distance, duration, or timing window. The Crucifix guide covers positioning, feedback, and failure recovery without inventing an exact cooldown.
Phase 5: close the case cleanly
A case is not finished merely because the patient animation changed. Confirm that the objective advances, complete any form or computer decision, and perform cleanup if the current task requests it. Only then call the next patient.
If the queue appears frozen, trace the protocol backward: final decision, treatment completion, requested tool, patient placement, active case. The first unresolved step is usually more useful than searching another room. Use the dedicated Troubleshooting guide for platform and stale-server checks.
Decision matrix
Protocol differences by night
Night 1 is the best place to learn the complete case boundary. Night 2 community walkthroughs report changed prompts and a faceless warning, so reading the new instructions matters more than speed. Night 3 and Night 4 have official completion badges but thinner public route evidence; keep the same task-led structure while refusing to import a Night 2 patient total or anomaly rule.
The nights can increase pressure without changing the purpose of the protocol. Your job remains to know which patient is active, which evidence is objective, which action the game requests, and whether the case truly ended.
Protocol FAQ
Is this the exact permanent treatment order?
No. It is a current community-supported decision framework. Patient branches and beta updates can alter the individual interactions.
Should I use night vision on every patient?
Use it when available and useful, but do not let it replace clearer form or measurement evidence. Hallucination warnings make repeated unsupported checks costly.
When should I call the next patient?
Only after the active objective confirms the current case is complete. Check the form/computer decision and requested cleanup first.
What if an anomaly appears during treatment?
Stop ordinary treatment, re-read the prompt, and use the current anomaly response. Do not assume every reveal has the same timing or name.
Where do classes fit?
Classes can alter the pace or comfort of parts of the loop according to current third-party guides. They do not replace reading evidence. Compare roles in Class Selection.