Litigation Docketing for IP Teams: 9 Critical Tests

Ask a docketing vendor whether it handles litigation docketing and the answer is always yes. Ask which rule it applies to compute the answer date in a TTAB opposition, and the room goes quiet. Prosecution deadlines and proceeding deadlines are produced by different machinery: one runs from a statutory anchor that never moves, the other from a scheduling order that moves constantly. Most IP teams buy a platform built for the first and improvise the second in a shared calendar. These nine tests separate the two engines, with the governing rule cited for each.

Litigation Docketing and Prosecution Docketing Are Two Different Engines

A prosecution docket computes dates from an anchor that never moves. A registration issues on a date, and the Section 8 window opens five years later whether anyone touches the file or not. You can recompute that date from the registration certificate alone, ten years after the fact, and get the same answer.

A proceeding docket does the opposite. Its dates come from an order, and orders get reset. The Trademark Trial and Appeal Board issues an institution order, then resets it when a party moves for an extension, when a motion suspends proceedings, or when the parties stipulate to a new schedule. Nothing in the registration certificate tells you what the current trial calendar looks like.

That is the whole distinction, and it is why litigation docketing is a different product problem from prosecution docketing. One engine needs a rules table keyed to statutes. The other needs an event log keyed to orders, where the newest order supersedes everything before it and every downstream date recalculates.

Clock	Anchor date	Who sets it	Can it move?	Example
Prosecution / maintenance	Filing, registration or grant date	Statute and rule	No — the window is fixed by law	Section 8, years 5–6 after registration
Office action response	Issue date of the office action	Statute, with one extension	Only by the one permitted extension	3 months, plus one 3-month extension
Board proceeding	Publication date, then the institution order	The TTAB	Yes — resets are routine	Answer, discovery, trial periods
Federal court	Service, filing or the court’s order	FRCP plus local and standing rules	Yes — continuously	Scheduling order under Rule 16

Most IP teams own a platform built for the first column and improvise the last two in a shared calendar. That works until a proceeding runs long enough to collide with a maintenance window — which, as Test 5 shows, is not a hypothetical.

Test 1: Does It Compute the Opposition Window, or Just Store It?

Publication starts a 30-day opposition clock. What happens next is the single best test of whether a system understands Board practice, because the extension scheme in 37 CFR 2.102(c) is tiered, conditional and capped.

• First request: either a 30-day extension, “which will be granted upon request,” or a 90-day extension, available only for good cause shown.
• Second request: a potential opposer who took the 30-day extension may request a further 60 days, “which will be granted only for good cause shown.”
• Final request: after extensions totalling 90 days, one final 60-day request, which requires the applicant’s written consent or a showing of extraordinary circumstances.
• Hard cap: “The time for filing an opposition shall not be extended beyond 180 days from the date of publication.”

Two branches share the same 180-day ceiling but are not interchangeable. A party that takes the 90-day route lands at day 120 from publication and has one final 60-day request left. A party that takes 30 then 60 also lands at day 120, by a different path. A system that simply adds 30, 60 or 90 days to whatever the user typed will happily generate a date past the cap.

This is the first thing to put in front of a vendor, because it is where a general calendar and a real litigation docketing engine diverge in one screen. Ask to see the deadline a docket produces after a first 90-day extension. If the system cannot tell you how many requests remain and what the remaining one requires, it is storing the date rather than computing it.

Test 2: Does the TTAB Institution Order Drive the Whole Trial Calendar?

When an opposition is filed in proper form, the Board institutes the proceeding and issues an order that sets the answer date and the full trial schedule. Under 37 CFR 2.106, the Board designates a time “not less than thirty days” for the answer; in current practice the institution order customarily sets it at 40 days from the institution date.

That distinction matters for docketing. Thirty days is the regulatory floor, not the deadline. The deadline is whatever the order says, which means the order — not the rule — is the source of truth. A system that hard-codes 30 days from institution will be ten days early every time, and a docket that is systematically early trains people to ignore it.

The same order sets the discovery conference, the opening and close of discovery, the pretrial disclosure dates and each party’s trial period. These are not independent entries. They are one schedule, and a proper litigation docketing record stores them as one schedule attached to one order.

Failure to answer has a cascading effect the docket should model: under the rule, an untimely answer may lead to judgment by default, and the failure to file a timely answer tolls all deadlines, including the discovery conference, until the default question is resolved. A docket that keeps counting down the discovery conference while default is pending is showing dates that no longer exist.

Test 3: When One Date Moves, Do the Other Twelve Move With It?

