One computer, one fixed fee: £800 + VATCivil, employment, family, business and private matters · 5–10 working days to the signed reportTalk it through first:0800 6890668
DFEDigital Forensic Expert 0800 6890668 Instruct
BUNDLE PAGE B/08DFE / The dispute / Intellectual property and source code

Source code · CAD drawings · design files · repositories cloned · archives made · uploaded or carried out · similarity is for an expert · £800 + VAT

Intellectual property and source code. Whether two programs are too alike is a question for an expert. Whether your code left the building on a Thursday night is a question for the laptop.

Intellectual property disputes with a computer at their centre have two halves. One is comparison: is the rival's product derived from yours? That is opinion evidence from a specialist in the technology, and no part of this service. The other is movement: did the material leave, when, and by what route? That is a factual question, and the departing developer's or designer's work computer is where the answer usually sits. Large collections of files leave distinctive traces when they are gathered up, compressed and sent somewhere. A factual report sets those traces out, and tells the solicitor whether the first half is worth pursuing.

The drive is imaged firstEvery finding names its recordAn account, not a person£800 + VAT, paid before the work

This page quotes rules, guidance and decided cases and gives the source for each. It is not legal advice; for your own position, ask a solicitor.

Tell us the dispute and whose computer it is; you hear whether a factual report fits before any fee is taken
0800 6890668

What a factual report can give.

A factual report givesHow and when a body of work was gathered and moved off the computer
FromThe forensic image of the work machine
It does not giveWhether another product copies it, or whether the work is protected

What is alleged, and what the computer may record.

What is allegedWhat the computer may recordWhat it cannot showWorth knowing
Whole repository cloned shortly before leavingLocal repository folders, dates, tool historyServer-side access by other meansAsk for the hosting service's audit log
Project zipped and uploadedArchive creation, compression tools run, browser uploadsThe archive's contents once deleted and overwrittenFile names and sizes often survive
Drawings copied to an external driveDevice records, folders openedThe drive's present contentsAs for any departing employee
Code emailed to a personal accountSent mail, webmail sessionsWeb-based message bodiesMail server logs help
Work for a rival done on our timeNew projects, searches, documentsAuthorship of ideasDates against employment
Rival product resembles oursNot examinedSimilarityAn expert in the field compares the works

What to do first, in order.

  1. Preserve the work computerUnused, powered off, not reissued.
  2. Preserve the logs you controlVersion-control hosting, cloud storage, VPN and mail server logs often expire in weeks.
  3. Identify the crown jewelsWhich repositories, drawings or datasets matter. The examination can then look for those names.
  4. Take advice on the claimConfidence, copyright, database right and contract give different remedies. That is your solicitor's field.
  5. Instruct the examinationWith the list of what matters and the dates.

Do not

  • Do not reissue a developer's laptop on their last day.
  • Do not let retention periods on hosted logs run out.
  • Do not download a rival's product on to the same computer to compare.
  • Do not expect a forensic report to say the rival copied you.
  • Do not access the former employee's personal repositories.

In more detail.

Traces of bulk movement

Taking one document leaves little. Taking a codebase or a drawing office's output means handling thousands of files, and people do that with tools: a version-control client to clone a repository, an archive program to compress a folder, a sync client or a browser to upload the result. Each tool leaves evidence that it ran and when, and the operating system records large files appearing and disappearing. A report will typically show, for example, that a compression tool was first run on a given date, that an archive bearing the project's name was created minutes later, and that a file-sharing site was visited next.

Logs that are not on the laptop

Much of the best evidence in these cases is held by services, not computers. Hosted version-control platforms and cloud storage providers keep audit logs of clones, downloads and sharing, for limited periods that depend on the plan. Corporate VPNs and mail gateways keep their own. This service examines the computer; it does not obtain or analyse provider logs as part of the fixed fee, though analysis of exports you supply can be quoted. The first action in any suspected theft of code should be to ask whoever administers those services to export and keep the logs.

The comparison is someone else's job

If the factual picture supports it, the claim will turn on whether the defendant's work reproduces or derives from the claimant's. Courts decide that with the help of experts in the relevant technology, who compare the works and explain similarities and differences, subject to the usual rules on permission and duties to the court. That is a different skill from forensic examination of a computer and is not provided here. What the factual report contributes is the history: who had the material, and how it moved.

Sources
  1. Elcomsoft, USB device history on Windows (registry timestamps 0064-0067, Event 1006, limits) — blog.elcomsoft.com/?p=12849
  2. ForensicsWiki, Google Chrome (profile files and timestamps) — forensics.wiki/google_chrome/
  3. Bates Wells, search and imaging orders: the new model form (23 February 2026) — bateswells.co.uk/updates/search-and-imaging-orders-the-new-model-form-and-what-applicants-need-to-consider/
  4. Practice Direction 31B (disclosure of electronic documents) — www.justice.gov.uk/courts/procedure-rules/civil/rules/part31/pd_part31b
  5. Civil Procedure Rules Part 35 (experts and assessors) — www.justice.gov.uk/courts/procedure-rules/civil/rules/part35

Each quotation was checked against the source named, on 11 November 2026; where a case was read in a summary or case note, the page says so. Rules are amended from time to time, so use the links for the text in force. This is not legal advice, and none of the bodies named has any connection with this site.

Asked in disputes like this.

Can you tell if our source code was copied?

The report can show whether and how it was gathered and moved off the work computer. Whether another product copies it is for an expert in the technology.

Can you get the logs from our code-hosting provider?

You or your administrator request those. Analysis of exports you supply is extra and quoted first.

What does it cost?

£800 + VAT for one computer with one drive, paid before the examination starts.

Switched off. Locked away. Then tell us the dispute.

Say what the dispute is about, whose computer it is and whether anything has been started in a court or tribunal. Within a working day you hear whether a factual report is the right tool and whether we can take it on, free of charge. If you go ahead, the fee of £800 + VAT per device is paid on a pro forma invoice before imaging. In the meantime the computer stays off, out of reach and unused.