How can I show independent development when accused of copying or misuse?

Someone alleges that your software, design or process draws on their work or confidential information. You believe your team developed it independently. The useful question is what your records can show about how you reached the disputed result.

A clear account connects particular features to the people, sources and decisions behind them. This answer focuses on copyright, unregistered designs and trade secrets. The legal significance of independent development, and who must prove which facts, depend on the right and jurisdiction. Your adviser should assess those questions against the actual allegation.

Start with the features you are accused of copying

Identify the code, design elements or information the other party says you took. If the allegation is broad or unclear, ask your adviser to seek enough detail for a meaningful response. See identifying the material at issue in an IP dispute.

Then locate those features in your own records. A project may have begun years before the dispute while the contested feature appeared only recently. An early proposal for the whole product will not necessarily explain the origin of that feature.

For each disputed item, identify its earliest documented appearance, the contributor involved and the records showing its subsequent development. Keep the relevant versions available for comparison.

Explain the path from the initial problem to the result

Use the records made during the work to explain how your team arrived at its solution. Drafts, laboratory notes, prototypes, issue discussions and design reviews can connect a finished feature to the decisions that produced it. Failed experiments and discarded approaches may help explain why the team chose a particular configuration.

WIPO’s trade-secret litigation guide identifies records of research and development progress as useful evidence when independent discovery is asserted. The point is to substantiate the route by which the information was obtained.

For example, imagine your company is accused of using a competitor’s confidential coating process after hiring one of its engineers. Trial records from before the engineer joined might show your team testing and selecting the disputed combination of temperatures and timings. Link those results to the version actually used in production. A general budget approval for coating research would establish much less about the origin of that combination.

Continue the account through later changes. Earlier independent work may explain the initial process without explaining a subsequent improvement. Identify what changed, who proposed it and the evidence of how that person reached the proposal.

Account for the sources your team used

Identify the public papers, standards, supplier specifications, licensed components and earlier internal work that informed the disputed features. Connect each source to the relevant decision or implementation, including when your team obtained or used it.

A source found after the allegation may show that information was publicly available. It does not establish that your team actually relied on that source during development. Distinguish those two propositions in your account.

Similarities may have a common origin. In a hypothetical software dispute, matching code or even a shared error could come from a library both teams used. Dependency records, licence files and earlier versions may help test that explanation. Identify the matching material precisely; the presence of one shared library does not explain every similarity in a program.

The US Ninth Circuit’s copyright instructions discuss independent creation and a prior common source as alternatives to copying. This is a US copyright example. A technical comparison should explain significant similarities and differences and their possible origins, while the legal assessment addresses which material is protected.

If your team studied or tested another product, describe that activity accurately. Keep acquisition records, test notes and resulting findings. The EU Trade Secrets Directive, Article 3, recognises independent creation and certain forms of reverse engineering as lawful acquisition, subject to its conditions, including the absence of a legally valid duty limiting that acquisition. Do not describe all work as independently invented if some of it came from such examination or from licensed material.

Address any access to the other party’s material

Review whether relevant team members encountered the claimant’s work or information through earlier employment, collaboration, demonstrations, shared files or public releases. Identify what they could access and when. Access does not itself establish use, but an explanation that ignores known contact leaves an important question unanswered.

Compare that timeline with the development of each disputed feature. Where decisions preceded the contact, identify the supporting records. Where they followed it, examine the sources and discussions behind them rather than assuming the earlier project start resolves the issue.

If you relied on separate teams or access restrictions, retain evidence of how those arrangements operated: team assignments, permissions, instructions and communications. A policy labelled “independent development” does not itself show that the people doing the work were separated from the information.

Also examine the permissions that applied. You may have been entitled to use material under a licence or collaboration agreement. That is a different explanation from independent development. Under Article 4 of the EU Trade Secrets Directive, lawful receipt does not necessarily permit later use or disclosure in breach of applicable duties.

Corroborate the chronology and make gaps visible

Connect internal records to dated exchanges with suppliers, external test reports, delivered prototypes or other records outside the immediate development team. Explain what each supports: an external test report may establish the performance of a sample without revealing the process used to make it.

Previously timestamped versions can support when particular files existed. They are most useful here when the files contain the disputed features or explain their development. Read more about what a digital timestamp establishes.

If you prepare a chronology now, label it as a later summary and link each statement to its source. Record recollections separately from contemporary documents. Preserve the underlying records, including material that complicates your account; do not rewrite earlier notes to make the history appear more complete.

Give your adviser a feature-by-feature account of the development, the supporting evidence, relevant exposure to the claimant’s material and unresolved gaps. This lets them test your explanation and identify where further investigation is needed.

Independent development is particularly relevant to the rights discussed here, but it is not a universal answer to an IP allegation. The European Commission’s design guidance distinguishes unregistered protection against copying from registered design protection. Do not assume that showing an independent origin resolves a registered-design or patent claim in the same way.