Before filing, how do you compare confidential invention material your team is authorized to use with public evidence? Proposed claims may depend on technical details scattered across inventor notes, drawings, and a working specification. Public references may use different terminology, while product documentation may leave implementation details unanswered. A structured review gives your patent team a traceable basis for identifying gaps and revising the draft.

The workflow concerns your own authorized pre-filing material under U.S. practice; attorneys retain review and decision authority.

What can you search before publication?

Separate 2 questions in an unpublished patent search: finding publicly accessible records and analyzing your own invention material. Public patent search covers published records. Reviewing your own unpublished material depends on documents your team is authorized to supply.

The U.S. Patent and Trademark Office (USPTO) provides public patent search over U.S. patents and published applications. Applications that have not been published are generally preserved in confidence, subject to specific public-access exceptions. Public search therefore cannot retrieve another applicant’s still-confidential filing simply because its subject matter matches your invention.

Use precise labels for the material under review:

• Pre-filing draft: invention material or a working application that has not yet been filed.
• Filed, unpublished application: an application submitted to a patent office whose contents have not yet been published.
• Published application: an application available to the public, with claims that may change during examination.
• Issued patent: a granted patent whose issued claims require their own analysis.

For U.S. applications subject to publication, publication generally occurs after 18 months from the earliest filing date for which benefit is sought. Earlier publication and exceptions are addressed in the USPTO’s application-publication rules.

Keep invention material and public evidence separate

Before confidential material enters an analysis workflow, record what may be shared, with whom, and through which approved channel under the client’s instructions and applicable obligations.

Maintain 2 clearly labeled source groups throughout the review:

Authorized invention material includes the selected draft claims, specification, drawings, and technical explanations supplied for the matter. Record the version and provenance of each item. Distinguish an inventor’s demonstrated implementation from a proposed alternative or an unanswered technical question.

Public evidence includes retrieved patent publications, technical papers, standards, manuals, and public product documentation. Record the publication identifier or URL, relevant dates, and exact passage used in a comparison. A source that describes a similar objective may use a different mechanism, so preserve the technical details behind each apparent match.

Practitioners maintain the review record through the team’s approved recordkeeping process. Every comparison should identify which proposition comes from the invention material, which comes from an external source, and which is an analytical inference.

Define the question before comparing claims

A pre-filing review can address several questions, each requiring a different comparison.

Prior-art and patentability questions

Compare proposed claims with potentially relevant earlier disclosures. In U.S. practice, novelty and obviousness are addressed under §102 prior-art rules and §103 obviousness guidance. Assess the claimed invention and the legal relevance of the references, including dates and applicable exceptions.

Call this patentability review of proposed claims. Reserve invalidity analysis for evaluating the validity of claims in an existing patent.

Disclosure and claim-language questions

Compare the proposed scope with the draft’s technical teaching. Under U.S. §112(a), written description, enablement, and best mode are separate requirements. Section 112(b) addresses claim definiteness. The USPTO explains these specification requirements and claim-definiteness standards separately.

Identify where a limitation appears in the text or drawings, flag unexplained alternatives, and send technical questions to the inventors. Evaluate whether the disclosure supports the proposed scope and whether the claim language needs revision.

Proposed claim scope against product evidence

A hypothetical comparison can ask whether available product documentation describes the features recited in a draft claim. Preserve the distinction between an explicit disclosure, an inference, and a feature for which evidence is missing.

Infringement analysis concerns patent rights and the relevant claims, product, jurisdiction, and conduct.

Freedom to operate (FTO) requires a separate review workflow for third-party patent rights affecting the intended product, activity, and markets, because a patent grants a right to exclude and the ability to practice depends on others’ rights and applicable laws.

Build a pre-filing review record

1. Fix the draft and review objective

Select the claim set and supporting documents for one review pass. Identify the technical distinction you want to investigate, such as a control sequence, material property, or relationship between components.

Record the draft version, intended filing jurisdiction, relevant date assumptions, and matter owner. Give the search a defined purpose. “Find references describing optical-emission control of an etch sequence” produces a more focused assignment than “assess the invention.”

2. Search public sources for the technical mechanism

Build search concepts around the problem, mechanism, components, and alternatives. Add terminology used in relevant patent publications and technical literature. Use patent classifications and citation trails to expand beyond the inventors’ vocabulary.

