Claim scope and accused product features
Create a claim-feature table, identify product functions and collect supporting technical documents without assuming that marketing materials reveal internal implementation.
Infringement assessment requires more than placing a product photograph beside a patent abstract. The comparison must address the actual claim language, available technical evidence and competing explanations for how the product operates.

A patent owner assessing enforcement or a product team responding to an allegation needs a clean documentary record. Claim mapping, evidence provenance and expert collaboration help counsel focus on factual uncertainties before formal positions are taken.
Create a claim-feature table, identify product functions and collect supporting technical documents without assuming that marketing materials reveal internal implementation.
Track evidence origin, versions, access permissions and missing information; coordinate specialist technical review where software, chemistry or hardware behavior requires testing.
Separate factual comparisons from infringement opinions, defenses, remedies and settlement options. Technical research can inform decisions but does not replace legal claim construction or advice.
These examples illustrate how a limited consulting assignment could support internal decisions. The exact deliverables, professional roles and project feasibility are confirmed before engagement.
The scope states the inputs, owner and quality threshold, so the resulting document can be checked by decision-makers rather than treated as an unsupported conclusion.
The deliverable identifies source records, assumptions, gaps and the follow-up review needed before a commercial commitment or formal professional action.
Recommendations are framed as options, dependencies and next steps. They do not imply a guaranteed investment, litigation, certification, clinical or regulatory result.
These topics are research coverage, not a claim that every activity is directly delivered. Any regulated opinion, professional certification or formal procedure is assessed separately.

Identify the business decision for patent owners; product companies; disputes experts; litigation support teams, the relevant assets, the stakeholders and any time-sensitive restrictions.
Collect permissioned documents relevant to claim scope and accused product features, distinguishing public records from information supplied by the client.
Compare evidence provenance and expert coordination with settlement economics and dispute readiness, recording material uncertainty and alternative explanations.
Prepare the agreed claim chart research pack, a review-ready issues register and a prioritized list of next decisions and specialist referrals.
A starting pack may include relevant claims, patent family data, product specifications, feature comparison tables, evidence citations and a list of assumptions or unanswered questions.
When legal claim construction, jurisdictional infringement standards, protected technical evidence or contentious procedural decisions arise, counsel review is necessary.
Describe your technology, buyers, countries, immediate business decision and the supporting records you can share. The first step is a defined consulting scope with clear assumptions and specialist handoffs where required.
rd (at) patentbusinesslawyer (dot) comProfessional-scope boundary: Patent infringement opinions, litigation conduct and damages quantification need appropriately qualified professionals; evidence alone does not establish infringement. This page outlines a potential global consulting and research assignment, not a jurisdiction-specific legal opinion, medical advice, regulated investment recommendation or certification. Requirements and availability are checked for each project.