Damages quantification: costs drivers
Damages quantification is the stage where a patent dispute turns from a legal question into a numbers exercise. It rarely runs on a fixed budget: cost depends on how many product lines are affected, how far back the infringement goes, and how much of the financial data sits with the other side. A short case with clean records is inexpensive to price. A cross-border case spanning several product cycles is not.
What actually drives the cost
Four factors decide most of the final invoice. Each one multiplies effort rather than adding to it, so a case with two or three of them together costs considerably more than the sum of its parts.
| Driver | Effect on cost |
|---|---|
| Number of product lines involved | Each line needs its own sales and margin analysis |
| Length of the infringement period | Longer periods mean more accounting years to reconstruct |
| Access to the infringer's financial data | Refusal to disclose forces reliance on market estimates, which takes longer to build and defend |
| Whether a counterclaim is filed | A counterclaim adds a parallel valuation track and doubles the review load |
Access to data is usually the deciding factor. When the other side discloses sales figures voluntarily, the exercise is closer to an accounting review. When it does not, the file has to rely on market comparators, expert estimates, and secondary sources, all of which need to be defended separately.
What to do
The sequence below is the order we follow once a client asks for a quantification file, not a list of options to pick from.
- The client gathers internal sales and cost records for the affected products.
- The team maps the infringement period against those records and flags the gaps.
- A request for disclosure goes to the other side, with a set deadline.
- If disclosure is refused or incomplete, an expert builds a market-based estimate instead.
- The file is assembled into a single valuation report with supporting schedules.
- The report is reviewed internally before it is filed or used in negotiation.
Each step has an owner. The client supplies internal figures. The team drives disclosure and deadlines. An external expert, engaged only where needed, builds the estimate when direct data is unavailable.
Who decides and how long it takes
There is no single decision-maker for the quantification itself. The valuation is a working file, not a ruling. It becomes binding only once a court or arbitral tribunal accepts it as evidence, or once both sides agree on it during settlement talks. Timing depends almost entirely on disclosure: a cooperative counterparty can bring a file together within a few weeks, while a refusal to disclose can stretch the process past three months.
The forum matters less than the underlying data. A dispute heard through a specialised patent forum still needs the same records; the venue changes the procedure around the file, not the file itself.
Common forks
If your dispute involves a departing employee who took know-how into a competing product, the valuation questions overlap with staff-related IP claims rather than pure infringement. When a former employee launches a similar product explained sets out how that overlap changes the cost picture.
If the infringing product line has since been discontinued or merged into a different offering, tracing the affected revenue takes longer. A comparable tracing problem appears in token-based assets after a technical split; the underlying logic of following value through a change in the asset is similar. Fork and migration handling step by step in detail walks through that logic in a different context.
If the other side ignores the disclosure request entirely, the file moves to the market-estimate track described above. This adds time but does not stop the process.
How the file is organised
A quantification file is built by the same team that handles the underlying dispute, supported by an external financial expert where the numbers require it. We do not outsource the whole file to a third party; the legal team stays responsible for how each figure is used. The people behind the reports in detail describes how that division of work is set up across the firm.
Sources and limit of this page
This page describes the internal procedure for building a damages file. It does not set the applicable measure of damages, does not fix a currency figure, and does not predict what a court or tribunal will accept. Those questions depend on the specific dispute and the jurisdiction where it is heard, and they are answered case by case, not on a general page.
Where the dispute involves a counterparty outside the client's home jurisdiction, the quantification file is only as strong as what can be verified about that counterparty in the first place. Counterparty in Norway in detail sets out what a standard verification report can establish before the valuation work starts.
Reviewed for procedural accuracy on the date this page was published. No article numbers or statutory citations are given here by design; this is a description of process, not a legal opinion.
Related reading
A protective letter is sometimes filed before quantification starts, to pre-empt an interim injunction. Protective letter step by step covers the costs of that earlier stage.
Next step
If the dispute in front of you involves a former employee rather than an external competitor, the first moves differ from a standard infringement file. When a former employee launches a similar product step sets out what to check before any valuation work begins. Write to us with the product line and the disputed period, and we will confirm within a working day what the quantification file for your case would involve.
FAQ
How long does damages quantification take in practice?
A cooperative counterparty and clean internal records can produce a working file within a few weeks. A refusal to disclose financial data pushes the process past three months, since the file then relies on market estimates that need separate support.
Which documents are needed to start?
Internal sales and cost records for the affected product lines, a defined infringement period, and, where available, any correspondence already exchanged with the other side about the dispute.
What happens if the other side does not respond?
The file moves to a market-based estimate built by an external expert. This does not stop the process, but it adds time and requires the estimate itself to be defended as part of the file.