When a customer arrives in Shift At Midnight, the fastest safe action is not an immediate verdict. The official Store description presents a three-part check: examine the ID, cross-check the details in the computer, and observe behavior. Use that order to create a record you can defend. If you skip the middle step because the customer looks normal, the later return of a creature can cost more time than the check saved.
First pass: read the ID
Read every field the interface makes available. Do not assume the portrait, name, or one unusual detail is the answer by itself. The purpose of the first pass is to identify what the game expects you to compare. If the customer is asking for service while the ID is open, keep track of whether the current prompt changes; a visual mismatch and a prompt mismatch are different observations.
Before you leave the interaction, repeat the important field in your own words or tell a teammate. This is especially useful in co-op, where another player may be looking at a different part of the station. Keep the wording factual: “the date displayed on the card is X” is better than “this customer is definitely fake.”
Second pass: use the computer
Move to the computer only after you know which identity details need checking. Compare the record that the game exposes with the ID rather than searching randomly. If the database returns a result that looks incomplete, treat the missing information as a reason to investigate further, not automatic proof of a threat. The public evidence confirms the computer cross-check but does not document every possible database state.
Return to the customer through the same recognizable route. A direct line that passes behind a door or through a cramped corner may be faster on a calm shift and worse when a creature is active. Learning the safe route now makes the later Survival decision less frantic.
Third pass: observe behavior
Watch what changes while you interact. Ask the available questions or follow the current prompt, then compare the behavior with the ID and database result. Avoid a one-clue rule. A character’s appearance can create suspicion, but the public Store page does not promise that any single hairstyle, outfit, answer, or animation is a complete identification method.
If you are testing a behavior clue, keep the shift, branch, and date with the result. A community video or guide can reveal a useful hypothesis, but label it as working-source information until the released Steam build confirms it. Never copy a list of monster tells from the separate Multiplayer Demo without checking whether the base game exposes the same information.
Decision and recovery
Once the available checks point in one direction, make the decision the current interaction requests and immediately note what happened. If the customer leaves and the game later signals a threat, tell teammates which part of the check was uncertain. Do not spend the next minute arguing from memory while the station becomes unsafe. Move to the barricade, trap, and hiding route appropriate to the current defense phase.
If the check was correct, keep the same record as a successful sample. A success is evidence of that context, not proof that every future customer with the same surface detail is identical. The game uses randomly generated shifts, and official updates have changed enemies, lobby behavior, and fixes since release.
If the result is uncertain
Uncertainty is a useful state. Keep the customer in view, state which check is missing, and avoid sending the whole team into the same small space. If the customer leaves before the team decides, report the last location and switch to the Survival route only when the game indicates that a creature has escaped. After the shift, record the missing evidence so the next attempt tests one question rather than repeating the whole run blindly.