This is the test that separates a genuine proceedings module from a calendar with IP labels on it. Ask the vendor to reset a mid-case deadline and watch what happens downstream.

In Board practice a suspension, a consented extension or a granted motion does not move one date. The Board issues a new order that resets the remaining schedule wholesale. The correct system behaviour is to supersede the prior schedule, recalculate every open date from the new order, and retain the old schedule as history rather than deleting it.

The failure mode is subtle and common: the system updates the date the user edited and leaves the rest of the trial calendar showing the superseded dates. Nobody notices, because the edited date is the one the paralegal was looking at. The pretrial disclosure date three months out is now wrong and will stay wrong until someone reads the order again.

• Does a reset create a new schedule version, or overwrite the old one?
• Are superseded dates retained and viewable, or gone?
• Does the system flag open dates that the new order did not address?
• Can you see which order each live date derives from?

If the answer to the last question is no, the docket cannot be audited — and an unauditable docket is the one that fails when it matters. Our trademark docket audit checklist covers how to test this on a live system.

Test 4: Are Prosecution Clocks Kept Separate From Proceeding Clocks?

The 2020 Trademark Modernization Act changed the response window for trademark office actions, and the change has three parts that a docket has to model separately.

• Pre-registration office actions: since 3 December 2022, the response period is three months for applications filed under Section 1 or Section 44, with one available three-month extension, for a maximum of six months from the issue date.
• The extension is not automatic: it must be requested before the response is filed, must be received on or before the initial deadline, and is subject to a fee (currently $125 through TEAS — check the live fee schedule before you rely on it). Only one extension request is permitted per office action.
• Section 66(a) applications are carved out: the USPTO states that applicants under the Madrid-based Section 66(a) basis “must respond within six months from issue date, with no option to extend the deadline.”
• Post-registration office actions: the same three-month-plus-extension structure took effect on 7 October 2023, after the USPTO delayed its original implementation date.

That Section 66(a) carve-out is the one that catches systems out. Two office actions issued on the same day, on two applications in the same portfolio, can carry genuinely different deadlines — three months plus a purchasable extension for one, a flat six months with no extension for the other. A docket that applies one rule to both is wrong about one of them.

We cover the response clock in depth in our trademark office action deadline guide.

Test 5: Does a Pending Proceeding Block the Section 15 Filing?

Here is where the two engines have to talk to each other, and where most setups quietly fail.

A Section 15 declaration converts a registration into an incontestable one. The USPTO states three conditions: the mark is registered on the Principal Register, it has been in continuous use in commerce for at least five years after the registration date, and there are no adverse decisions or pending proceedings involving rights in the mark.

Read the third condition against a live docket. A pending TTAB cancellation — an entry that lives in the proceedings engine — disqualifies a filing that lives in the maintenance engine. If those two engines are separate systems, or separate tabs nobody reconciles, the firm can file a Section 15 declaration that is defective on its face.

The reverse trap is worse, and it is the one to test for. Maintenance deadlines do not pause because a proceeding is running. The Section 8 declaration is still due between the fifth and sixth anniversaries of registration; the combined Sections 8 and 9 renewal is still due between the ninth and tenth years and every ten years after that, with a six-month grace period and an additional fee at each stage. A cancellation action does not toll any of it.

So the correct test is a two-way one: can the system surface a pending proceeding when someone opens a Section 15 filing, and can it keep a Section 8 window visible while the same mark is in litigation? Our trademark renewal deadlines guide sets out the maintenance calendar in full.

Test 6: Does It Watch the Madrid Five-Year Dependency?

The Madrid Protocol is where a proceeding in one country becomes a portfolio event everywhere else, which makes it the clearest case for holding both engines in one record.

Article 6(2) of the Protocol provides that an international registration becomes independent of the basic mark “upon expiry of a period of five years from the date of the international registration.” Before that, under Article 6(3), protection may no longer be invoked if the basic application or registration is withdrawn, lapses, is renounced, or is the subject of a final decision of rejection, revocation, cancellation or invalidation. This is what practitioners call central attack.

The detail that most dockets miss sits in the rest of Article 6(3). An appeal, an action seeking revocation or cancellation, or an opposition to the basic application that was commenced before the five-year expiry still brings down the international registration if it results in a final adverse decision after the five years have run. The dependency risk does not end cleanly on the fifth anniversary; it ends when every proceeding pending on that date is finally resolved.

That is a proceedings fact that has to be recorded against a prosecution record. A system that closes the dependency watch on the anniversary date is closing it too early.

