How to organize prior-art references for review for Patent Infringement Matters

Organize candidate prior-art references in a source-linked matrix that separates technical relevance from potential prior-art status. Give each reference a stable identifier, preserve its provenance, distinguish its dates, and map specific passages to asserted claim limitations. Record proposed anticipation positions or obviousness combinations, contrary evidence, and unresolved questions for counsel. The deliverable is a review-ready reference matrix with linked source materials, qualified review decisions, and assigned follow-up—not an unverified publication list or a substitute for invalidity contentions.

When to use this workflow

Use this workflow when litigation counsel, in-house patent teams, technical reviewers, or experts receive search results, inventor-supplied materials, opposing-party productions, or earlier search files. Its immediate purpose is to decide which candidates warrant detailed charting and which date, disclosure, or provenance gaps require investigation. Patent owners can also use it to evaluate references advanced against their claims.

The scope is US federal district-court patent litigation, primarily involving utility-patent claims. Verify governing local rules and case-specific orders before preparing disclosures. Northern District of California Patent Local Rules provide a district-specific example: Rules 3-3 and 3-4 address reference identification, anticipation and obviousness positions, combinations, limitation charts, and supporting production. They do not establish substantive invalidity. See Patent Local Rules 1-2, 1-3, 3-3, and 3-4.

PTAB proceedings, ITC investigations, arbitration, and state proceedings fall outside this guide’s procedural scope. The matrix remains an internal review tool; each forum requires its own procedural analysis.

What you need

Start with the asserted patents, current asserted-claim list, issued claim wording and dependencies, prosecution histories, and relevant claim-construction positions or orders. Identify the versions reviewers must use. A mapping made under an earlier claim set or construction assumption needs an explicit qualification.

Collect complete candidate references where available: patent publications, technical articles, manuals, archived web materials, product records, and sale or use evidence. Include bibliographic records, attachments, translations, repository information, and evidence bearing on availability. A product or alleged activity may require several supporting documents rather than one publication.

Obtain applicable disclosure orders, existing invalidity positions, and a reviewer list covering technical mapping, legal analysis, and source verification. Counsel should identify the applicable statutory regime and claim-specific date questions. AIA and pre-AIA treatment cannot safely be selected from a patent’s issue date alone; the USPTO explains the transition provisions in MPEP § 2159.

Preserve unmodified files separately from OCR, annotations, excerpts, and translations. Keep each derivative linked to its source version.

Use the template

The companion template is Patent Infringement Matters — Prior-art reference matrix. You can copy this table into your working document or spreadsheet. Use one row per reference and proposed theory; repeat the reference ID when different claims, mappings, or combinations require separate decisions.

Source / locator identifies the complete reference and the exact passage: document ID, Bates page, publication page, figure, or native-file location. For an alleged sale or use, link the supporting evidence package and identify the product or event separately.

Dates / evidence distinguishes priority, filing, publication, public-accessibility, sale, and use dates when relevant. Attach support for each date; mark unsupported dates unresolved rather than supplying a sortable approximation.

Disclosure / gap captures direct support, contrary material, and inferential steps. Proposed theory identifies the candidate position without implying approval. Prior-art status / foundation separates statutory treatment from authentication and availability questions. This wording avoids confusing prior-art qualification with patent subject-matter eligibility.

Use Action / owner for a decision, reason, responsible reviewer, and concrete deliverable. Link longer date analyses and charts instead of packing them into unreadable cells.

Step by step

1. Fix the claim set and review questions

Create a controlled claim sheet identifying patent, claim number, dependencies, issued wording, and the source of construction assumptions. Short internal limitation identifiers can aid navigation, but must remain linked to the actual wording.

Ask counsel whether the immediate task is screening search results, evaluating an opponent’s reference, testing an existing position, or selecting candidates for detailed charts. Set an internal review cutoff against the actual case schedule, not another district’s default timetable.

Record in the matrix: claim and limitation, claim-sheet version, review purpose, and any construction question affecting the mapping.

2. Register references without collapsing versions

