Skip to main content
Fix Errors in Rowan Patents Prosecution

Examiner's typos, OCR gibberish, incorrect art citations, misidentified issues, fix them all before building your response package.

Laura Berwick avatar
Written by Laura Berwick
Updated this week

Even USPTO examiners are only human, and optical character recognition success relies on the quality of the content scanned. Our Rowan Patents Prosecution module puts the power to make immediate corrections in your hands at every step of the response process.

Look below for guidance on:

  • Missing/Incorrect Cited Art

  • Extra, Mislabeled, or Missed Issue Statements

  • Claim and Office Action Text Errors

  • Bibliographic Information Errors

  • Going Back Later for More Corrections


Missing/Incorrect Cited Art

Rowan Prosecution uses the unique U.S. Patent number to download cited art references. By far the leading cause of incorrect or missing reference art is either a typo by the Examiner or an OCR error in this number.

We not only list the detected art for your reference as you work, but we also let you add, delete, and edit that listing, and will re-query our sources based on your changes.

  1. Edit cited art by clicking the pencil icon that appears when you hover over an art listing in the left-hand sidebar, as shown in the above video.

  2. Delete cited by clicking the trashcan icon that appears next to the pencil icon.

  3. Add additional art references by clicking the plus sign (+) next to the "Cited Art" list heading.


Extra, Mislabeled, or Missed Issue Statements

Our aim as we analyze your Office action is to identify exactly and only the issues you'll want to respond to. But we'd rather note more than you need than leave any out.

So we've included an interface letting you add, remove, and modify your identified issues, letting you zero in on exactly what your response needs to address.

  1. Edit the text identified as part of an issue and/or the type of issue identified by clicking the gray highlighted issue text, selecting "Modify" from the options presented, and following the guidance provided.

  2. Remove an identified issue by clicking the gray highlighted issue text and selecting "Remove" from the options presented.

  3. Add a new issue by selecting the desired text, clicking the "Add Issue" button to the upper right, and selecting the desired options.


Claim and Office Action Text Errors

Sometimes text is just misrecognized and ends up wrong in the Prosecution module. To help, we provide all claims and Office action text in editable fields where you can make immediate corrections before generating your response package.

  1. Identify errors you wish to correct.

  2. Click into the editable text fields provided and make your corrections.

Note that this is NOT the place to make the claim amendments you wish to include in your response. Those can be made in the Response Writer when your package is built, and automatic markup styling and status indicator updates will be applied.

Also note that there is no need to correct Office action OCR errors unless the text will be included in your response (such as issue statement text), or unless you desire to do so for improved clarity going forward.


Bibliographic Information Errors

Sometimes bibliographic information can't be retrieved from Patent Center or identified in an uploaded Office Action. We've made those fields editable so you can fill in anything that's missing, or make any corrections you see might be needed.

  1. Identify errors you wish to correct.

  2. Click into the editable text fields or select the dropdown menus provided and make your corrections.

Note that fields with missing information will be highlighted red so you can readily locate what needs correction.


Going Back Later for More Corrections

Once you've saved your .rpr package file, are you stuck? Of course not. You can go back at any time to make corrections.

  1. Click the "Package" tab.

  2. Click the Go "Back to Package Builder" link.

  3. Make the changes you wish in the Package Builder tabs.

Did this answer your question?