He asked for the company database to prove his case. The court said no.
A UK employee wanted access to his employer's entire database to show job vacancies existed. The Court of Appeal refused, citing proportionality.
Denied.
Database locked.
Proportionality rule.
A UK employee wanted access to his employer's entire database to show job vacancies existed. The Court of Appeal refused, citing proportionality.
He needed the company's database to prove there were job openings. The court called his request 'doubtful legal merit' and shut it down.
The database sat on Bass Taverns' servers. Robert Kouzaris could not touch it. He believed it held the proof he needed — records showing job vacancies existed at a specific time. Without those records, his case against his former employer could not move. So he asked the court to force Bass Taverns to hand over the entire database. Every record. Every field. Every entry. The UK Court of Appeal refused.
The courtroom fell silent as the ruling was read. The judge had removed his glasses, setting them on the bench with a soft click. The printed discovery motion — forty pages of argument — lay untouched on the clerk's desk. The database, the court had decided, would stay locked behind the employer's server room door.
When the evidence is locked behind a server
Kouzaris was a former employee who believed he had been wronged. He wanted to recover something — money, a position, or both. The proof, he argued, was hiding inside the company's electronic records. If Bass Taverns had job openings on a certain date, that fact could help his claim.
So he filed a motion for discovery (a formal request asking the court to order the other side to produce documents or data). He wanted the court to compel Bass Taverns to hand over its entire database — every record, every entry, every field — so he could search for the vacancies himself.
It was a broad request. The court noticed.
The motion itself was a thick sheaf of paper, stapled and tabbed, arguing that the database was the only source of truth. Without it, Kouzaris said, his claim would collapse. The employer's lawyers sat across the aisle, their own response brief already filed — a shorter document, but heavy with objections.
What each side said
Kouzaris' argument was simple: the employer controlled the data, and the data was relevant to his case. Without access to the database, he could not prove the vacancies existed. Bass Taverns had the keys to the evidence room. The court, he said, should order them to unlock it.
The employer pushed back. A company database is not a single document or a folder of emails. It is a living system containing years of transactions, employee records, financial data, and operational logs. Handing over the entire database would mean extracting, copying, and reviewing potentially millions of records — many of them irrelevant, some of them commercially sensitive. The server room hummed with the weight of that data, row after row of blinking lights, each drive holding years of business history. To copy it all for one employee's claim would be a monumental task.
The court had to decide: was Kouzaris' need for the data strong enough to justify the cost and disruption of handing over the entire database?
The court's answer
The UK Court of Appeal applied a principle that governs discovery in modern litigation: proportionality (the idea that the cost and effort of producing evidence must be balanced against its actual importance to the case).
The reasoning was blunt. The court described Kouzaris' request as having "doubtful legal merit" — meaning the connection between the database and his claim was too weak to justify the burden of production. Then it laid down the test that every litigant must now meet when seeking discovery of large datasets: there must be a balance between "the nature and volume of the data requested to be preserved and its importance and position in the potential trial."
In plain terms: the bigger the data request, the more relevant the evidence must be. A fishing expedition — asking for everything in the hope that something useful turns up — would not pass muster.
The judge's glasses sat on the bench as the full judgment was delivered. The silence in the courtroom stretched as each word of the proportionality test was read aloud. The clerk made a note. The database would not be touched.
Understanding proportionality in discovery
The ruling in Robert Kouzaris v. Bass Taverns Ltd is not just about one employee's failed request. It establishes a framework that applies to every case where digital discovery is sought. The court did not say that databases can never be produced. It said that the request must satisfy a two-part test:
First, the evidence sought must be clearly relevant to the case — not merely speculative or tangential. Kouzaris believed the database would show job vacancies, but he could not demonstrate a direct link between those vacancies and his claim. The court saw this as a weak connection, one that did not justify the burden of production.
Second, the burden of producing the data must be proportionate to its importance. A company database is not a single email or a folder of documents. It is a complex, interconnected system. Extracting relevant records from such a system requires time, expertise, and money. The court weighed these costs against the value of the evidence and found the balance tipped against production.
This two-part test is now the standard. Any litigant seeking discovery of a large dataset must be prepared to argue both relevance and proportionality. A vague assertion that "the data might contain something useful" will not suffice.
The practical implications for litigants
For employees and claimants, the message is clear: do not assume that the court will order the other side to hand over entire databases. Before filing such a request, you must be able to point to specific records or categories of data that are directly relevant to your case. You must also be prepared to address the burden of production — perhaps by proposing a narrower request, such as a targeted search using specific keywords or date ranges.
For employers and defendants, the ruling offers protection. A company database contains sensitive commercial information that should not be exposed to a fishing expedition. If a discovery request is too broad, you can argue proportionality and ask the court to refuse or limit the request.
For both sides, the lesson is the same: discovery in the digital age requires precision. The days of asking for everything and sorting it out later are over. The court will weigh the request against the burden, and if the balance is wrong, the request will be denied.
The broader message for the legal system
The Kouzaris ruling reflects a growing awareness in courts around the world that digital evidence presents unique challenges. Data is cheap to store but expensive to produce. A single company database can hold terabytes of information — millions of pages of records. To require production of all of it for a marginal claim would be wasteful and unjust.
The principle of proportionality is the court's answer to this challenge. It ensures that the cost and effort of discovery do not outweigh the benefits. It protects litigants from burdensome requests that are not truly necessary. And it preserves the integrity of the judicial process by focusing on evidence that actually matters.
The UK Court of Appeal's decision in Robert Kouzaris v. Bass Taverns Ltd is a reminder that the law must adapt to technology — but not at the expense of fairness. The database stayed where it was. The employee's theory stayed unproven. The court's message stayed clear: proportionality is not a suggestion. It is the gatekeeper.
THE PLAY: Before filing a discovery request for a large dataset, map out exactly which records are needed and why — and be prepared to show the court that the burden of production is proportionate to the importance of the evidence.
The server room door remained closed. The printed motion sat in the case file, now stamped "Refused." The judge's glasses were back in their case. The silence in the courtroom had given way to the shuffle of papers and the low murmur of lawyers packing their bags. The database, with all its secrets, stayed where it belonged — with the employer who owned it.