Assign stable IDs at intake. Capture title, author or issuing entity where available, acquisition source, collection information, and version. Keep patent publication identifiers and family relationships without assuming related publications contain identical disclosures.

Distinguish manual revisions, language editions, attachments, and incomplete copies. Group exact duplicates for review, but preserve each copy’s provenance. For product evidence, distinguish the alleged historical product version from a later manual describing a modified model.

Record in the matrix: selected source copy, precise locator, related-version links, evidence-package ID where applicable, and missing pages or attachments requiring retrieval.

3. Separate date evidence from prior-art analysis

Enter each relevant date with its label and support. Retrieval time, a date printed on a manual, and evidence of public accessibility answer different questions. Do not substitute one for another.

Counsel should assess the applicable statutory treatment, relevant claim dates, and exceptions or factual dependencies requiring investigation. The AIA transition provisions consider application and claim history, including specified continuity relationships; do not reduce that inquiry to a single calendar filter. See MPEP § 2159.

Keep technically promising candidates qualified while analysis remains incomplete. A patent document’s priority claim should trigger examination of the supporting record, not an automatic earlier-date entry for every disclosure.

Record in the matrix: supported and conflicting dates, proposed statutory treatment, unresolved questions, and assigned legal review. Preserve the evidence behind any date correction.

4. Map actual passages to limitations

Read relevant sections in context, including figures, captions, definitions, and qualifications. Identify what the reference expressly describes and what requires technical interpretation. Keep an engineer’s explanation separate from the underlying passage.

For dependent claims, review inherited limitations as well as added language. Mark construction-dependent mappings expressly. If a reviewer proposes an implicit disclosure, require the explanation and supporting evidence rather than accepting a bare conclusion.

Record in the matrix: pinpoint citation, concise disclosure explanation, missing or contrary material, and interpretive assumptions. Link the detailed chart when abbreviated cells cannot show the mapping adequately.

5. Distinguish single-reference positions from combinations

Keep proposed anticipation positions separate from proposed obviousness combinations. For each combination, identify constituent IDs, proposed contributions, and the rationale requiring counsel or expert assessment. Matching keywords is not a reasoned combination analysis.

Check technical compatibility and statements that cut against the proposal. Identify whether the proposed modification changes the operation on which the mapping depends. These are review questions, not conclusions generated by the matrix.

Where Northern District of California Rule 3-3 applies, the disclosure must identify anticipation or obviousness positions, combinations, and reasons for obviousness, with limitation charts. The matrix supplies inputs; it does not replace those requirements. See Patent Local Rule 3-3.

Record in the matrix: theory, linked combination entries, contrary disclosures, compatibility concerns, and unresolved reasoning assigned for substantive review.

6. Identify foundation and language gaps

Assess whether the evidence package supports what the team claims the item is. Federal Evidence Rule 901 requires sufficient support for a finding that an item is what its proponent claims; testimony from a knowledgeable witness is one listed method. Authentication alone does not establish public accessibility or overall admissibility. See Federal Rule of Evidence 901.

Identify potential custodians or witnesses without implying their testimony exists. Preserve foreign-language originals alongside translations and specify untranslated relied-upon portions. Northern District of California Rule 3-4(b) requires English translations of relied-upon portions of covered non-English prior-art items. See Patent Local Rule 3-4.

Record in the matrix: provenance gaps, possible foundation evidence, translation scope, verification owner, and required deliverable.

7. Prioritize and issue the review package

Prioritize by potential contribution and the consequence of unresolved questions. A relevant manual with uncertain availability may justify targeted investigation; a documented article missing the decisive limitation may not justify immediate charting.

Issue the matrix with source files, linked charts, date evidence, and a short unresolved-issues list. Distinguish counsel’s strategy annotations from factual source descriptions and determine appropriate circulation. Preserve rejected theories and reasons so later reviewers do not repeat unsuccessful work.

Record in the matrix: retain, investigate, chart, or deprioritize; rationale; reviewer; and next deliverable. When inputs change, identify affected rows for renewed review.

Worked example

The parties, documents, dates, and claim descriptions below are entirely fictional.

