Field order 01 · Before entering
Turn five prompts into a squad conversation
Start by confirming the people actually present rather than planning for an assumed party. Official Steam material supports one-to-four-player play, but this checklist does not convert party size into a required composition. The recovery-plan prompt asks the group to agree how it will respond to FAITH and FEAR pressure. It does not claim an exact threshold, resource count, spell, class, or item is mandatory. Use the adjacent Squad Synergy Planner when the group needs to name broad responsibilities before marking this check.
The interaction prompts are reminders to look at the current room and the current build. Official material describes physical interactions and examples involving fire with oil and electricity with water. That evidence supports a plan to observe and communicate; it does not support a universal recipe, guaranteed outcome, or damage value. A physical utility plan can name who notices doors, traps, and movable objects without inventing exact inventory requirements. The boss-preparation prompt is equally conversational: agree on regrouping, recovery, movement, and what evidence should stop the squad from advancing.
Field order 02 · Inside the bunker
Reassess when procedural conditions change
Official descriptions frame the bunker as procedural and interactive, so a useful plan must be revisable. Mark “track FAITH pressure” only when someone is actively watching the resource relationship, and mark “coordinate FEAR recovery” when the group has communicated what recovery means for this run. For the checked mechanics context, read the FAITH and FEAR guide. The checklist deliberately avoids a percentage threshold because the approved evidence does not establish one that should be presented as a universal instruction.
Generator and light decisions belong to the room in front of the squad. The generator guide explains the verified risk-and-visibility framing without promising one correct switch state. Doors, traps, and physical items should also be read tactically from visible conditions. “Conserve resources for boss risk” is not an instruction to preserve a particular count. It is a pause point: compare what remains with the group’s own recovery and exit plan, then decide whether the next step is justified. The bunker guide provides broader procedural-survival context.
Field order 03 · Before B.O.S.S.
Use the final four checks as a threshold stop
The last group is intentionally short. Regroup first. Review the recovery options that genuinely remain, then review capability coverage instead of assuming the original plan survived every earlier decision. The co-op guide offers communication doctrine for shared runs, while the B.O.S.S. guide keeps encounter preparation within the official evidence boundary. Neither page invents phases, health values, counters, rankings, or a supposedly optimal build.
“Avoid entering accidentally/unprepared” is a deliberate stop, not a claim about a specific doorway or encounter trigger. Use it to make sure the group has recognized the transition and chosen to proceed. If the current build presents something different, trust visible in-game information over this editorial card. Leave a short local note when the squad needs a reminder, but do not record personal or sensitive details. The tool cannot see the game, validate a loadout, detect an encounter, or judge readiness.
Record handling · Browser only
Understand what persistence can and cannot do
The interactive card stores a version-one record in localStorage on the current browser. It accepts only the 14 known checklist identifiers and a bounded note. Corrupted JSON, an unknown version, invalid item identifiers, invalid note data, or a note beyond the limit returns the tool to a safe blank state. Extra fields are discarded. If browser storage is blocked, the checklist can still work while this page remains open, but it may not survive a reload.
Nothing in the checklist is shared, copied into a URL, or sent to this site’s server. Clearing site data, using some private-browsing modes, changing browser profiles, or moving to another device may remove the record. Reset always opens a confirmation step before deleting checks and notes. Cancel preserves the run; confirm starts a blank card. This boundary is intentional: a lightweight field card does not need an account, telemetry, a public strategy payload, or a false promise of permanent storage.