mpep.io

Corrections

Parts of this site are generated, and generated things are wrong sometimes. Reports are read and acted on, and they are the main way errors get found. Send one through the contact page.

Worth reporting

  • A holding summary that misstates the case
    The most useful report of all. Say which case and what the manual actually uses it for. These are model-written and none has been reviewed by a person yet, so an expert eye is genuinely the backstop — see methodology.
  • A citation link pointing at the wrong authority
    A case or statute link that resolves to a different one than the text names, or a cross-reference landing on the wrong section.
  • Section text that does not match the USPTO's
    Missing paragraphs, a truncated section, a table that lost its structure, a subsection attached to the wrong parent. Include the section number.
  • A subsection link that lands in the wrong place
    Subsections resolve to an anchor inside their file-level section. If one scrolls to the wrong heading, that is a bug here.
  • A section marked structured that clearly is not
    Or the reverse. Coverage is reported per section and should match what is actually there.

Not errors here

  • The MPEP itself being wrong or out of date
    The text is reproduced as published, at the pinned revision. If the manual says something you disagree with, or the USPTO has since changed it, that is not a transcription error and it will not be edited — that would break the thing that makes this citable. Later USPTO guidance is tracked separately.
  • A statute reading differently from the current U.S. Code
    Statutory text comes from the manual’s own appendices at the pinned revision, so it reflects the law as the manual reproduced it then, not as amended since.
  • A holding that is right but incomplete
    The summaries state what a case stands for as the MPEP uses it, in one sentence. They are not case briefs, and they are not a substitute for the opinion.

What helps

The URL, what you expected, and what you saw. For a holding, the proposition you would have expected instead. There is no need to write it up formally — a sentence and a link is plenty.

What happens next

Parsing and linking errors are fixed in the pipeline that produces them, so the fix applies everywhere the same fault occurred rather than only on the page reported. A corrected holding summary is recorded as a reviewed holding, which then shows the reviewer and date on the case page.