Harbor Circuit LLC asserts a patent against Juniper Controls Inc. Claim 1 concerns a sensor controller with adaptive sampling and a defined calibration sequence. Claim 4 depends on claim 1 and adds a recovery-state operation. The controlled claim sheet records a claimed August 2014 effective filing date, but counsel has not verified entitlement to that date or completed statutory-regime analysis.

Counsel receives three candidates. An article addresses adaptive sampling but not the identified calibration sequence. A manual describes calibration, but its revision date lacks distribution support. A non-English proceedings paper contains a potentially relevant recovery diagram with an untranslated caption.

These dates precede the claimed filing date, but that comparison does not resolve statutory treatment or availability. PA-001 remains technically useful rather than a completed single-reference position. PA-002 warrants focused date investigation and combination analysis. PA-003 does not advance to a recovery-state mapping until the relied-upon language is understood; even then, claim 4’s inherited limitations remain part of the review.

The matrix identifies missing evidence without inventing distribution records, witness knowledge, or translated wording. Follow-up is directed at decisions that could change reference selection.

Common mistakes

• Treating a printed date as established availability. Separate displayed dates from accessibility, sale, or use evidence; assign the missing proof.
• Merging a patent family or manual revisions. Preserve distinct identifiers and verify disclosure in the actual relied-upon version.
• Charting search snippets. Retrieve the reference and examine surrounding text, figures, and qualifications before recording support.
• Using a combination to conceal gaps. Identify each reference’s contribution and separately assess rationale, compatibility, and contrary disclosures.
• Ignoring dependent-claim inheritance. Link the added limitation to the complete inherited claim mapping.
• Equating collection with legal qualification. Keep technical relevance, statutory status, authentication, and accessibility separate.

Final quality check

Before issuing the review package, confirm:

• Retained rows identify source versions and exact passages, or expressly identify missing evidence.
• Claim wording, dependencies, and construction assumptions match the controlled claim sheet.
• Date types remain distinct, supported or expressly unresolved.
• Proposed theories disclose gaps, combination reasoning, and contrary evidence.
• Relied-upon OCR and translations have been checked against originals.
• Foundation assignments identify evidence to obtain rather than assumed witness answers.
• Open issues are resolved or assigned to a responsible reviewer with a concrete deliverable.
• Planned disclosures have been checked against governing rules and case-specific orders.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its litigation document-review and evidence-analysis capabilities can support reviewing candidate references and related evidence. Keep the matrix as your team’s work product and retain legal and technical judgment over dates, prior-art status, mappings, and combinations. To discuss this evidence-review workflow, book a demo.

Frequently asked questions

Should one row cover an entire patent family?

Usually not. Identify each relied-upon publication separately and link family relationships. Verify dates and disclosures in the specific version; family grouping is a navigation aid, not a substitute for reference-level analysis.

Can we retain a reference with uncertain availability?

Yes, as a qualified candidate. State the existing evidence, missing support, and investigation owner. Inclusion does not mean counsel has determined that the reference qualifies as prior art.

Is this matrix an invalidity contention chart?

No. It organizes internal review and supplies source-verified inputs. Governing rules and orders control required disclosures; abbreviated rows do not replace full limitation charts or reasoned positions.

How should technical reviewers and counsel divide the work?

Technical reviewers identify disclosures, omissions, compatibility concerns, and assumptions. Counsel directs statutory and procedural analysis. Both should revisit theory-changing uncertainties rather than converting tentative observations into established conclusions.

Sources

• Northern District of California Patent Local Rules: district-specific scope, invalidity contentions, and supporting production.
• Federal Rules of Evidence, Rule 901: authentication requirements and examples.
• USPTO MPEP § 2159: AIA applicability and transition provisions; examination guidance, not a litigation ruling.

Scope: General professional workflow guidance, not advice for a particular matter. Substantive prior-art status and invalidity require matter-specific analysis.

This guide is general information about legal workflows, not legal advice for any matter. It was drafted and reviewed with AI assistance. The worked example is fictional. Contract rights and procedure depend on the governing law, the actual wording, and the facts, so check the cited sources and the rules that apply in your jurisdiction before relying on it.