Claim-level product evidence

Evidence-of-use search

Investigate the evidence for a known product against selected patent claims, whether you need a new chart, a review of an existing chart or help with specific missing limitations.

For patent counsel and licensing teams with a selected patent and known product.

A focused assignment first. Deliverables, responsibilities, timing and fee agreed before research begins.

The decision behind the research

What public evidence supports, weakens or leaves unresolved a proposed claim-to-product mapping?

Need to identify candidate products first? Explore infringement search.

Common reasons to commission this work

  • Licensing and enforcement preparation
  • Technical diligence
  • Counsel work-product support
  • Competitive product analysis
  • Portfolio prioritization

Choose the research around the decision and what you already know. A full programme is not required to begin a conversation.

What you receive

A defined work product for your team’s next review.

A limitation-level chart, source register and gap memorandum in agreed editable and presentation formats. Source copies are included only where permitted.

  • Limitation-level evidence chart
  • Dated source library
  • Evidence-strength grading
  • Gap and contrary-evidence notes
  • Product-version record
  • Questions for technical or legal review

What the evidence is based on

Dated technical manuals, product documentation, developer materials, standards and other relevant sources. We record model applicability and distinguish observed statements from technical inference.

How your team reviews the result

Agree priority claims and product versions, examine difficult limitations and discuss unresolved evidence at handoff. Testing, teardown and source-code work are separately scoped.

How sources and uncertainty are recorded

See the work

What evidence supports each selected limitation for a known product?

Evidence-of-use analysis and claim-chart services document the technical source record for selected claims and a known product.

The assessment labels apply to individual limitations, not to an overall infringement conclusion.

Review the fictional demonstration to see the fields, reasoning and limitations. The output for your project is agreed during scoping.

Fictional demonstration. All source excerpts, products, patents and dataset values are illustrative, not client work.

Annotated evidence-of-use demonstration
Selected limitationEvidence / sourceAssessmentGap / next action
A controller receives a measured temperature from a sensor“The controller accepts the sensor temperature signal.” Fictional manual A-01 §4.2, dated 2026-09-01; reviewed 2026-10-26SUPPORTED: explicit description of the selected feature for the identified modelVerify the source applies to the product version under review.
The controller compares the measured temperature with a threshold“Maintains the selected temperature automatically.” Fictional guide A-02 p.18, dated 2026-09-05INFERENCE: regulation is described, but the comparison mechanism is not statedInvestigate technical documentation or agreed testing. Do not present the mechanism as observed.
The threshold is adjusted in response to a remote commandNo source in the defined research setUNRESOLVED: no supporting evidence locatedRequest further instructions. Absence of public evidence does not prove absence of the feature.

Need to find candidate products first? Explore candidate-product discovery.

What you can hand over first

Start with the assignment your team needs help with.

Start with a selected claim and product version, an existing partial chart or specified missing limitations. Agree acceptable sources, dates and the required depth before research begins.

Develop a new evidence chart

Investigate a known product against selected claims using attributable technical sources.

Typical output within the agreed scope: A limitation-level chart with dated citations, reasoning and unresolved gaps.

Discuss this scope

Review an existing chart

Check the strength, applicability and completeness of the sources already assembled.

Typical output within the agreed scope: An annotated review distinguishing documented features, inference, version issues and missing support.

Discuss this scope

Investigate missing limitations

Focus research on the particular implementation details holding up your team’s review.

Typical output within the agreed scope: A focused evidence memorandum with located sources, remaining gaps and sensible next investigations.

Discuss this scope

We confirm feasibility, milestones and a delivery schedule after reviewing the scope and available inputs. Your proposal identifies the project contact, research responsibilities and review steps.

Discuss your project

How the work is performed

Agree the evidence standard, investigate and review.

01

Set the standard

We agree the claim granularity, acceptable sources, date rules and confidence scale.

02

Research

We locate manuals, specifications, archives, regulatory documents and other attributable technical sources.

03

Chart

Evidence is mapped limitation by limitation with quotations, URLs, dates and source type.

04

Grade

Each row distinguishes direct evidence, reasoned inference, missing evidence and contrary indications.

For the first discussion

You do not need a finished research brief.

A non-confidential description of the question, what you know and any deadline is enough to start. The following inputs help establish scope; do not upload sensitive materials with your initial inquiry.

  • Known target product and version
  • Selected patent claims
  • Critical dates
  • Existing evidence or technical hypotheses
Agree handling arrangements before sharing confidential information

Scope boundaries

  • An infringement, validity or freedom-to-operate opinion
  • A substitute for testing, reverse engineering or discovery
  • Legal claim construction
  • Patent prosecution services

Technical findings are structured for review. Legal conclusions and final business decisions remain with the appropriate decision-makers.

Discuss delivery and review responsibilities

Before you reach out

Evidence-of-use search questions

What counts as evidence of use?

Depending on the scope, sources can include product manuals, data sheets, standards materials, regulatory filings, archived webpages, demonstrations and technical publications. Every source is identified and dated where possible.

Do you test products?

The standard service focuses on documentary public evidence. Physical testing or reverse engineering would require a separately defined workflow and suitable specialists.

How do you show uncertainty?

Each limitation receives an evidence status and an explanation. Inferences, missing documentation and version ambiguity are made visible in the chart.

Can you work from a partial chart or a specific evidence gap?

Yes. A focused engagement can investigate selected limitations or assess the sources already assembled. Share a non-confidential description first; detailed transfer arrangements can follow.

What if public documents do not reveal the implementation?

We identify the unresolved limitation and explain what additional evidence or investigation could address it. We do not turn a missing source into a positive finding or a legal conclusion.

How do we get a quote?

Describe the question and what you already know. We discuss fit and a practical scope, then agree deliverables, responsibilities, timing and a fixed fee before work begins.

Useful research guidance

Start with a conversation

Tell us what you’re trying to understand.

We’ll discuss whether we can help, what information is available and how the work could be scoped.

Discuss your project