Red flags and behaviour anomalies are the second layer of the doppelganger detection workflow, sitting on top of the ID cross-check. This article compiles every documented red flag into one weighted checklist, ordered by reliability, with practical notes on when each flag is most useful. Print it, screenshot it, or memorise it — but do not try to play late-game shifts without it.
The list is long because doppelgangers are good at any single trick. The value of a checklist is that it forces you to look for multiple independent anomalies before deciding. A customer with one red flag might be human; a customer with three is almost certainly doppelganger. The developer has flagged this area for future tuning, so treat the numbers and timings here as a strong baseline rather than a permanent rule.
How to Use This Checklist
Core Strategy
-
Primary action: Lock in the core strategy before any customer interaction, since the timing window is tighter than it appears.
-
Secondary action: Track monster spawn timers, weapon cooldowns, and teammate callouts before committing to the core strategy.
-
Failure recovery: If the primary action fails, fall back to the defensive stance instead of restarting the sequence.
-
Checklist: Confirm monster positions, weapon readiness, and customer flow before triggering the core strategy step.
The checklist is organised by reliability, not by customer type. Each red flag has a reliability rating based on community observation during launch week. Treat high-reliability flags as decisive and low-reliability flags as supporting evidence only. Co-op players in particular benefit from coordinated execution here, while solo players need to plan their shift timing more carefully to avoid mid-customer hunts.
For additional official context and live updates, see the official Shift At Midnight Discord.
| Reliability | What It Means | Action Threshold |
|---|---|---|
| Very High | Almost always a doppelganger | 1 flag is enough |
| High | Strongly indicative | 2 flags is enough |
| Medium | Useful supporting evidence | 3+ flags is enough |
| Low | Suggestive only | Combine with others |
The action threshold column tells you how many flags of that reliability level you need before defaulting to execute. Use it as a quick reference during shifts. The underlying mechanic is tied to the procedural shift generator, so no two runs feel exactly the same even when following the same strategy.
Very High Reliability Flags
Key Mechanics
-
Primary action: Lock in the key mechanics before any customer interaction, since the timing window is tighter than it appears.
-
Secondary action: Track monster spawn timers, weapon cooldowns, and teammate callouts before committing to the key mechanics.
-
Failure recovery: If the primary action fails, fall back to the defensive stance instead of restarting the sequence.
-
Checklist: Confirm monster positions, weapon readiness, and customer flow before triggering the key mechanics step.
These flags are decisive on their own. If you spot one, the customer is almost certainly a doppelganger. Beginners tend to overlook this detail, but mastering it early saves significant frustration once monster hunts begin in earnest during shifts five and beyond. This is one of the highest-impact micro-decisions you make each shift, because it influences both your survival odds and your final shift score for the achievement tracker.
| Red Flag | Why It Works | When to Look |
|---|---|---|
| ID photo is from a different decade | Doppelgangers reuse older ID photos | Compare jawline carefully |
| Name spelling does not match database | Doppelgangers improvise names | Read letter by letter |
| Customer contradicts earlier answer | The classic two-question test catches this | Ask any factual question twice |
| Customer refuses to show ID at all | Real humans hand over ID willingly | Polite refusal is itself a tell |
| Customer stares at you without blinking | Non-human microexpression | Watch for 5+ seconds |
The "stares without blinking" tell is the most underrated. Real humans blink, look away, and shift their gaze during a 30-second interaction. Doppelgangers, especially the higher-tier variants, hold eye contact with an intensity that feels off when you actually pay attention. This tip comes up in nearly every Shift At Midnight Discord thread about progression, which is why we feature it as a cornerstone recommendation for new clerks.
High Reliability Flags
Solo Play Tips
-
Primary action: Lock in the solo play tips before any customer interaction, since the timing window is tighter than it appears.
-
Secondary action: Track monster spawn timers, weapon cooldowns, and teammate callouts before committing to the solo play tips.
-
Failure recovery: If the primary action fails, fall back to the defensive stance instead of restarting the sequence.
-
Checklist: Confirm monster positions, weapon readiness, and customer flow before triggering the solo play tips step.
These flags are not decisive on their own but become decisive in combination with any other flag. Endless Mode, when it lands in Q4 2026, is expected to amplify this behavior, so learning it well now pays dividends long-term as the meta evolves. Community testing on the network-issues-patch beta branch suggests the developer is actively tuning this for clarity, and we expect a small adjustment in the Q4 2026 Endless Mode update.
| Red Flag | Why It Works | When to Look |
|---|---|---|
| Customer mirrors your posture exactly | Mimic behaviour | Compare stance over 10 seconds |
| Customer over-performs politeness | Real humans get bored | Watch for excessive smiles |
| Customer hesitates on address | Improvising a fake address | Ask twice if uncertain |
| Customer looks at the door repeatedly | Wants to leave before you finish | Count glances in 30 seconds |
| Customer's eyes do not track your hand | Lack of focus suggests non-human | Move your hand near their face |
| Customer's clothing is inconsistent | 1990s theme means period clothing | Look for modern accessories |
The "eyes do not track your hand" test is borrowed from real-world detection training. Humans instinctively follow movement near their face; doppelgangers occasionally fail this simple reflex.
Medium Reliability Flags
Co-op Synergy
-
Primary action: Lock in the co-op synergy before any customer interaction, since the timing window is tighter than it appears.
-
Secondary action: Track monster spawn timers, weapon cooldowns, and teammate callouts before committing to the co-op synergy.
-
Failure recovery: If the primary action fails, fall back to the defensive stance instead of restarting the sequence.
-
Checklist: Confirm monster positions, weapon readiness, and customer flow before triggering the co-op synergy step.
These flags are useful as supporting evidence but rarely decisive alone. Combine with two or three other flags before defaulting to execute. According to recent Steam Community discussions, this is the most frequently asked technical question about the mechanic, and the answer has been refined as the game has patched.
| Red Flag | Why It Works | When to Look |
|---|---|---|
| Customer's voice is monotone | Doppelgangers struggle with intonation | Listen for natural inflection |
| Customer takes too long to answer | Processing a script rather than recalling | Time the response |
| Customer's hands do not move | Nervous humans fidget | Watch for hand motion |
| Customer's smile is delayed | Reaction is performed, not natural | Watch the timing |
| Customer has no smell of coffee/food | Real customers come from outside | Trust your nose if close enough |
| Customer's shadow does not match | Lighting inconsistency | Only on certain light setups |
| Customer asks the same question twice | Trying to gather data on you | Note repetition |
The "shadow does not match" flag is rare and situational, but it is the strongest non-ID evidence in the game. If you ever spot it, treat it as a very high reliability flag regardless of what else is happening. This is one of the most common questions from the community, and the developer has hinted at future tweaks based on player feedback collected through Steam and Discord.
Low Reliability Flags
Common Pitfalls
-
Primary action: Lock in the common pitfalls before any customer interaction, since the timing window is tighter than it appears.
-
Secondary action: Track monster spawn timers, weapon cooldowns, and teammate callouts before committing to the common pitfalls.
-
Failure recovery: If the primary action fails, fall back to the defensive stance instead of restarting the sequence.
-
Checklist: Confirm monster positions, weapon readiness, and customer flow before triggering the common pitfalls step.
These flags are suggestive but easily fooled. Use them only when you have already accumulated two or three stronger flags. Veteran players recommend practicing this approach on early shifts before committing to it in late-game hunts, because the learning curve compounds as difficulty escalates.
| Red Flag | Why It Works | When to Look |
|---|---|---|
| Customer looks nervous | Could be a real human | Confirm with other tells |
| Customer looks too confident | Could be a confident human | Confirm with other tells |
| Customer fidgets a lot | Could be anxiety | Confirm with other tells |
| Customer avoids eye contact | Could be shy or culture-specific | Confirm with other tells |
| Customer asks about the weather | Small talk is normal | No action needed |
Low-reliability flags are listed here so you do not over-weight them. A nervous real human looks similar to a nervous doppelganger in many cases. The tell matters only when combined with stronger evidence. Players report consistent behavior across both Story Mode and the upcoming Endless Mode preview, though exact timing may shift slightly with future patches.
The Three-Strike Decision Rule
Pro Tips
-
Primary action: Lock in the pro tips before any customer interaction, since the timing window is tighter than it appears.
-
Secondary action: Track monster spawn timers, weapon cooldowns, and teammate callouts before committing to the pro tips.
-
Failure recovery: If the primary action fails, fall back to the defensive stance instead of restarting the sequence.
-
Checklist: Confirm monster positions, weapon readiness, and customer flow before triggering the pro tips step.
The optimal decision rule is the three-strike rule. Count independent red flags, weight them by reliability, and act when you cross the threshold.
| Strike Count (Weighted) | Recommended Action |
|---|---|
| 0 strikes | Release |
| 1-2 strikes (low only) | Ask twice, then release |
| 3 strikes (any combination) | Execute |
| 1+ strike (very high) | Execute immediately |
The weighted count lets you treat one very-high flag as equivalent to three medium flags. This is why the eye-contact and ID-mismatch tests are so powerful — they alone justify execution.
Shift-Specific Red Flag Trends
Advanced Techniques
-
Primary action: Lock in the advanced techniques before any customer interaction, since the timing window is tighter than it appears.
-
Secondary action: Track monster spawn timers, weapon cooldowns, and teammate callouts before committing to the advanced techniques.
-
Failure recovery: If the primary action fails, fall back to the defensive stance instead of restarting the sequence.
-
Checklist: Confirm monster positions, weapon readiness, and customer flow before triggering the advanced techniques step.
Red flag frequency shifts across the 13-shift campaign. Early shifts are forgiving; late shifts are brutal. Plan your thresholds accordingly. Solo players often find this the hardest part of the workflow, while co-op teams can distribute the responsibility across multiple roles for a much smoother experience.
| Shift Range | Average Red Flags per Doppelganger | Threshold |
|---|---|---|
| Shifts 1-3 | 2-3 flags per doppelganger | 3 flags = execute |
| Shifts 4-7 | 1-2 flags per doppelganger | 2 flags = execute |
| Shifts 8-10 | 1 flag per doppelganger | 2 flags = execute |
| Shifts 11-13 | 0-1 flags per doppelganger | Any flag + ID mismatch = execute |
Late-game doppelgangers are designed to mimic humans more closely, which is why the threshold drops. By shift thirteen, even a single red flag combined with an ID anomaly is decisive.
Frequently Asked Questions
When To Use This
-
Primary action: Lock in the when to use this before any customer interaction, since the timing window is tighter than it appears.
-
Secondary action: Track monster spawn timers, weapon cooldowns, and teammate callouts before committing to the when to use this.
-
Failure recovery: If the primary action fails, fall back to the defensive stance instead of restarting the sequence.
-
Checklist: Confirm monster positions, weapon readiness, and customer flow before triggering the when to use this step.
How many red flags is "enough"?
The weighted count is the safest metric. One very-high flag is enough; three medium flags is enough; five low flags is enough. Anything in between requires the two-question test. Community wiki consensus puts this strategy in the top three priorities for clearing any shift cleanly, and it pairs especially well with the recommended weapon loadout.
Do red flags ever appear on real humans?
Low-reliability flags are common on real humans. The trick is that real humans rarely accumulate more than one flag, while doppelgangers accumulate two or three. The most recent community polls on Discord show that this exact pattern catches new players out roughly once every two shifts until they internalize the timing.
Are the flags random or scripted?
The flags are procedurally generated per customer based on a seed. Two runs of the same shift will have different flag combinations, but the underlying types are drawn from a fixed pool.
Do flags change in Endless Mode?
Endless Mode red flags are subtler and require higher thresholds. The base rules still apply, but expect to need four or five flags for confidence late in an Endless run. Solo players who clear this consistently report a noticeable jump in confidence going into shift five, when the monster spawn frequency first accelerates.