Dawn Raid Aftermath: Reviewing Seized Data When In-House Privilege Does Not Apply

A dawn raid ends when the inspectors leave. The work it creates is only beginning.

European Commission officials arrive without notice, image laptops and mailboxes, and depart with a copy of a substantial slice of your client's business records. What follows is a review exercise with an unusual property: the ordinary assumptions your team carries about privilege may not hold. Teams trained in common law jurisdictions often discover this late, and the discovery is expensive.

The pace of inspection activity makes this more than a theoretical concern. European competition authorities carried out 17 dawn raids in the fourth quarter of 2025 alone, according to White & Case's Dawn Raid Analysis Quarterly, with the Commission accounting for two of them and national authorities the balance. Each of those raids produced a data set that somebody had to review under EU rules, quickly, and without the safety net most in-house teams assume they have.

The privilege rule that catches teams off guard

In EU competition proceedings, legal professional privilege does not extend to communications with your in-house lawyers.

This is not new law, but it remains the single most misunderstood feature of an EU investigation. The Court of Justice set the rule in AM&S Europe v Commission in 1982 and confirmed it in Akzo Nobel v Commission in September 2010. The reasoning turns on independence. An in-house lawyer, however senior, however carefully enrolled with a bar, remains an employee. The Court held that an employment relationship is incompatible with the independence that privilege requires.

The practical consequence is blunt. An email in which your general counsel gives considered legal advice on the exact conduct under investigation is, in the Commission's hands, an ordinary business document.

Recent litigation has tested the boundary without moving it. In August 2026, the President of the EU General Court refused Broadcom's application to suspend a Commission decision requiring production of documents in the investigation into its software licensing practices. The order reaffirmed the AM&S and Akzo Nobel line while recognising privilege as a fundamental right of defence under Article 7 of the Charter and Article 8(1) of the European Convention on Human Rights. The Association of Corporate Counsel has applied to intervene in the proceedings to argue for in-house privilege. The rule may yet evolve. It has not evolved today.

One nuance is worth holding onto. While the Commission reads AM&S and Akzo Nobel as confining privilege to EU-qualified lawyers, it generally accepts claims over advice from non-EU external counsel as a matter of international comity. That distinction is not academic when your matter involves US or UK firms.

Scope the people before you scope the documents

Because the privilege line runs through who wrote a document rather than what it says, custodian and author mapping is the first substantive task, not an administrative preliminary.

Before a single document is coded, your team should be able to state, for every name appearing in the seized data, whether that person is an external lawyer, an in-house lawyer, a non-lawyer employee, or something harder to classify. The hard cases are predictable. There is the in-house counsel who moved into a commercial role in 2021 and back again in 2024. There is the seconded associate from an external firm who sat inside the business for eighteen months. There is the European patent attorney whose communications sit under a different rule entirely.

Getting this map wrong contaminates everything downstream. A privilege claim asserted over an in-house lawyer's advice is not merely unsuccessful. It signals to the case team that your log was built on the wrong standard, and it invites scrutiny of the claims that were properly made.

What an EU privilege log has to withstand

A log produced in this setting faces a reviewer looking for exactly one thing: claims that fail the independence test.

Each entry therefore needs to carry more than a conclusion. It needs the identity and status of the author, the identity and status of every recipient, the basis on which independence is satisfied, and enough about the purpose of the communication to show that legal advice was sought or given. Entries that assert privilege over a document because a lawyer appears somewhere in the header will not survive contact.

This is demanding work at speed, and it is where consistency matters more than brilliance. A log where the standard drifts between the first thousand documents and the tenth thousand is a log with a soft centre, and the softness will be found.

Where AI review carries its weight

The reading in a post-raid review is enormous and the judgment is narrow. That ratio is what makes the exercise a good fit for AI-assisted review, provided the division of labour is right.

This is the approach we take with Claira inside Nuix Discover. Claira runs across the full seized population and returns, for each document, a privilege assessment, the parties involved and their roles, a written justification, and excerpts quoted from the document itself. Your lawyers confirm or override every call. The machine carries the reading and the reasoning stays visible, while the decision stays with counsel. We set out that division of labour in more detail in our article on privilege review in the age of generative AI, and the structured output is documented in the privilege review workflow guide.

The EU setting places particular weight on context. Claira's Case Context feature lets you record the matter background, the firms on each side, which lawyers are external and which are in-house, and any role changes with their dates. Claira then applies that map to every document in the population. A model told that a given name is in-house counsel will treat that person's advice correctly on the first document and on the fifteen-thousandth, which is the consistency a contested log requires.

Objective coding earns its place here too. Dates, authors, recipients and document types extracted uniformly across the set give you the spine of both your custodian map and your log, without a reviewer keying fields by hand at two in the morning. And because the inspection was opened on a suspicion of conduct, the same population usually needs screening for cartel indicia on a parallel pass, so your team learns what the Commission is likely to have found at roughly the same time as it learns what it can protect.

One caution on jurisdiction. A privilege prompt written for a domestic standard will apply that standard faithfully, which is exactly the problem when the standard has changed underneath you. Set the criterion to the EU rule explicitly, and record in Case Context which lawyers are EU-qualified and external, so that the analysis separates protected advice from advice that merely looks protected.

Where to start

If your organisation has EU exposure, the useful preparation is not a memo. It is a rehearsal.

Take a closed matter or an internal data set, build the custodian and role map you would need under time pressure, and run a privilege pass over it applying the EU standard rather than your domestic one. Count the documents your usual approach would have logged as privileged that the EU rule would leave exposed. That number is the argument for changing something, and it is far better to learn it now than in the fortnight after an inspection.

If you would like to work through that exercise on your own matter profile, book a working session with us. The rule on in-house privilege is not one you can negotiate with. The review process you bring to it is entirely within your control.