Tarkov death review: five questions after every raid

Escape from Tarkov Guide 5 min read

Version basis: written 2026-08-23, against patch 1.1.0.0 of 3 August 2026 and Season 1: KORD BREACH. This page describes a review habit, not game data. It contains no numbers that a patch can invalidate, and that is deliberate.

Spend sixty seconds after each death answering five fixed questions. The reason new players plateau is not reflexes; it is that deaths arrive as a blur of bad luck and never get sorted into categories, so the same mistake happens forty times and reads as forty different mistakes.

The five questions

Ask them in this order, immediately, before queueing again. Order matters, because the early questions usually make the later ones unnecessary.

  1. Where was I, exactly? If you cannot name the location, the cause is orientation, and no other answer on this list matters yet.
  2. Did I know a fight was possible there? Surprised or not surprised is the biggest single split in this list.
  3. Was I moving, looting or standing still? Most deaths cluster into one of these for any given player, and the cluster is your actual weakness.
  4. What would have prevented it — position, patience or gear? Be honest. Gear is the answer far less often than it feels.
  5. Was I still in the raid for a reason? If you had already met your objective, the death was free and entirely avoidable.

Mapping the answer to a correction

Each cause has exactly one correction. Doing the matching correctly is the whole value of the exercise.

Cause identifiedThe correctionNot the correction
Could not name the locationRun orientation raids on that map with a throwaway kitBuying better armour
Surprised in a known hot areaApproach it differently, or stop approaching itPlaying faster to “get there first”
Died while lootingLoot in cover, and loot less per stopA bigger backpack
Died standing still in the openMove between covers, never across themBetter optics
Died after the objective was doneLeave when the objective is doneAnything else at all

The right-hand column is there because those are the corrections players actually make. All of them cost money and none of them address the cause.

The weekly pass

Once a week, look at the whole set of debriefs together rather than one at a time. Individual deaths are noisy; the pattern is not.

  • If most deaths share a map → you have a map problem, and the fix is deliberate learning raids rather than more raids.
  • If most deaths share a phase of the raid — early, mid, extract — → you have a timing habit, usually extracting too late.
  • If most deaths share an activity — always while looting, always while pushing → that activity needs a rule, not more practice.
  • If deaths are genuinely scattered → you are probably fine and just playing a game where people die. Stop optimising and play.
  • If the same task appears in three or more deaths → the task is the problem, not you. Do it with a different route or a different time of raid.

Two failure modes of reviewing

Reviewing too much. A sixty-second debrief works because it is short enough to actually do after every raid. A ten-minute analysis gets skipped after the third one, and a habit you skip teaches nothing.

Reviewing for blame. The question is never whether the death was fair. It is whether the death is repeatable, and repeatable deaths are the only useful kind. A player who killed you from a position you did not know existed has handed you a free piece of map knowledge, provided you write down the position instead of the grievance.

Review time is also raid time you are not spending, which matters if you are on a seasonal character with a deadline. The season time planner prices your remaining weeks in raids, and a minute per raid is a rounding error against the raids a fixed habit saves. If your run’s modifiers are what keeps producing the same death, that is a different problem, and the modifier trade-off scorer is where to take it.

What this framework does not do

  • It does not tell you who killed you or how. The kill screen gives less information than people assume, and reconstructing a fight from it is mostly invention.
  • It does not use statistics. Survival rate percentages are a poor guide at low raid counts, and comparing yours against numbers quoted in threads compares two different populations.
  • It does not recommend gear. By design — see the right-hand column of the table.

Sources