A Post-Grant Review (PGR) petition is one of the least forgiving documents in patent practice. It’s filed once, it locks in the grounds and evidence the Patent Trial and Appeal Board (PTAB) will consider at institution and formal defects – not just substantive weaknesses – can get a petition rejected, expunged, or stripped of key arguments before the Board ever reaches the merits. Proofreading a PGR petition is therefore not a final spell-check pass; it’s a compliance review against a specific set of PTAB rules, layered on top of ordinary legal and technical accuracy checks.

This guide sets out the document standards that matter most, organized the way a thorough pre-filing review should actually run.


1. Formal Requirements Under 37 CFR § 42.6

Every paper filed in a PTAB trial proceeding – including a PGR petition – must comply with baseline formatting rules:

A proofreading pass should confirm every one of these mechanically, not just visually – font substitutions during drafting (a pasted claim chart in a different font, a table imported from Excel) are a common, easy-to-miss defect.


2. Word-Count Compliance Under 37 CFR § 42.24

PGR petitions are governed by a word limit, not a page limit: 18,700 words, per 37 CFR § 42.24(a)(1)(ii). This is the same limit that applies to covered business method (CBM) petitions and is materially higher than the 14,000-word limit for inter partes review (IPR) petitions – a distinction worth double-checking if a template is being reused across proceeding types.

What counts toward the limit and what doesn’t:

A compliant petition must include a certification of the word count. Proofreading should verify that:


3. Substantive Content Requirements Specific to PGR

Beyond formatting, 37 CFR § 42.204 sets out content the petition must affirmatively include and a proofreading pass should trace each requirement to a specific location in the document:

A useful proofreading technique is a traceability check: build a table mapping every claim element and every asserted ground to the specific exhibit citation supporting it and confirm the exhibit actually says what the petition claims it says. Gaps here are a leading cause of institution denials that have nothing to do with the underlying merits of the invalidity theory.


4. Exhibit and Evidence Presentation Standards

PGR petitions typically depend heavily on supporting evidence – prior art references, expert declarations and technical documents – and the Board’s exhibit-numbering and labeling conventions are strictly enforced:


5. Mandatory Notices and Procedural Housekeeping

Under 37 CFR § 42.8, every petition must include mandatory notices identifying real parties in interest, related matters (including related litigation and other PTAB proceedings involving the same patent) and lead/backup counsel. Proofreading should confirm:


Key Takeaway

Because a PGR petition largely locks in the case a petitioner gets to make, proofreading it is a compliance exercise as much as a language-quality one. The formatting and word-count rules are mechanical and unforgiving, the content requirements under 37 CFR § 42.204 need to be affirmatively traceable rather than just implied by the narrative and the exhibit/citation architecture needs to hold together under scrutiny before the Board – or the patent owner – finds the gap first.

Leave a Reply

Your email address will not be published. Required fields are marked *