Early shifts combine routine station work with evidence checking and unpredictable visitors. A clear division of jobs makes those demands easier to follow. This guide uses current official descriptions for the loop and patches for relevant changes, while keeping horror encounters non-graphic and avoiding invented customer answers.
- Choose the session before dividing the work
- Give routine station tasks a clear owner
- Compare identity evidence before reaching a conclusion
- Keep service and investigation visible at the same time
- Use current customers rather than a memorized old sequence
- Adjust teammate audio when communication is unclear
- Read the result in the mode you actually played
- Review the next shift with one concrete improvement
1. Choose the session before dividing the work
Confirm Story or Endless, the participants and the current platform versions. Story has thirteen generated shifts; the developer describes the original cooperative design around three players. Later lobby settings allow up to six, but larger first sessions are explicitly discouraged by the developer. Choose the capacity with that tradeoff in mind. More available slots do not prove that every quota, task or encounter scales into an equally balanced introduction.
Sources: Current Steam listing / Official release announcement / Released six-player lobby update
2. Give routine station tasks a clear owner
Stocking, deliveries, cleaning and serving customers all belong to the documented shift loop. Decide who is currently handling each task and communicate when that responsibility changes. This is an organizational suggestion based on the listed duties, not a verified fastest route or mandatory job lock. A player returning to a shelf does not know whether another teammate has already dealt with it unless the team shares the relevant observation.
Sources: Current Steam listing
3. Compare identity evidence before reaching a conclusion
The investigation loop uses identification, computer information and visitor behavior to distinguish suspicious customers. Compare the observations that the current visitor actually supplies. One unusual action should prompt a check rather than an invented universal answer for every generated case. This guide keeps the game-level identification task non-graphic and does not provide a fabricated roster of all correct identities or prescribe real-world behavior toward a person.
Sources: Current Steam listing
4. Keep service and investigation visible at the same time
Serving customers supports the station loop, while missing a suspicious visitor can create later danger in the game. Tell teammates when a check needs attention so it does not silently displace every routine duty. The store description establishes competing responsibilities, not one infallible order that guarantees every shift. Observe the current situation and keep the evidence question distinct from the practical question of who is free to handle the next task.
Sources: Current Steam listing
5. Use current customers rather than a memorized old sequence
The August and September updates add visitors to both Story and Endless. August also corrects start-of-shift notes that were not randomizing properly. A familiar old sequence is therefore not a reliable substitute for checking the current information. The update counts describe additions at each date, not the exact number you must encounter in one night. Read the active note and visitor rather than deriving an invented fixed spawn order from an older recording.
Sources: August customer and save update / September customer and Endless update
6. Adjust teammate audio when communication is unclear
The August update introduces individual volume sliders for each player. Use that interface when one teammate is difficult to hear relative to another, then confirm that the needed task information is understood. This is a released control, not a promise that it repairs every microphone or network problem. Keep a voice-level issue separate from incompatible platform pools or different builds; those affect whether the session can be shared in the first place.
Sources: August customer and save update / Official release announcement
7. Read the result in the mode you actually played
Endless reports lose quota, personal-funds and pet fields in September, and emails are disabled for that mode. Story and Endless should therefore not be reviewed using an assumed identical report. Ask which task or observation mattered in the current shift rather than diagnosing every missing field as failed progression. September also restores Endless patience, so do not use the earlier no-patience rule when planning how much attention visitors require.
Sources: September customer and Endless update / Earlier balance update
8. Review the next shift with one concrete improvement
Identify whether the difficulty came from unassigned station work, uncertain identity evidence, poor communication, session compatibility or a changed mode rule. Keep one improvement for the next generated shift. Steam cloud saves were added in August, but support for that feature does not justify deleting local progress to solve unrelated gameplay questions. Preserve relevant save information when diagnosing a technical issue and compare the exact current version and mode.
Sources: Current Steam listing / August customer and save update / September customer and Endless update
| Problem during a shift | Useful response |
|---|---|
| Routine task silently neglected | Assign and communicate the current owner |
| Customer identity uncertain | Compare current documents, computer and behavior |
| Result differs from an old video | Check mode, new customers and later rules |
Give each active task an owner and share the evidence you found. Generated visitors still need current checks even when an older sequence looks familiar.
Related guides
Choose a compatible session, divide station work and compare identity evidence. Use player audio controls, current customer additions and the correct mode report to plan a useful change for the next shift.
Sources checked October 14, 2026. Published facts are linked beside their explanations. Planning and practice suggestions are editorial advice rather than verified optimal builds.
Comment
No comments yet. Be the first to post one.