THE RECEIPTS
Overwatch Scoreboard Explained
Final scoreboard stats are useful summaries. Read them together, compare like with like, and do not ask them to testify about moments they never recorded.
Each column is a match total: eliminations, assists, deaths, damage, healing and mitigation. Read them together, compare players in the same role, and treat the board as clues, never as a replay.
How to read a final scoreboard
A final scoreboard collects visible totals from the whole match. That makes it useful for a quick relative comparison: which team line was ahead or behind, which player had a notably high death count, and whether several recorded fields point in the same direction. It is not a complete match report.
The most reliable way to start is simple: compare players with relevant teammates, look at multiple fields together, and remember the role attached to each line. A huge number in one column is not a universal verdict. A pattern across several columns is more informative, but still limited to what the board displays.
Common scoreboard stats
| Stat | Most useful for |
|---|---|
| Eliminations | Involvement in fights, all roles |
| Assists | Team play, especially supports |
| Deaths | Survival, all roles |
| Damage | Damage players and tanks |
| Healing | Supports |
| Mitigation | Tanks and some other heroes |
Eliminations
Eliminations show the recorded elimination total for a player. They can be a useful part of a broad contribution comparison, especially beside assists, deaths, and role-relevant output. On their own, they do not show the order of events, the decisive target, or the value of a particular elimination.
Assists
Assists show recorded credit alongside eliminations. They can add useful context to a player’s visible involvement, particularly when compared with nearby teammates or an equivalent enemy role. Like every final total, they do not describe timing, positioning, or the conditions around the recorded event.
Deaths
Deaths are often the most immediately useful survival signal. A player with substantially more deaths than relevant teammates, especially alongside weak recorded output, may stand out on a final board. The number cannot explain why those deaths happened, so it works best as part of a wider scoreboard pattern rather than as a standalone accusation.
Damage
Damage is the total shown on the final board. It can help compare players in similar roles and can be read with eliminations, assists, and deaths. It does not tell you how that damage was distributed or which moments mattered most, so “most damage” is not a complete answer to who contributed most.
Healing
When healing is visible, it records the total displayed for that player. It is meaningful support-line context, especially when read with assists, deaths, damage, eliminations, and an equivalent enemy support line. It should not be used as the only measure of a support player or compared directly with a damage total from another role.
Mitigation
When mitigation is shown, it is additional context for roles that can produce it. It can help describe a visible tank line alongside survival, combat output, eliminations, and assists. It is not a universal scoreboard field and should not become a single-number substitute for the rest of the board.
Other visible fields
Some scoreboards may show additional role-specific or version-specific fields. Read any of them the same way: as recorded totals that gain meaning through role-aware comparison, not as a complete explanation of a match.
Why comparing absolute numbers across roles misleads
Roles do not have the same visible responsibilities or the same scoreboard columns. A support’s healing does not answer the same question as a damage player’s damage. A tank’s mitigation should not be treated as a direct rival to either. Even within one role, a useful comparison should include more than one field and should account for survival.
A practical scoreboard review compares tanks with tank context, damage players with damage context, and supports with support context. Enemy players in the equivalent role can be a helpful benchmark, but they are still only a reference for the final totals. A matchup on the board does not reveal the unseen details that produced it.
Common mistake: reading “most damage” as “best player”. Damage without survival or role context is only one column.
What the scoreboard does NOT tell you
The final scoreboard does not reveal positioning, ultimate timing, communication, target priority, decision-making, objective play, fight timing, rotations, peel, space creation, or clutch moments. It cannot show every missed shot or every strong choice. It cannot prove intent, responsibility for a particular lost fight, or which teammate was “actually bad.”
- Match totals per player
- Relative gaps between players
- Survival compared with teammates
- Positioning and timing
- Ultimate usage and target choice
- Communication or intent
That is not a flaw in the scoreboard; it is a limit of a final-total summary. Use the board to identify visible patterns and questions. Use a replay, a conversation, or a quieter next match for anything that requires more context.
A better post-match habit
- Your deathsCompared with teammates and the enemy in your role.
- Your role outputThe columns that matter for your role.
- The patternClear and repeated, or flat and mixed?
Start with your own line. Check deaths, role-relevant output, eliminations and assists, then compare with teammates and equivalent enemy roles. If the pattern is clear, you have a useful scoreboard observation. If it is flat or mixed, the honest conclusion may be that the final board does not produce one obvious answer.
Let the court read the receipts
DidIThrow is an entertainment-oriented final-scoreboard court. Upload the board, review a role-aware comparison of the visible stats, and get a playful verdict that stays attached to that match. No invented match footage. No secret knowledge. Just the numbers, a fake judge, and a suspiciously confident stamp.