The judgement in Dead by Daylight comes out during the end-of-trial sequence, after the final survivor is sacrificed, escapes, or the match timer expires. The game tallies bloodpoints from four categories, applies multipliers and event bonuses, then displays the results screen. On PC and current consoles that handoff typically takes 5–15 seconds, though server load and platform can stretch it longer.
That short answer hides a longer pipeline. Understanding what happens between the final hook and the results screen explains why your point total sometimes looks wrong, why the "judgement" can feel delayed, and what you can actually control. This explainer walks through the scoring architecture, the match-end flow, and the edge cases that trip up even experienced players.
What the judgement actually is
"Judgement" in Dead by Daylight is community shorthand rather than an official term. Players use it to describe the moment the game evaluates their performance and awards bloodpoints, the currency that feeds the bloodweb progression system. The evaluation is not a single event. It is a running tally that finalizes when the trial ends.
The game tracks four scoring categories continuously during play. Survivors earn points for objectives, survival, altruism, and boldness. Killers earn points for brutality, hunter, deviousness, and sacrifice. Each category caps at 8,000 bloodpoints per trial under standard rules, giving a theoretical 32,000-point ceiling before multipliers.
The final "judgement" display is where those four categories are summed and converted into progression currency. It appears on the results screen, not mid-match. A common misconception is that the judgement arrives the instant the last survivor dies. In practice, the game must close the trial instance, reconcile the score, and transmit results to the player's profile before anything displays.
The scoring engine behind the results
Bloodpoint scoring is event-driven. Every action that earns points fires a scoring event into a running ledger tied to your player entity for that trial. Repairs, chases, unhooks, pallet stuns, and generator progress all generate discrete events with fixed point values. The engine does not wait until the end to calculate. It accumulates in real time.
This architecture matters because it explains partial credit. If you disconnect mid-trial, the ledger usually retains the points already banked, which is why disconnects sometimes still show a reduced results screen. The category caps are enforced continuously, so once you hit 8,000 in a category, further qualifying actions in that category stop adding value. Players who "waste" actions after capping a category are not losing earned points, but they are not gaining either.
Multipliers apply at settlement, not at event time. Bloodpoint offerings, event bonuses, and certain perks that modify point gain are layered onto the category totals when the trial closes. This ordering is why a 100% bonus offering doubles the final category sums rather than each individual event. The distinction rarely changes the total, but it does change how the results screen animates the tally, which is why some players perceive a "delay" between match end and the bonus appearing.
The match-end pipeline, step by step
The sequence between the final hook and the visible results screen follows a predictable order. The table below maps the stages and rough timing on a healthy connection.
| Stage | What happens | Typical duration |
|---|---|---|
| Trial closure | Last survivor removed or timer expires | Instant |
| Score reconciliation | Category ledger finalized and caps applied | Under 1 second |
| Multiplier settlement | Offerings and event bonuses applied | Under 1 second |
| Server transmission | Results posted to profile service | 2–10 seconds |
| Client display | Results screen renders with animation | 1–3 seconds |
| Progression update | Bloodpoints credited, bloodweb refreshed | 1–5 seconds |
Most players experience the whole handoff in under 15 seconds. The variable stage is server transmission, which depends on platform backend load. During events with high concurrent player counts, that stage can stretch to 20–30 seconds. If the client loses connection during transmission, the results screen may fail to render even though the server recorded the trial, a discrepancy that shows up as "missing" bloodpoints that later reconcile.
A counterintuitive detail: the game sometimes displays the results screen before the profile service has confirmed the credit. The visible tally and the stored total can diverge for a few seconds. Refreshing the bloodweb immediately after a match occasionally shows a stale balance. Closing and reopening the menu forces a resync.
Where the timing estimate breaks down
The 5–15 second figure is a central estimate, not a guarantee. Several conditions push the judgement outside that window.
Server-side event load: during seasonal events, backend queues lengthen and transmission can double. Platform certification delays: console storefront integrations occasionally add latency to profile writes. Connection quality: a degraded uplink can stall the transmission stage without dropping the match entirely. Disconnect edge cases: a disconnect near trial end may settle as a partial result or fail to display at all.
If the results screen has not appeared after roughly 60 seconds, the trial has almost certainly settled server-side and the client is the problem. Restarting the game forces a fresh profile fetch and usually reveals the credited points. Do not assume the match was lost. The server ledger is authoritative, and the client display is a view onto it.
Common misconceptions about the judgement
The most persistent myth is that the judgement is calculated after the match rather than during it. Players sometimes believe that leaving early or playing passively until the end preserves points. In reality, points accrue in real time, and the end-of-trial step only sums and multiplies what already exists. Playing passively earns nothing to sum.
A second misconception concerns the category caps. Some players believe hitting the 8,000 cap in one category redirects overflow into another. It does not. Each category is capped independently, and overflow is simply lost. A survivor who maxes objectives early gains nothing from additional generator work beyond the cap.
A third myth is that the results screen total equals the bloodpoints added to your balance. Offerings, event multipliers, and progression bonuses can make the credited amount higher than the displayed base tally. Conversely, some limited-time modifiers reduce gain. The displayed number and the balance change are related but not identical, which fuels confusion when players check their totals afterward.
Practical steps to read your results correctly
You can reduce ambiguity around the judgement with a few habits. These steps target the information gaps that cause most confusion.
Wait for the full results animation before checking your balance, since the credit can lag the display. Screenshot the results screen if you suspect a discrepancy, because the server record is what support will reference. If the screen never appears, fully restart the client rather than re-queuing, which forces a profile resync. Track your pre-match balance so you can compute the actual credited amount, not just the displayed tally. Avoid disconnecting near trial end if you want a clean results record, since partial settlements are harder to verify.
The threshold that matters most is the 60-second mark. Under a minute, waiting is reasonable. Beyond a minute, the client is the likely fault point, and a restart is the reliable fix.
What the timing cannot tell you
The judgement timing says nothing about matchmaking quality or your skill rating. Dead by Daylight uses separate systems for scoring and matchmaking, and the results screen reports only the former. A fast judgement does not mean a good match, and a slow one does not mean a bad one.
The pipeline also cannot be used to infer server health reliably. Transmission latency spikes during events are normal and expected, not evidence of infrastructure failure. Conversely, a fast judgement on a degraded connection is possible if the transmission stage happens to route cleanly.
Finally, no public authoritative source documents the exact internal timing thresholds, because the developer does not publish them. The ranges here reflect observed behavior and community measurement, not an official specification. Treat any specific millisecond figure as an estimate rather than a guarantee. For current details on events, bonuses, and platform-specific behavior, consult the game's official patch notes, which are the only authoritative record of changes to the scoring and settlement systems.