USPTO being helpful about IDSs that did not get considered

click to enlarge

Beginning a couple of years ago, some very nice people in the Issue Branch at the USPTO have promoted patent quality, and have promoted science and the useful arts, and have saved us as patent practitioners from a lot of stress and malpractice risk, by looking out for IDSs that have not been considered.  In the past, we as patent practitioners had to pester the Examiners to consider such IDSs.  Those very nice people in the Issue Branch at the USPTO do the pestering for us nowadays.  I am guessing I will never get to learn the names of those very nice people, and will never have the opportunity to thank them directly.  All that I can do, I guess, is thank them in this blog.  Maybe someone at the USPTO who knows who those nice people are can print out this blog article and show it to them. 

For the reader to fully appreciate the helpfulness of these nice people in the Issue Branch, a bit of background is called for.

When I launched my own patent firm, a very long time ago, one of the first things that we did was to set up “IDS logs”.  In each trifold paper file (yes, this was in the days of trifold paper files) there was a brightly colored piece of paper dedicated to the logging of Information Disclosure Statements.  (As I recall we eventually decided that this document was so important that we would keep it topmost on top of the drawings in the “drawings” section of the trifold file.)  The idea of this log is that each time we were to file an IDS, we would make note of it in the log.  Each time that an Office Action arrived, we would look to see whether we had received or had not received from the Examiner a signed copy of the IDS, acknowledging that the Examiner had reviewed the references cited in the IDS.  This “looking to see” process got repeated when the Notice of Allowance arrived from the USPTO.

Crucially, when the Notice of Allowance arrived, we would consult the IDS log to see if it listed any IDS that had not yet been considered by the Examiner.  And if the answer was “yes”, we would do what we called “docketing aggressively”.  This meant checking the status of the problem very often, no less often than weekly, and if more than a couple of weeks were to pass without the errant IDS getting considered we would start making telephone calls.  The timing and urgency of the calls would of course be tied to how close we were to the abandonment date for payment of the Issue Fee.  The first telephone call was to the Examiner.  If only a few days remained, then we would push it very hard — if 24 hours were to pass with no signed IDS from the Examiner, we would call the SPE (the Examiner’s supervisor).  If 24 hours were to pass and still no signed IDS had arrived from the Examiner, we would call the Director of the Technology Center.  If another 24 hours were to pass and still no signed IDS had arrived from the Examiner, we would call the office of the Commissioner for Patents.  Eventually a harried Examiner would promise that he or she had indeed considered the IDS.  Surely that was enough for us, the verbal promise, the Examiner would plead?  

Nope.  We needed to see that the Examiner had not, for example, “lined through” some reference on this signed IDS that we had not yet seen.  We needed to see it with our own eyes.  Could the Examiner fax the signed IDS to us, we would ask?  No, that was not proper procedure, the Examiner would tell us.  So then there would be another series of calls to the SPE and to the Director of the Tech Center and so on until someone would make an executive decision to pop the signed IDS onto a fax machine to us so that we could see with our own eyes that the Examiner had actually signed the IDS and had not “lined through” any references.

When the time came to get ready to pay the Issue Fee, our internal procedure was to start all over again with a review of the IDS log, just as if we had never reviewed it before.  What if somehow when we did the review at the time of the arrival of the Notice of Allowance, we had somehow forgotten to take a look at the IDS log?  This was our chance to correct that lapse.  But more importantly, what if we had filed yet one more IDS even after the arrival of the Notice of Allowance?  This would have gotten logged on the IDS log.  And at the time of getting ready to pay the Issue Fee, we would want to see if such a thing had happened in that particular file.  (Maybe it was the kind of IDS where an appropriate certification had been made, as well as payment of an appropriate fee, in which case the Examiner was indeed obligated to consider that IDS despite its tardy arrival into the case.)  And indeed if the review of the IDS log at the time of getting ready to pay the Issue Fee revealed that there was at that time some outstanding IDS, then once again we would commence a course of “aggressive docketing”.

A further moment of background needs to be established, namely to discuss “why is this important?”

The reason that this is important is that TYFNIL an unconsidered IDS in a patent file wrapper will be an invaluable gift to the accused infringer.  Able counsel, representing the accused infringer, will have no difficulty finding real or imagined reasons why the references cited in that IDS, had they only been considered by the Examiner, would supposedly have made all the difference in the world as to what was patentable and what was not.  It is easy to imagine fact patterns where the presence of an errant IDS like this could completely derail an otherwise lucrative patent license, or could greatly diminish the settlement value of an infringement claim.  

Not to put too fine a point upon it, but a patent owner facing such a lost patent license or devalued settlement might well choose to assert a malpractice claim against the patent practitioner who paid the Issue Fee while failing to notice that there was an unconsidered IDS floating around in the patent file.

