IP Docketing Automation

Deterministic patent & IP deadline tracking, portal sync, and audit-ready compliance — done right.

🌐 www.ip-docketing.com →

---

What this is

IP Docketing Automation is a deep, production-grade reference for the engineers and paralegals who build and run patent docketing systems. Every guide favors operational accuracy and reproducible implementation over theory: exact statutory rule logic, jurisdiction-aware date arithmetic, portal-sync patterns, and cryptographically chained audit trails you can actually ship.

In IP docketing, a single mis-rolled date is a malpractice event, not a rounding error. This site treats deadline calculation as the deterministic compliance discipline it really is — the same filing event must produce the same defensible due date every time it is computed, years apart, on any machine.

Who it's for

• IP paralegals & docketing managers who need the rules behind the dates to be explicit, defensible, and reproducible.
• Law-firm operations leaders enforcing service levels and audit readiness across a portfolio.
• Legal-tech developers & Python automation engineers building docketing infrastructure against USPTO, EPO, and WIPO systems.

What's inside

The material is organized into four engineering tracks, each mapping to a real production concern:

• Core Docketing Architecture & Deadline Types — the reference architecture, the governing statutes (PCT, EPC, 35 U.S.C.), a canonical ingestion-to-audit pipeline, jurisdictional isolation, maintenance-fee and continuation/CIP tracking, and tamper-evident compliance boundaries.
• Automated Deadline Calculation & Rule Engines — type-safe, timezone-correct date arithmetic; version-pinned rule registries; priority-chain validation; and patent term adjustment.
• Patent Office Portal Sync & Data Ingestion — authenticated feeds, async polling, schema validation, OCR for legacy documents, and resilient retry/backoff against USPTO, EPO, and WIPO endpoints.
• Docket Alerting, Escalation & Compliance Reporting — turning computed deadlines into timely, escalating, auditable action: reminder cadences, escalation ladders, malpractice compliance reporting, and docket-health dashboards.

Why it's different

• Deterministic by construction. Identical inputs always yield an identical due date and an identical audit hash. Base date, period length, and holiday calendar are treated as three independent, separately versioned inputs.
• Grounded in the real rules. Every deadline cites the exact statute, article, or rule number and links the official source — 37 CFR, the EPC Implementing Regulations, the PCT, and the WIPO/USPTO/EPO developer portals.
• Real, runnable code. Python 3.11+ with explicit type annotations, zoneinfo (never pytz), calendar-correct month arithmetic, and Pydantic validation at every boundary.
• Audit-grade. Append-only, hash-chained ledgers; role-based access; and reproducible compliance exports built to survive malpractice review.

About this repository

This repository holds the source for the site — an Eleventy static site with hand-authored inline SVG diagrams and structured data (JSON-LD) on every page.

npm install      # install dependencies
npm run build    # build the static site into _site/
npm run deploy   # build and deploy to Cloudflare

Content lives under content/ as Markdown; templates, styles, and assets live under src/.

Explore

→ www.ip-docketing.com — start with any of the four tracks above, or browse every guide from the homepage.

---

_{Authored and maintained by IP Docketing · Patent / IP Docketing & Deadline Tracking Automation}