Timezone correct
"Today" is computed in the tenant timezone, so a deadline is not shown overdue a day early, or late, for a team in another part of the world.
Loading
Enterprise Trust
Controls shown reflect the current product architecture during private beta. Independent security assurance reports have not been issued yet.
Built for regulated patent teams handling confidential invention data, audit-sensitive workflows, and multi-jurisdiction portfolios.
Design Your Invention Team
IP Management Platform
One missed annuity payment or office-action response can cost a client an entire patent. Docketing is built as an audit-first engine that derives supported statutory and procedural deadlines from your case data, scores each one by risk, and pushes it to the responsible owner before it comes due. Every calculated date stays reviewable, and remains subject to verification by a qualified patent professional.
Deadlines are not a manual calendar. A single engine derives every statutory and procedural deadline across the entire case hierarchy and presents them in one prioritized, filterable view, each bucketed by urgency from overdue through upcoming and tagged with its family, assignee, and (for fees) amount and currency.
| Deadline Type | Derived From | Sub-types |
|---|---|---|
| Office Action Response | NPE office actions (due date) | Non-final, Final, Advisory |
| Annuity / Renewal Fee | NPE annuity fees (due date + grace period) | On-time, In-grace window |
| PCT Deadlines | PCT filings | Chapter I (Rule 22), Chapter II (Rule 30/31) |
| PRV Deadlines | Provisional applications | Expiry, Conversion deadline |
| Patent Fees | Fees on any entity | Across 8 fee categories |
| NPE Deadlines | NPE cases | Patent expiry, Request for Examination (RFE) |
| Custom Reminders | User-created reminders | One-time or recurring |
"Today" is computed in the tenant timezone, so a deadline is not shown overdue a day early, or late, for a team in another part of the world.
Annuity fees track a grace-period end date, so the system distinguishes "overdue but still payable in grace" from "truly lapsed."
Abandoned, granted, or already-paid items drop out of the active deadline view automatically, so the list stays the work that actually remains.
Every deadline gets a 0 to 100 risk score and a traffic-light level, so attorneys triage by workload pressure rather than date order alone. The score is a weighted blend of four signals, and scores roll up into a portfolio-level breakdown for an at-a-glance health read. Scores rank what needs attention first. They are not a legal assessment of the case.
How close, or how far past, the deadline is. Overdue items spike toward 100.
Office actions (90) and annuities (80) outrank routine reminders (20).
Already-overdue or open past-due items escalate sharply rather than plateauing.
Unassigned deadlines are penalized. An orphaned deadline is a dangerous deadline.
Docketing does not wait for users to log in. Three automated digest jobs push deadlines out, each respecting user notification preferences, throttled to provider limits, and failing gracefully per user. A fourth report goes further and catches what date-only docketing misses entirely.
Every morning at 8 AM in each tenant local timezone, every user gets the deadlines coming due within a configurable window, pre-sorted by risk.
The same morning send for custom reminders falling due that day, so team-specific tasks land alongside statutory deadlines.
Mondays at 9 AM local, a hygiene report of the things quietly going wrong that no hard deadline would surface.
A docket opened but never built out, sitting empty and forgotten.
PRV, PCT, or NPE entities untouched past a threshold (default 90 days).
Past due and still not responded, the single most expensive thing to miss.
Annuities past due, surfaced with grace-period and amount context.
Pending reminders whose date has already passed without action.
Active families with no updates inside the threshold window.
Fees, outside counsel, family health, dashboards, and bulk operations all feed the same prioritized deadline view, so the docket reflects how patent work actually flows. The same data becomes a branded PDF report for a client or an auditor, it can leave in a format you own whenever you want it, and it rolls up into the protection horizon of every product it covers.
Track patent and annuity fees with status, due date, amount, and currency. Analytics roll up spend across the portfolio with date-accurate FX conversion into one chosen currency.
A searchable, tenant-scoped roster of firms and agents, with per-case assignments by role (lead counsel, local agent, foreign associate, annuity provider) and duplicate-assignment protection.
Each family gets a 0 to 100 data-completeness score across family fields, child coverage, and child quality, turning "is this docket set up correctly?" into a measurable number.
Status breakdowns across families, PRVs, PCTs, NPE cases, office actions, annuities, and reminders, plus deadline-window counts and the aggregate risk breakdown, as of any chosen date.
Onboard whole portfolios in one pass, importing families with their PRV, PCT, and NPE child records and key dates, with validation and column mapping.
Filter deadlines by type, family, priority, date range, and assignee, with a "mine only" view for limited-permission users. Export deadlines, fees, and entity lists to CSV.
Turn the live docket into a client-ready document. The portfolio health report carries your logo and organization name, the sections you choose, and an optional as-of date, with deadlines ranked by risk, 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, and the preview and the download are byte identical. A report you handed a client months ago can still be verified against the record.
Export the whole account, not just a view. Families, filings, cases, fees, reminders, and audit history come out as structured NDJSON with schemas and CSV renderings, on every plan. Each user can also export their own personal data from their profile.
Docketing tells you what is due. The LOE timeline tells you what it is worth. Link every drug product to the patent families and regulatory exclusivities that protect it, then read the protection horizon per jurisdiction and indication.
Before you let an annuity lapse, drop the family in the live what-if and watch every affected product recompute, so the blast radius is visible before the decision is made.
OncoNova B1 · EP
Product-widePatent wall
2048-02-15
Regulatory floor
2041-07-01
Combined horizon
2048-02-15
EP 4 512 880 B1
granted
EP26890001.4
granted
Pediatric
revoked · product-wide
Market protection
active · product-wide
PCT context
Recorded national-phase deadline
PCT context
Recorded national-phase deadline
Horizons are built from the dates your attorneys record. A portfolio visualization, not a legal determination.
Docketing inherits the platform multi-tenant, audit-first architecture. The same controls that make the platform defensible in enterprise procurement apply to every reminder, fee, and case.
Every create, update, and delete on reminders, fees, and cases is logged with actor, before and after state, timestamp, IP, and request ID. Report generation and data exports are audited the same way, and an account export requires a typed reason and notifies every admin.
Edits to sensitive fields such as dates and statuses require a typed reason, and deletions always do. The field is required rather than optional, following 21 CFR Part 11 patterns.
Every query runs under PostgreSQL Row-Level Security inside a tenant-scoped transaction. Defense-in-depth tenant isolation is designed to prevent one firm from reaching another firm docket.
Read versus write is enforced server-side per module (prv, pct, npe, and the rest). "View all reminders" versus "only mine" is a permission, not a UI toggle.
How deadlines are derived, scored, and surfaced before they come due.
No. Supported deadlines are computed on read from the underlying case records, not entered manually. The moment you set a filing date or a publication date, every dependent statutory and procedural deadline the engine supports appears automatically and recalculates when those source fields change. Dates the engine does not derive stay under your control as custom reminders, and all dates should be verified by a qualified patent professional.
Seven types across the whole case hierarchy: office action responses, annuity and renewal fees, PCT deadlines (Chapter I Rule 22 and Chapter II Rule 30/31), PRV deadlines (expiry and conversion), patent fees, NPE deadlines (patent expiry and request for examination), and custom reminders. Each is bucketed by urgency from overdue through upcoming.
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. Because deadlines are derived on read, every dependent deadline appears automatically the moment the 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.
Book a walkthrough on a sample portfolio, or explore free patent search to start building families that feed the deadline engine.
Calculated dates are workflow aids, not legal advice. Coverage depends on the case data you record, and every date should be verified by a qualified patent professional before it is relied on.