The detective layer is the information gate of Shift At Midnight. A customer is not only a sale to complete; the Store page says you examine an ID, cross-check details in the computer, and observe behavior before allowing the person to leave. If a creature slips through, it can return later in the shift. That makes the correct habit more important than a fast guess: collect the available evidence, compare it in the right place, then make a decision you can explain to a teammate.
Treat the customer as a small investigation
Start with the information the interaction actually gives you. Look at the ID, note the identity fields the interface exposes, and decide which details need a database lookup. Then use the computer rather than relying on a remembered name or face. Finally, watch how the person behaves while the interaction continues. These three sources—document, database, behavior—are the official public description of the loop. They are not a license to invent a universal “always ban this feature” chart.
A useful mental model is claim, check, consequence. The ID makes a claim about who the customer is. The database lets you check the claim against another record. The consequence is your decision to serve, delay, or treat the customer as a threat according to the actual game prompt. If the screen does not expose a field, do not fill it with a community rumor just because another guide mentions it.
Move between the counter and the computer
The route matters because every trip away from the customer costs attention. Before starting a long physical task, learn the shortest safe path to the computer and back to the service area. When playing with friends, say “I am checking the database” so a teammate knows that the customer decision is not abandoned. When playing alone, finish the check before stacking a second objective on top of it unless the interface gives you an explicit interruption.
Keep the station visible while investigating. The official game loop includes stocking, deliveries, cleaning and serving customers, so the computer cannot become a permanent safe room. A good route ends at a position from which you can see or reach the entrances. This is a planning principle, not a claim about a fixed map layout. Randomly generated shifts and updates can change where a player wants to stand.
How to record a clue without overclaiming
When a customer is accepted or rejected, write down the complete context: the displayed ID, the database result, the behavior you noticed, the shift or branch, and whether a teammate saw the same thing. “The face looked wrong” is too weak to reproduce. “The ID field differed from the database result on the default branch after the July 29 update” is a testable observation, though it still remains a player report until confirmed by a broader source.
Do not call an observation an official rule just because it worked once. A customer name, date, clothing choice, or question response may matter, but the public Store page does not publish a complete clue taxonomy. Use the current game and official announcements for the product boundary; use an independent walkthrough only as a working source, and mark the exact claim as community-reported when it is not confirmed by Bun Muen or Kwalee.
When a decision becomes a defense problem
The official description says that a missed creature can return and force you to board up, set traps, and hide. Once that transition happens, stop trying to complete a normal identity checklist in the same way. Tell teammates what evidence you had and where the threat went. Move to the Survival guidance for door, trap, and hiding decisions. The detective page owns the information failure; it does not pretend that an investigation mistake can be repaired by a single universal button.
Team investigation
Co-op is strongest when players share observations rather than duplicate the same screen. One player can speak to the customer, another can cross-check the computer, and a third can keep the station route clear. The game supports proximity chat, but exact range and the best division of labor need current-build verification. Agree on a short vocabulary—“ID mismatch,” “database clear,” “behavior concern,” “returning threat”—so a teammate can act without hearing an entire story.
Record evidence without guessing
Use a short evidence note after every important check: customer location, ID result, computer result, behavior, and next action. This format is valuable because the station can become noisy and the same player may need to swap from investigation to defense. It also keeps an observation from being promoted into a rule too early. If a clue has only appeared once, label it as observed and include the mode and date.
When several players disagree, return to the three evidence sources rather than voting on a hunch. One player can re-read the ID, another can verify the computer, and a third can watch the customer from a safe angle. The public sources do not publish a complete tell table, so the guide should preserve uncertainty instead of filling it with invented numbers or guaranteed animations.
The same note also helps after a failed shift. Write down whether the team lacked an ID check, a computer comparison, or enough time to watch behavior. On the next run, change that one part of the process and compare the result. A detective guide becomes more durable when it teaches players how to test a clue, not only what conclusion to reach.
Sources and limits
Recommended guides
Choose the guide that matches what you want to do next.
All Detective guides
1 focused guides with steps, checks, and current caveats.