Recovering a Missed PCT National Phase Entry via USPTO Restoration Petition

When the 30-month US national-phase deadline lapses, the application does not vanish — but the recovery route depends entirely on what was missed, and choosing the wrong petition wastes fees and time. This guide walks the decision: revival of an abandoned national stage for unintentional delay under 37 CFR § 1.137, reinstatement of rights under PCT Rule 49.6, and the distinct remedy of restoring the right of priority under 37 CFR § 1.452, together with the required statement, the fees, and the timing each demands.

The single most common error is treating all three as interchangeable “late-entry fixes.” They are not. Revival and reinstatement address a national stage that went abandoned because the 30-month acts were not performed; priority restoration addresses an entirely different failure — an international application filed just after the 12-month priority year. This page sits under the PCT National Phase Entry Rules framework and picks up exactly where a REVIEW_REQUIRED restoration flag from the entry engine leaves off.

Two Different Failures, Two Different Remedies

Before selecting a petition, classify the failure. The table separates the recovery paths by what actually lapsed.

The first two paths overlap heavily in US practice: the USPTO implements PCT Rule 49.6 reinstatement through the same unintentional-delay machinery as 37 CFR § 1.137, so a national stage that became abandoned for failure to perform the 37 CFR § 1.495 acts is revived on a petition, a fee, and a statement that the entire period of delay was unintentional. The third path — 37 CFR § 1.452 — is a fundamentally different remedy that a docketing system must not conflate with late entry.

Operational Action: Before opening any petition, record which deadline lapsed — the 30-month entry acts or the 12-month priority year — because that single fact selects the remedy and every downstream fee and statement.

Path A: Reviving the Abandoned National Stage

If the 30-month acts were not performed, the national stage is abandoned under 37 CFR § 1.495(h). The cure is a petition under 37 CFR § 1.137(a) accompanied by four things: the required reply (the national-stage entry acts that were missing — basic national fee, translation, oath), the petition fee under 37 CFR § 1.17(m), a statement that the entire period of delay from the due date to the filing of the petition was unintentional, and, where the delay is lengthy, additional information the Office may require to support the unintentional statement.

Because the standard is that the entire delay was unintentional, a gap between discovering the miss and filing the petition can itself defeat the showing. The petition must be filed promptly once the lapse is known, and any period of deliberate inaction after discovery undermines the statement.

Operational Action: File the revival petition the moment the lapse is confirmed and timestamp the discovery date in the audit log — the “entire delay unintentional” statement covers the gap up to filing, so an internal delay after discovery is itself a defect.

Path B: Restoring the Right of Priority (Do Not Confuse)

Restoration of the right of priority under 37 CFR § 1.452 is not a late-entry cure. It applies when the international application itself was filed after the 12-month Paris Convention priority period but within two months of its expiration. On a petition, the prescribed fee, and a statement that the failure to file within twelve months was unintentional (the USPTO applies the unintentional standard; some receiving offices apply the stricter “unavoidable” or due-care standard), the priority claim is restored — which in turn re-anchors the 30-month national-phase clock to the earlier priority date.

The docketing distinction is sharp: a Path A revival restores an abandoned entry; a Path B restoration restores a priority claim and therefore changes the base date every downstream deadline is computed from. Feeding a restored priority date back through the entry engine recomputes the national-phase window and every child deadline, which is why priority-chain integrity — the subject of the broader detecting broken priority chains in PCT filings work — must be re-validated after any restoration.

Encoding the Decision in Code

A docketing system should classify the failure and route to the correct remedy deterministically rather than leaving it to ad-hoc judgment. The classifier below keys off which deadline lapsed and returns the applicable rule, fee code, and required statement:

from datetime import date
from dataclasses import dataclass
from dateutil.relativedelta import relativedelta

@dataclass(frozen=True)
class RecoveryRoute:
    remedy: str
    rule: str
    fee_code: str
    statement: str

def select_recovery_route(
    priority: date, intl_filing: date, entry_deadline: date, today: date
) -> RecoveryRoute:
    """Pick the USPTO recovery path from what actually lapsed."""
    # Priority year first: was the international application itself filed late?
    priority_year_end = priority + relativedelta(months=12)
    restoration_window_end = priority_year_end + relativedelta(months=2)
    if priority_year_end < intl_filing <= restoration_window_end:
        return RecoveryRoute(
            remedy="Restoration of the right of priority",
            rule="37 CFR 1.452",
            fee_code="37 CFR 1.17(m)",
            statement="failure to file within 12 months was unintentional",
        )
    # Otherwise, a lapsed 30-month entry is a revival case.
    if today > entry_deadline:
        return RecoveryRoute(
            remedy="Revival / PCT reinstatement of rights",
            rule="37 CFR 1.137(a); PCT Rule 49.6",
            fee_code="37 CFR 1.17(m)",
            statement="entire period of delay was unintentional",
        )
    raise ValueError("No lapse detected — nothing to recover")

# International app filed 40 days after the priority year -> priority restoration.
route = select_recovery_route(date(2022, 3, 1), date(2023, 4, 10),
                              date(2024, 9, 1), date(2024, 10, 1))
assert route.rule == "37 CFR 1.452"

Operational Action: Never auto-file a petition — the classifier only flags the route; the petition, statement, and any explanation of a lengthy delay are attorney work that must clear human sign-off before submission.

Timing and Fees at a Glance

Each path carries its own fee and its own timing discipline. Both petition fees are set by 37 CFR § 1.17(m), and both statements turn on the unintentional standard, but the triggering events differ.

For a petition filed well after the lapse, the Office may require additional explanation supporting the unintentional statement, so the audit trail should preserve the discovery date, the internal handling timeline, and the reason for any delay. The same unintentional-delay machinery governs reviving a lapsed granted patent for missed maintenance fees, covered in reviving a lapsed patent with a USPTO unintentional-delay petition, so a firm can share one petition workflow across both.

Frequently Asked Questions

Related

• PCT National Phase Entry Rules — the entry engine whose restoration flag hands off to these recovery paths.
• USPTO vs EPO National Phase Entry Differences — how the missed-deadline consequences diverge by office.
• Reviving a Lapsed Patent: USPTO Unintentional Delay Petition — the same 37 CFR 1.137 machinery applied to missed maintenance fees.
• Detecting Broken Priority Chains in PCT Filings — re-validating the chain after a priority restoration.

↑ Back to PCT National Phase Entry Rules