Include non-patent literature (NPL) where it can explain the same mechanism or its technical context.

Keep a search record with the source coverage, search date, concepts, and references selected for closer analysis. Use the authorized search inputs defined for the matter.

3. Compare limitations with exact passages

Break the proposed claim into its individual limitations, meaning the requirements expressed by its language. For each issue, preserve:

• The exact proposed limitation and its draft version.
• The passage or figure in the invention material that relates to it.
• The external reference and exact passage used for comparison.
• The difference, missing evidence, or inference requiring review.
• The technical question and the recorded disposition.

Keep novelty and obviousness reasoning separate. A limitation-by-limitation record helps locate evidence, while an obviousness analysis considers the claimed invention as a whole and the rationale for any proposed combination of references.

Check cited passages in context, confirm relevant dates, and record how the evidence supports the comparison.

4. Resolve technical gaps and revise the draft

Send technical gaps to the people who can answer them. Ask the inventors to explain implementation details, alternatives, and the basis for any asserted distinction. Keep their responses tied to the relevant limitation and draft passage.

Record which claims or specification passages will change and why. When wording changes, revisit the affected comparisons and record which evidence and questions remain relevant. Preserve the earlier review record so the rationale for the revision remains visible.

5. Prepare the filing decision

Prepare a compact decision record: the selected draft, key references, unresolved technical questions, proposed revisions, and the reasoning accepted or rejected during review.

Include the public-search visibility gap. Under the America Invents Act (AIA), certain later-published U.S. patent documents can qualify as prior art from an earlier effective filing date, subject to statutory conditions and exceptions. The USPTO’s earlier-filed document guidance explains that treatment. Record the search date and assign any follow-up search to a named reviewer.

A fictional example: one limitation, three evidence questions

Suppose a team preparing a 2026 filing is drafting a claim for a semiconductor wafer-etching process. The process switches from a main etch to a lower-power finishing step when an optical-emission intensity ratio crosses a threshold.

An inventor note describes the ratio-triggered switch. The working specification describes a timed switch but leaves the wavelength selection and threshold logic unexplained. A retrieved patent publication describes an emission-ratio endpoint sequence. A public equipment manual says that an etch chamber supports “adaptive endpoint control” without explaining what triggers a step change.

Each source creates a different review task:

• Disclosure question: record the inventor’s explanation of the wavelength selection and threshold logic and the resulting draft revisions.
• Prior-art question: assess the publication’s relevant dates, technical disclosure, and relationship to the proposed claim.
• Product-evidence question: the reviewer records the trigger mechanism as unresolved. “Adaptive endpoint control” supplies too little detail to equate the documented product behavior with the proposed limitation.

The useful output is a set of source-specific questions and decisions. Broadening the claim to “adaptive endpoint control” would change both the prior-art comparison and the disclosure review. Record the rationale for that revision.

Make the handoff useful to your patent team

For an in-house team, connect each unresolved issue to the filing schedule and the relevant research and development (R&D) decision. Separate the implementation intended for the current product from alternatives on the roadmap. Assign a technical owner and a decision owner for each open item.

The deliverable is a reviewable decision record that outside counsel and the internal team can use in the same filing discussion.

Where Patlytics fits

Patlytics supports the disclosure preparation, evidence comparisons, and application drafting behind your pre-filing decision.

• Invention Disclosures (IDF) turns inventor materials, slides, and spoken input into a reviewable invention disclosure form.
• Patent Drafting prepares application drafts from technical source material.
• §112 Check analyzes written description and enablement under §112(a) and definiteness under §112(b), returning flagged phrases and ratings.
• Patent & NPL Search retrieves patent and non-patent references, including literature from PubMed.
• Claim Charting produces citation-backed, limitation-level comparisons.

For chemical or biological drafts, inputs and drafting support include ChemDraw input, a structure editor, image-to-SMILES (simplified molecular-input line-entry system), Markush/R-group generation, and sequence uploads with complementarity-determining-region (CDR) detection.

Attorneys approve the inputs, review generated work product, and retain decision authority over its use.

Build an evidence-backed pre-filing record that guides claim and specification revisions. Book a demo of Patlytics for disclosure review and patent drafting.