TL;DR

Search by claim element, not by product name. Cover patents (Google Patents, Espacenet, Patentscope) and non-patent literature (papers, manuals, datasheets, archived web pages). Everything must predate the application's earliest effective priority date, and for anything without a printed date you'll need evidence — the Wayback Machine is your friend.

What Counts (and What Doesn't)

For a 3PPS you may submit only patents, published patent applications, and printed publications — documents. A "printed publication" is broad: academic papers, textbooks, product manuals, datasheets, standards documents, conference slides, catalogs, and web pages all qualify if they were publicly accessible before the critical date.

Two hard limits:

  • The date. The reference must qualify as prior art against the application — as a working rule, look for material published before the application's earliest priority date (shown on the front page of the published application as "related/priority data"). Material dated between the priority date and the filing date raises complications a practitioner should assess.
  • Documents only. A product that was on sale is not itself submittable — but its manual, datasheet, or archived product page is. Physical devices, videos, testimony, and declarations cannot go into a 3PPS.

Proving the Date

A reference is only useful if the USPTO can see it was publicly available before the critical date. Patents and published applications carry official dates — nothing to prove. For everything else:

  • Printed date on the document. A copyright year, revision date, or journal issue date on the face of the document is usually sufficient. (In the worked example, the manual's "© 2019, Rev. B" line does this work.)
  • Wayback Machine captures. An archived copy with a crawl date is standard evidence for web material. Save the archive URL and include the capture date in your description of the document.
  • Library or database records. Journal indexing dates, ISBN records, and conference proceedings front matter.
Undated Documents Sink Submissions

A perfect technical disclosure with no provable date can be given no weight. Before you build a filing around a reference, make sure the date question is answered on the face of the document or by an archive record you can attach.

Search Technique: Elements, Not Titles

The most common amateur mistake is searching for the invention's name or the product category. Patents are granted on claim language, so search the way claims are written:

  1. Decompose the independent claim into its elements — the same first step as the drafting mapping technique. Three to six elements is typical.
  2. Search element combinations, with synonyms. A "controller that varies motor output based on rider torque" is also "torque sensor pedal assist," "pedelec proportional control," "cadence-torque motor controller." Engineers, marketers, and patent drafters use different vocabularies — cover all three.
  3. Chain citations. Every close patent you find links backward (its references) and forward (who cites it). Two or three hops from one good hit usually maps the whole field.
  4. Browse the classification. Find the CPC code on your best hit and browse adjacent documents in that class — this surfaces art that keyword searches miss entirely.
  5. Go where the engineers were. For software: RFCs, GitHub release histories, conference talks. For hardware: teardowns, FCC filings, distributor datasheets. The killer reference is often a document nobody ever indexed as "patent literature."

You're looking for references that disclose specific claim elements at specific locations — because that's what your Concise Description has to cite, and mapped submissions measurably outperform unmapped ones.

From Search to Filing

Once you have candidate references: rank them, check the window, decide whether filing now is actually the right move (a single silver-bullet reference may be worth holding for an IPR), then build the mapping and description per the Drafting Guide — or walk through the whole thing concretely in the Worked Example.