Direct answer

Check in this order

  1. Confirm the ID has a barcode and plausible details.
  2. Search the NET database and compare name, date and status.
  3. Compare the person with the photo, skin tone and facial marks.
  4. Ask identity questions and compare the answers with the record.
  5. Make the decision before the customer completes the transaction.

Signal reliability

HIGH

Database says deceased

A living visitor attached to a deceased record is a direct identity conflict. Re-check the record spelling, then treat it as strong evidence.

HIGH

ID or photo mismatch

A missing barcode, wrong skin tone or facial mark on the wrong side is stronger than general body language.

HIGH

Answers conflict

Job, date or identity answers that disagree with the ID/NET record add an independent confirmation.

LOW

Nervous behavior

Use behavior as a prompt to investigate, not a verdict. Humans can be awkward and familiar customers still require a new check.

Randomization warning: the Story Mode shifts are officially described as randomly generated. A permanent face-only cheat sheet can therefore create false positives. Use the interactive checker with the current record.

Decision matrix

ObservationWeightNext action
NET record matches and photo/details matchLow suspicionFinish the remaining question check; do not skip it because the face is familiar.
Missing barcode or photo detail conflictHigh suspicionRe-read the ID and confirm a second independent mismatch.
NET details conflict or the record says deceasedHigh suspicionVerify spelling and fields, then treat the conflict as decisive evidence.
Answer disagrees with the recordHigh suspicionCompare the exact fact instead of judging tone or hesitation.
Nervous or unusual behavior onlyLow confidenceInvestigate further; behavior alone is not a reliable execution rule.

Fast 20-second re-check

  1. Read the name from the ID and search that exact record.
  2. Match the highest-signal physical detail visible in both the photo and person.
  3. Ask one question whose answer is explicitly stored in NET.
  4. If one clue conflicts, stop and confirm another channel before acting.
  5. If the evidence agrees, finish the transaction without inventing a tell.
Why evidence stacking works: the official description explicitly separates ID examination, computer cross-checking and behavioral observation. Using more than one channel follows the designed investigation loop.

Quick answers

Frequently asked questions

Can a familiar customer be a doppelganger?

Yes. Re-check every appearance because the official game description says shifts are randomly generated.

Is nervous behavior enough to shoot?

No. Treat behavior as a reason to check the ID, NET record, visible details and answers—not as a verdict.

What is the strongest clue?

A direct identity conflict such as a mismatched record, photo detail, answer or deceased status is stronger than general behavior.

Source register

Evidence used on this page

  1. Official Shift At Midnight Steam pageOfficial game features, modes, platforms, system requirements and roadmap. Retrieved 2026-08-01.
  2. AllThings.How doppelganger identification guideSecondary documentation of launch-version checks and named copies; re-check after patches. Retrieved 2026-08-01.