Patent Docketing That Reduces Deadline Risk

Current computed coverage focuses on supported PCT deadlines and U.S. office-action response chains. Each result carries its informational trust status and a derivation trace, and must be professionally verified. The unified docket also tracks annuities, provisional and national-phase matters, patent fees, and custom reminders; not every tracked date is a rules-based calculation.

Every deadline gets a 0 to 100 score blending four signals: time pressure (40%), type severity (25%), overdue cascade (25%), and assignment gap (10%). A score of 70 or higher is red, 40 or higher is amber, and anything lower is green. Scores roll up into a portfolio-level breakdown so managers get an at-a-glance health read. The score prioritizes workflow attention. It is not a legal assessment of the case or of the consequences of a missed date.

No. "Today" is computed in each tenant local timezone, so a deadline is not miscolored for a team in another part of the world. Annuity fees also track a grace-period end date, so the system separates "overdue but still payable in grace" from "truly lapsed."

Three automated jobs push deadlines out: a daily deadline digest (8 AM local, pre-sorted by risk), a reminder-due email the same morning, and a weekly stale-alert hygiene report on Mondays at 9 AM local. Sends respect each user notification preferences, are throttled to provider limits, and fail gracefully per user so one bad address does not block the batch.

It surfaces silent risks that no hard deadline would catch: families with no filings, stale PRV/PCT/NPE records, overdue open office actions, unpaid overdue fees, expired reminders, and stale families. It is the "what is slipping through the cracks?" view that date-only docketing misses.

Yes. Fees and annuities carry an amount and currency, and analytics roll up spend across the portfolio with date-accurate FX conversion into a single chosen reporting currency. Fees attach polymorphically to families, PRV, PCT, NPE cases, or office actions, so renewal exposure is visible at every level.

Every create, update, and delete on reminders, fees, and cases is logged with actor, before and after state, timestamp, IP, and request ID. Edits to sensitive fields require a typed reason, deletions always do, and tenant data is isolated with PostgreSQL Row-Level Security. Read versus write is enforced server-side per module.

Yes. The portfolio health report turns the live docket into a branded PDF in one click. It carries your organization logo and name, only the sections you select, and an optional as-of date, and it covers portfolio stats, family analytics, deadlines ranked by risk, annuity and patent fees grouped per currency, and stale-record alerts. Every report is stamped with a unique Report ID and a SHA-256 checksum written to your audit log, so a document you handed over months ago can still be verified against the record.

Yes. The Loss of Exclusivity timeline links each drug product to the patent families and regulatory exclusivities that protect it, then shows three numbers per jurisdiction and indication: the patent wall (the latest granted patent expiry), the regulatory floor (the latest active exclusivity end date), and the combined horizon, which is the later of the two. A live what-if lets you drop a patent family and watch every affected product recompute, so the cost of letting an annuity lapse is visible before the decision is made. The timeline visualizes the dates your attorneys record. It is a portfolio visualization, not a legal determination.

Annuity and renewal fees are tracked with amount, currency, due date, fee year, renewal year, and a grace-period end date. The engine derives each renewal deadline automatically from the case data, buckets it by urgency, and the daily digest surfaces it before it comes due, distinguishing "overdue but still payable in grace" from "truly lapsed."

Supported deadlines are computed on read from the case records rather than typed into a calendar, so they do not depend on someone remembering to add them. Unassigned deadlines are penalized in the risk score, abandoned or paid items drop out automatically, and three automated digests push what is due to the responsible owner. The weekly stale-alert report catches cases that are silently going wrong without generating a hard deadline. Accuracy still depends on the case data you record, and calculated dates should be verified by a qualified patent professional.

Most teams start with a bulk CSV import. You upload your existing portfolio and the system validates every row before anything touches the database, then creates families with their PRV, PCT, and NPE child records and key dates in a single atomic transaction with a full audit trail. Supported dependent deadlines appear automatically when the required source dates are imported.

Yes, on every plan, and without a support ticket. A tenant admin can export the entire account in one click: families, filings, PRV, PCT and NPE cases, office actions, fees, reminders, prior-art references, team roles, and the audit trail. The bundle ships as structured NDJSON with a JSON Schema for every dataset, plus CSV renderings of the common docket views, so it stays readable in Excel and parseable by another system. Each dataset carries a SHA-256 checksum, the whole export is a consistent point-in-time snapshot, and the export itself is audited and emailed to every admin. Individual users can export their own personal data from their profile.

It is a cloud web application with nothing to install. Every list view (deadlines, fees, families, PRV, PCT, NPE, and audit logs) supports one-click CSV export, bulk CSV import handles onboarding, and a REST API is available for custom integrations with existing firm systems.