Portfolio-to-product alignment

Patent-to-product mapping

Build, review or update the connections between your patent portfolio and products, with supporting sources and unresolved questions organized for your team’s review.

For IP managers and counsel coordinating patent and product information.

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

The decision behind the research

Which products or features should be associated with which patents, and what evidence supports each association?

Need to prioritize families before mapping? Explore portfolio analysis.

Common reasons to commission this work

  • Portfolio-to-product alignment
  • Patent-marking program support
  • Licensing preparation
  • M&A and internal diligence
  • Ongoing portfolio maintenance

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.

An editable mapping workbook with stable patent and product identifiers, source references, assessment labels and an unresolved-question list.

  • Patent-family and product inventory
  • Claim-to-feature mapping matrix
  • Dated evidence citations
  • Confidence and gap notes
  • Priority review list
  • Update-ready source workbook

What the evidence is based on

Selected claims, product specifications, manuals, model lists and client-authorized technical materials. We distinguish a preliminary family-to-product screen from a limitation-level record.

How your team reviews the result

Agree the mapping unit and fields on a representative subset before expanding. Discuss product changes and who will approve proposed associations.

How sources and uncertainty are recorded

See the work

Which current products have evidence relevant to the selected patent families, and what requires review?

Patent-product mapping and claim mapping can range from a family-to-product screen to a detailed comparison of selected claim limitations with product features.

A feature match is not a conclusion that an entire claim covers a product. The full selected claim must be reviewed.

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.

Patent-to-product mapping demonstration
Family / selected limitationProduct / featureEvidence and dateStatus / next review
DEMO-01, claim 1: controller receives a temperature measurementModel A v2.1 / temperature inputFictional manual A-01 §4.2, dated 2026-09-01; reviewed 2026-10-26Direct evidence for this limitation; association still requires full selected-claim review.
DEMO-02, claim 1: threshold varies with operating modeModel B v1.4 / adaptive controlFictional release note B-02 §2 describes adaptive operation but not threshold logicInference only; seek engineering confirmation before approving the association.
DEMO-03, claim 1: remote sensor calibrationNo matching feature locatedNo supporting source in the defined materialsUnresolved; revisit after next product release or further documentation.

A product-family alignment exercise and a full limitation-level chart answer different questions. We agree the unit of mapping, selected claims and review depth around your purpose.

What you can hand over first

Start with the assignment your team needs help with.

Choose a selected product line, patent family or portion of an existing map. Agree the mapping depth and fields on a representative subset before expanding.

Build a map for a product line

Connect selected patents with the products and features your team needs to review.

Typical output within the agreed scope: A proposed association matrix, supporting sources and an unresolved-question list.

Discuss this scope

Review existing associations

Investigate the evidence behind existing links and identify gaps, inconsistent identifiers or associations needing closer review.

Typical output within the agreed scope: An annotated workbook with evidence status, review priorities and questions for the approving team.

Discuss this scope

Update changed products or records

Focus on a defined set of product releases, changed models or patent records rather than rebuilding the whole map.

Typical output within the agreed scope: Proposed changes, source references and update triggers for your existing process.

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 mapping depth before expanding the work.

01

Normalize

We organize patent families, claim status, product names and versions before mapping begins.

02

Decompose

For agreed claim-level work, selected claims are broken into discrete limitations. A preliminary family-to-product screen uses a separately agreed depth.

03

Map

Each limitation is connected to dated product evidence, with source links and confidence notes.

04

Maintain

The matrix is versioned so new products, releases and patent events can be incorporated.

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.

  • Patent or application list
  • Product catalogue, model list or feature inventory
  • Available manuals, release notes and technical materials
  • Target date range and business purpose
Agree handling arrangements before sharing confidential information

Scope boundaries

  • Legal opinions on infringement or validity
  • Patent drafting, filing or prosecution
  • A conclusion that a mapping satisfies any marking statute
  • Unverified statements presented as facts

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

Patent-to-product mapping questions

What is patent-to-product mapping?

It is the structured process of comparing patent claim limitations with product features and documenting the supporting technical evidence. The result is a reviewable matrix, not a legal opinion.

Can the mapping support virtual patent marking?

It can organize the product-patent associations and evidence used by a marking program. Counsel should determine legal sufficiency and jurisdiction-specific requirements.

How is the map kept current?

We use stable identifiers, dated evidence and version control so product releases, discontinued models and patent-status changes can be reviewed systematically.

Can you review associations we already have?

Yes. The scope can focus on existing links, a selected product line or changed models. We agree whether the task is evidence collection, consistency review or new mapping.

Will the result fit our current workbook or system?

Discuss required identifiers, fields and file formats during scoping. The handoff can be organized around your review process; any system integration is separately agreed.

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