Which brings me to the main point of this blog article.  The main point of this blog article is that starting around two or three years ago, people in the Issue Branch at the USPTO apparently decided that part of their job included IDS logging.  Yes, when the time came for Final Data Capture, they would look through IFW to find all of the IDSs that had been filed, and would match them up against the signed IDSs appearing in IFW.  If everything matched, then that was one thing.  But if the review by the Issue Branch person revealed the existence of an IDS that had been timely filed and had not yet been considered by the Examiner, then the Issue Branch person would swing into action.

The procedure that the Issue Branch person follows is the creation what they call a “printer rush”.  Here is how a “printer rush” is described in MPEP section 1309.02:

When the printer finds an apparent error in an application or other issue which prevents publication, the file is returned to the examiner, a “Printer Rush” form is included in the Image File Wrapper (IFW) and is indicated with a “RUSH” document code, noting the supposed error or issue. Additional issues which may prevent publication until they are resolved include but are not limited to: amendments under 37 CFR 1.312, a Request for Correction of Inventorship under 37 CFR 1.48 and Information Disclosure Statements which have not been initialed by the examiner.  These applications are placed on the examiner’s “expedited” tab in Docket Application Viewer (DAV) and should be taken up for immediate action.

(emphasis added.)  MPEP section 708.01 (“List of Special Cases”) instructs the Examiner:

All allowed cases returned to the examiner marked as a “Printer Rush” must be processed and returned within the period indicated.

It means that our escalating sequence of telephone calls to the Examiner, to the SPE, to the Director of the Technology Center, and to the Commissioner for Patents, to get an outstanding IDS considered, are nowadays almost never needed.  It means that someone at the USPTO does the pestering of the Examiner instead of our having to do the pestering of the Examiner.

Quoted above is a Supplemental Notice of Allowability that arrived today in one of our firm’s allowed cases.  The case got allowed on July 2, 2020, but there was an outstanding IDS.  The Issue Branch person created a “printer rush”.  The Examiner indicated at Box 1 of this Supplemental Notice that it was prompted by “Printer Rush of 8/12/2020”.  The entire point of this Supplemental Notice is the check-box indicating that a signed Information Disclosure Statement is attached.  It is this Supplemental Notice that prompted me to write today’s blog article.

Does this practice by the Issue Branch mean that we can simplify our checklist of things that we do when we receive a Notice of Allowance or get ready to pay an Issue Fee?  Can we skip the step of checking for ourselves to see if all of the IDSs have been considered?  In our firm, we continue to feel that the answer is “no”.  We still check these things.  We do not assume that the USPTO people are going to catch every errant IDS.  But in recent years I must acknowledge with some admiration that the USPTO people have not slipped up on even one of our files.  It has not happened even once in these past couple of years, when we did our IDS check at Notice-of-Allowance time and found that there was indeed an outstanding IDS, that the USPTO people failed to create the needed “printer rush”.  

So thank you to these nice Issue Branch people, whose names I imagine I will never learn.  Thank you.

Turning to our dear reader … in your practice, did you formerly maintain IDS logs?  Do you still maintain IDS logs?  When you receive an Examiner-signed IDS, do you invariably scan it in trepidation, wondering if this is an IDS where some reference got “lined through”?  Were you aware of this nice IDS-logging activity by the Issue Branch people?  Please post a comment below.

6 thoughts on “USPTO being helpful about IDSs that did not get considered

  1. I like the IDS log you mentioned, and it’s nice that the PTO is also looking for unconsidered IDSs. But I worry that relying on perfect bookkeeping in the past, by either applicant or the PTO, defeats a Case-Is-Ready-to-Issue review for latent defects. In the PTO’s review for IDSs that the Examiner might not have fully considered, does a person review the entire file, or do they rely on some automation feature, including perhaps the correct coding of IDSs in the IFW? When I do a Case-Is-Ready-to-Issue review, I page through everything in the file wrapper without regard to the document code, and if something looks like an IDS, I would see it.

  2. I have not used a log, but checking that all references on all IDSs have been considered has always been on my allowance checklist. Since the Patent Office went all electronic, I find it helpful to sort the IFWs by document name to find all the IDSs quickly. Neil makes an excellent point about coding, but I can our internal documents sort using our document management system and compare numbers.

    We have had to, in the past, call to nudge some examiners to sign off on an IDS or two after receiving a Notice of Allowance. I cannot recall having to do that for the past several years, however. I believe I have just learned why. I expect just the knowledge that these helpful persons in the Issue Branch will be reviewing the file for such mistakes may prompt some examiners to do so themselves.

    I third, or fourth, the thanks to these helpful persons in the USPTO.

  3. Each time we file an IDS, we docket a date a year from the IDS filing for the task “expect Examiner to consider IDS#”. This task remains open until we see that the Examiner returned a signed copy of the IDS. We also check to see whether any disclosed items were crossed through (that is, not considered), and then determine whether an additional IDS needs to be submitted. I prefer not to wait until the application is allowed, because filing an IDS after allowance may require an RCE (if the disclosed items have been known for more than 3 months).

Leave a comment

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

This site uses Akismet to reduce spam. Learn how your comment data is processed.