If the worst happens, transformation is the remedy, and it is short. Article 9quinquies allows a national or regional filing to keep the international registration’s date, provided “such application is filed within three months from the date on which the international registration was cancelled.” Three months, in every designated territory you want to keep. That is a docket entry, not a memory exercise — see our Madrid Protocol deadlines guide.

Test 7: Does It Docket the Federal Court Case At All?

Trademark disputes do not stay at the Board. Infringement claims go to federal district court, and court deadlines come from a third rules system entirely: the Federal Rules of Civil Procedure, plus each district’s local rules, plus the individual judge’s standing orders.

This is genuinely hard software, which is why court-rules calculation is usually sold as its own product with its own rules-maintenance staff. Being fair about the category matters here: an IP docketing platform that does not compute court dates is not defective, it is scoped. The question for a buyer is whether anyone has decided where those dates will live.

Alt Legal, writing about its own dispute module, notes that many IP docketing systems are not designed to handle disputes and require a separate module, which pushes subscribers to docket disputes in litigation-focused systems or in basic calendars. That is the vendor describing the category honestly, and it matches what most firms actually do.

• Where does the Rule 16 scheduling order get docketed, and who reads it in?
• If the court case and the TTAB proceeding involve the same mark, do both appear on the mark’s record?
• Is a suspension of the Board proceeding pending the civil action recorded on both files?
• Who is accountable when the two systems disagree?

A small team can answer “a shared calendar, and the associate reads the order” and be perfectly safe — provided that is a decision rather than an accident. Scoping litigation docketing deliberately is a defensible answer; discovering after the fact that nobody scoped it is not.

Test 8: Who Owns the Date, and Can You Prove It?

Every docketing failure post-mortem reaches the same question: who was responsible for that date, and what did the system show them?

In prosecution work the answer is usually clean, because the docket clerk enters dates from documents that arrive on a predictable cadence. In proceedings work it is murkier. Orders arrive by email, deadlines get discussed in correspondence, and extensions are agreed between counsel before anything is filed. The date can change in a phone call and reach the docket days later.

The controls that hold up under scrutiny are unglamorous. Every live date should name the document it came from. Every change should record who made it, when, and against which order. Anything entered from correspondence rather than a Board or court order should be flagged as provisional until the order lands.

Two-person verification is worth the friction on the dates that end matters: the opposition deadline, the answer date, the Section 8 window and the transformation window. Our trademark docketing checklist covers the quarterly version of this review, and our catalogue of trademark docketing errors covers what happens when nobody owns the date.

Test 9: What Survives Migration and Audit?

The last test is the one buyers postpone: what happens to proceeding records when you change systems.

Prosecution data migrates reasonably well, because the fields are standard and the dates are recomputable. If a Section 8 window arrives wrong, you can regenerate it from the registration date. Proceeding data has no such safety net. A trial schedule is the product of an order history, and if the migration carries only the current dates, the reasoning behind them is gone.

• Does the export include superseded schedules, or only live dates?
• Does each date retain its source document reference after migration?
• Can proceeding records be exported in a format you can read without the vendor?
• After the cutover, can you recompute prosecution dates independently and reconcile them against the imported set?

That last reconciliation is the only real proof the migration worked. Recompute what is recomputable, compare it to what arrived, and investigate every difference. Our trademark docket migration guide sets out the full sequence.

Sources

• 37 CFR 2.102 — Extension of time for filing an opposition
• 37 CFR 2.106 — Answer
• USPTO — Response time period
• USPTO — Post-registration office action deadlines (7 October 2023)
• USPTO — Keeping your registration alive (Sections 8, 9, 15, 71)
• WIPO — Guide to the International Registration of Marks (Madrid Protocol Articles 6 and 9quinquies)

Taken together, these nine tests describe what litigation docketing has to do that a prosecution docket never does: derive every live date from the most recent order, recalculate the rest when that order is replaced, and keep the result reconcilable against the statutory clocks running alongside it. Run the tests against a live system rather than a feature list. Feature lists say yes to everything; a system that is asked to reset a trial schedule in front of you cannot.

How PerspireIP Can Help

PerspireIP runs managed trademark docketing for firms and in-house teams that want statutory windows computed from their anchors and proceeding schedules driven by the order that actually governs them. Every date carries the document it came from.

We reconcile the two engines the way Test 5 describes: maintenance windows stay visible while a proceeding runs, and a pending proceeding surfaces before anyone files a Section 15 declaration. If you are migrating, we recompute what is recomputable and reconcile it against what arrived.

Frequently Asked Questions