The Review Decision No One Documented
In discovery, the decision may be reasonable — but if no one can explain it later, the risk grows.
The review team made the call quickly. A group of documents was marked not responsive, a few borderline items were moved out of the production set, and the matter continued forward. At the time, the decision made sense. The team understood the issue, the documents seemed outside the scope, and the deadline did not leave much room for long discussion.
Months later, the same decision came back into focus. Opposing counsel asked why certain documents were excluded. The issue itself was not unusual. What made the moment difficult was that no one could clearly explain the reasoning. The people involved remembered the decision generally, but there was no clear note, no documented standard, and no easy way to show how the call had been made.
Reasonable Decisions Still Need an Explanation
In discovery, not every decision will be perfect, and courts generally understand that. What matters is whether a decision was reasonable when it was made and whether the team can explain the process behind it. A defensible decision is not only about the outcome. It is about the reasoning that supports the outcome.
Problems arise when review teams make judgment calls under pressure without leaving a clear record. This often happens in fast-moving matters where everyone is focused on keeping production on schedule. But when questions come later, memory is not enough. A decision that was reasonable at the time can look uncertain if there is no documentation to support it.
A decision that was reasonable at the time can look uncertain if there is no documentation to support it.
Documentation Protects the Process
Documenting review decisions does not have to be complicated. It can be as simple as noting the issue, the standard applied, who made the decision, and why that approach was chosen. These small records create a trail that helps the team explain itself later if the decision is challenged.
The strongest review workflows build documentation into the process rather than treating it as extra work. They include escalation paths, issue logs, quality checks, and clear guidance for borderline calls. This helps reviewers stay consistent and gives the legal team confidence that decisions were made thoughtfully, not casually. In discovery, a good record often protects a good decision.
The review decision no one documented may not feel important in the moment. But when it is questioned later, the absence of an explanation can become the problem.
At Sovereign Discovery, we focus on review workflows that do more than move documents from one stage to the next. We help legal teams build processes that can be explained clearly when scrutiny arrives. Because in discovery, defensibility is not created after the question is asked. It is built into the process from the beginning.