Deadline Rules

Signa includes a rule-based deadline engine that computes upcoming maintenance deadlines for every registered trademark. Its rules cover every production office and more jurisdictions beyond them (see office coverage); GET /v1/deadline-rules lists them all. Some jurisdictions, such as the US and Canada, carry separate rule sets for domestic and Madrid registrations, and a Madrid designation of a jurisdiction with no rules of its own renews with the international registration at WIPO (see Madrid designations without their own rules). The engine produces actionable deadline objects with status, urgency, and consequence information.

How Deadlines Are Computed

Given a trademark’s date fields and jurisdiction, the deadline engine returns an array of computed deadlines. Each one carries its type, due date, urgency, grace period (where applicable), and consequence-if-missed information. The same inputs always produce the same output. Each computed deadline includes:

Field	Description
`type`	`renewal`, `declaration_of_use`, `combined_renewal_and_use`, `declaration_of_incontestability`, `restoration`, `international_renewal`
`occurrence_key`	Stable identity of this occurrence (`rule_id:<cycle>`, or `rule_id:t<term>-<n>` when the record has no statutory anchor), also the calendar event identity
`rule_id`	The statutory rule, the join key to List Deadline Rules
`due_date`	The date the deadline falls
`window_opens`	Earliest date you can file
`grace_expiry_date`	Last day of grace period (if applicable)
`is_recurring`, `is_optional`	Whether the deadline repeats, and whether the filing is optional
`status`	`future`, `window_open`, `due_soon`, `in_grace`, `missed`
`urgency`	`routine`, `upcoming`, `critical`, `in_grace`, `missed`
`days_until_due`	Signed integer (negative = overdue)
`consequence_if_missed`	What happens if you miss it entirely: see Consequence vocabulary

Consequence vocabulary

consequence_if_missed names the mechanism the office’s own provision prescribes when the deadline and any grace period pass. It is one axis only: whether a remedy exists afterwards is said by the presence or absence of a restoration rule for the jurisdiction, never by this value.

Value	Meaning	Examples
`expiration`	The right ends by operation of law when its term (plus any grace) runs out; no office act is needed and any later register entry only records it.	PL (“wygasa”), BR (“extingue-se”), MX (“caducará de pleno derecho”), JP, KR, TR, TH, FR, BX, US §9
`removal_from_register`	The statute makes the office’s striking of the entry the consequence (removed, deleted, gelöscht, udslettet, slettes, poistetaan, afmáð, “cancel the mark from the register”), usually with effect from the expiry.	EU (Art 53(8) EUTMR), DE (§ 47(6) MarkenG), DK, FI, NO, SE, IS, GB, AU, SG, IN, PH, CH, CN (商标法第四十条注销, which falls after the six-month 宽展期, i.e. after the term is already over)
`cancellation`	The office cancels a registration that is still within its term, as the sanction for a missed maintenance filing. Never a third-party action.	US §8 and §71 declarations of use. Also VN, whose label rests on no pinned primary text yet and is a promotion target rather than a verified mechanism.
`cancellation_and_expiration`	A combined US §8 + §9 filing: both consequences.	US ten-year renewal
`expungement`	Canada’s statutory word: the Registrar expunges the registration, deemed at expiry (s. 46(3)).	CA
`lapse_of_international_registration`	The Madrid international registration lapses at WIPO and every designation falls with it.	WIPO, and the Madrid renewal limbs served on a designation (`ca_renewal_madrid`, `mx_renewal_madrid`, `es_renewal_madrid`, `pt_renewal_madrid` and `madrid_designation_renewal`), which are renewed at WIPO rather than at the designated office
`permanent_loss`	Restoration rules only: the last available remedy has passed.	GB, SG, IN, IS, JP restoration, and EU restitutio in integrum (`eu_restitutio`)
`none`	An optional filing.	US §15 incontestability

irrevocable_loss was retired on 3 September 2026 (it described restorability, which the restoration rule already states); no rule serves it, and consumers that stored it should read it as the jurisdiction’s current value.

Consequence relabels, 4 September 2026

Nine rules changed their consequence_if_missed string in the 4 September 2026 release. No due date moved, no window opened or closed differently, and no rule was added or removed. Only the label changed: each of these now names the mechanism the office’s own pinned provision prescribes.

`rule_id`	Jurisdiction	Was	Is now
`bx_renewal`	BX (BOIP)	`irrevocable_loss`	`expiration`
`ch_renewal`	CH (IGE/IPI)	`irrevocable_loss`	`removal_from_register`
`de_renewal`	DE (DPMA)	`cancellation`	`removal_from_register`
`dk_renewal`	DK (DKPTO)	`cancellation`	`removal_from_register`
`eu_renewal`	EU (EUIPO)	`cancellation`	`removal_from_register`
`fr_renewal`	FR (INPI)	`cancellation`	`expiration`
`mx_declaration_of_use_3yr`	MX (IMPI)	`irrevocable_loss`	`expiration`
`pl_renewal`	PL (UPRP)	`cancellation`	`expiration`
`th_renewal`	TH (DIP)	`removal_from_register`	`expiration`

This shipped with no deprecation window, and it can, because consequence_if_missed is not a value you can pin. It is an open string, not an enum. The vocabulary table above describes the values in use today, not a closed set. Signa adds a value when a jurisdiction’s statute names a mechanism none of the existing labels fit, and edits an existing rule’s value whenever a better reading of the primary source arrives. Either can happen in any release, without notice. So do not branch on it. Anything conditional in your code should key on rule_id, which is stable and permanent, or on the structured fields that carry the arithmetic: type, grace_period_months, optional, and the presence of a restoration rule for the jurisdiction. consequence_if_missed is for display. If you persist it, persist it as free text, and re-read the current value from List Deadline Rules rather than treating your stored copy as authoritative.

Trigger Dates

Each jurisdiction defines a trigger field: the date from which deadlines are calculated. This varies by jurisdiction:

Trigger	Jurisdictions
`filing_date`	EU, DE, GB, CH, FR, BX, SE, AU, NO, DK, FI, IS, IT, PL, TH, VN, SG, TR, ES (domestic), PT (domestic)
`registration_date`	US (domestic), US (Madrid), CA (domestic), PH, JP, KR, CN
`grant_date`	BR, MX (domestic)
`priority_date`	IN (the filing date when the application claims no convention priority)
`intl_registration_date`	WIPO, CA (Madrid), MX (Madrid), ES (Madrid), PT (Madrid), EU (Madrid), every other Madrid designation (`madrid_designation_renewal`)

Two individual rules override their jurisdiction’s trigger: ph_declaration_of_use_5yr_madrid runs from protection_grant_date (the statutory anchor for a Madrid designation into IPOPHL), and in_renewal runs from priority_date, falling back to filing_date where a mark claims no priority. Some jurisdictions changed their trigger field on a specific date. For example, Sweden switched from registration_date to filing_date on 2019-01-01. The engine handles this automatically based on the mark’s filing date.

US Trademark Deadlines

The United States has the most complex deadline structure of any jurisdiction, because it requires proof of continued use in addition to renewal.

US Domestic Marks

Section 8: Declaration of Use (years 5-6)

Due: 6 years after registration
Window opens: 1 year before (year 5)
Grace period: 6 months (with surcharge)
Consequence if missed: Cancellation
Required for all US domestic registrations

Section 15: Declaration of Incontestability (years 5-6)

Due: Eligible from year 5, commonly filed with Section 8 by year 6
Optional: No penalty for missing it. A Section 15 affidavit can be filed after any later five-year period of continuous use, so once the first window has passed Signa no longer lists it as missed
Principal Register only: a Supplemental Register registration (register.type: "supplemental") gets no Section 15 row (15 U.S.C. 1094)
Benefit: Makes the registration conclusive evidence of validity
No grace period

Section 8+9: Renewal + Declaration of Use (every 10 years)

Due: 10 years after registration, then every 10 years
Window opens: 1 year before
Grace period: 6 months (with surcharge)
Consequence if missed: Cancellation and expiration
Not renewed: when Signa has the USPTO prosecution history, it records at least one Section 8 or Section 9 filing as an event by the computation date (such as the six-year Section 8; a Section 15 filing, or a filing known only from the status, does not count), the USPTO status, dated on or before the computation date, does not say the registration was renewed, and no Section 8 or Section 9 filing for the cycle is on record once its grace period has passed, the term on record ended: derived.term.state is renewal_not_on_record and no later cycle is served

US Madrid Marks

Madrid Protocol registrations designating the US use Section 71 (the Madrid equivalent of Section 8) instead of Section 8. The trigger date is the USPTO record’s registration_date: on a USPTO 79-series record it is the date the USPTO issued the certificate of extension of protection, which 15 U.S.C. 1141k uses for every Section 71 window. A US designation row that comes from WIPO’s records carries the date WIPO recorded instead, not the certificate date, so Signa serves it no Section 71 or Section 15 row: each rule is listed in unsupported_rules with reason: "computed_on_office_leg". Docket them from the USPTO record of the designation. The trigger is not the date of the statement of grant of protection (protection_grant_date in Compute Deadlines, protection_effective_date on a stored record), which usually comes months later; a window counted from it opens and closes late. Renewal is handled at WIPO, not at the USPTO.

Deadline	Trigger	Due	Grace
Section 71 (first)	registration_date	Year 6	6 months
Section 15	registration_date	Year 6	None (optional)
Section 71 (at renewal)	registration_date	Every 10 years	6 months

With Compute Deadlines, send the certificate date (the USPTO record’s registration date) as registration_date.

USPTO filings already on record

For a mark sourced from the USPTO, Signa reads the post-registration filings in its prosecution history (GET /v1/trademarks/{id}/events): Section 8, Section 15, Section 71 and the combined Section 8 and 9 renewal.

A declaration or renewal filed inside its window, from the day the window opens to the last day of the grace period, closes that cycle. It is no longer served as due, in grace or missed. A filing made before the window opens or after the grace period does not count.
The combined renewal needs both parts. A Section 8 or a Section 9 filing on its own leaves the cycle open, and so does an acceptance of one part only, even one recorded after the grace period. One part filed inside the window and the other accepted after the grace period close it together.
derived.expiry_date moves to the next term only once the USPTO accepts the renewal. A renewal that is filed and still pending closes the deadline but keeps the current term end.
On an older record with gaps in its history, a later accepted Section 8, Section 71 or renewal shows that an earlier mandatory cycle was met. A Section 15 acknowledgement never counts for this, and an acceptance of one part of the combined renewal does not close its own cycle.
A US designation ingested from WIPO’s records rather than the USPTO’s is served no Section 71 or Section 15 rows (see above). POST /v1/deadlines/compute with caller-supplied dates has no field for filings; send a trademark id to use the stored history.

# Get deadlines for a specific trademark
curl -s https://api.signa.so/v1/trademarks/tm_abc123 \
  -H "Authorization: Bearer sig_YOUR_KEY" | jq '.derived.deadlines.items'

const tm = await signa.trademarks.retrieve("tm_abc123");
for (const deadline of tm.derived.deadlines.items) {
  // Dates, not countdowns. Compare against your own clock for status.
  console.log(deadline.rule_id, deadline.window_opens, deadline.due_date);
}
// "us_declaration_of_use_s8"  "2030-01-20"  "2031-01-20"
// "us_renewal_s9"  "2034-01-20"  "2035-01-20"

USPTO post-registration office actions

When the USPTO examines a Section 8, Section 71 or combined Section 8 and 9 filing and finds a problem, it mails a post-registration office action. The filing still counts as made on time, but the registration is cancelled (or, for a renewal, expires) unless the owner responds in time. Signa serves that response as its own row:

type is post_registration_oa_response and rule_id is uspto_post_registration_oa_response, the same rule Compute Deadlines uses for caller-supplied facts. trigger_date and window_opens are the date of the action, trigger_field is post_registration_action, and occurrence_key is uspto_post_registration_oa_response:<action date>:<action code> (for example …:2026-04-19:PRA8), so two actions mailed the same day are two rows.
due_date is six months after the action, or the end of the filing period the action examined if that is later (37 CFR 2.163(b), 2.184(b)(1), 7.39(a)), moved to the next business day when it falls on a weekend or federal holiday. The grace period does not extend it, so grace_expiry_date equals due_date.
note names the action, for example PRA8 2026-04-19.
The row closes only on explicit evidence on record, dated after the action: a response naming the action’s section, the office’s acceptance of the filing the action examined, or a cancellation of that filing. A TEAS response that names no section closes it only when it is the one post-registration action open (an action mailed the same day counts). An entry dated the same day as the action does not close it. A Section 8-only acceptance after a combined Section 8 and 9 action leaves the row open for Section 9. A Section 8 action and a Section 9 action mailed the same day are two rows, and answering one leaves the other open; a later action never replaces an earlier one. An entry whose stored description Signa does not recognise neither opens nor closes a row.
If the response date passes with nothing on record, the row stays, as missed. The declaration or renewal row the action examined is not changed: the filing still counts as made. Whether the registration was lost is the USPTO’s call, and Signa reads it from the registration’s status. Once the status reads cancelled or expired, the schedule follows it like any other dead registration.
A 30-day notice of incomplete response does not say which response it is about, so it reopens every row it could concern, except for any part the office has already accepted. Neither the regulation nor the TMEP states that period, so Signa serves the earlier of 30 days after the notice and the original response date, and the note says to check TSDR. The date does not move later once it has passed.

When the record cannot settle the date, Signa does not guess a later one. The row stays open on the earliest date it can defend and the note says to check TSDR:

If the filing the action examined is not on record, or more than one filing could be the one, the row is due six months after the action, without the filing-period floor. After that date the row stays, as missed, until a response or an acceptance closes it.
A notice of incomplete response with no action on record is due 30 days after the notice. It stays until a response naming a maintenance section answers it, or a TEAS response naming no section arrives while it is the one action open.
An action mailed before 2015, when the rule Signa models took effect, is due six months after the action.

An action still open more than a year after its response date while the registration’s current status is registered is dropped: the USPTO would have cancelled the registration if the action had gone unanswered. A cancelled or expired registration gets no response row. Not covered: a petition to the Director after a maintained refusal (37 CFR 2.165(b)). When the USPTO mails an action marked “no response required”, the note of the open response row says so. If there is no such row, every row of the mark says so for six months. Actions on a Section 15 declaration alone are not covered either, because they cost the registration nothing. If the prosecution history cannot be read, every row of the mark carries a note saying so.

EU Trademark Deadlines

The European Union has a simpler structure. No proof of use is required at renewal.

Field	Value
Trigger	`filing_date`
Renewal cycle	Every 10 years
Window opens	6 months before due date
Grace period	6 months after due date
Consequence	Removal from register (`removal_from_register`)
Proof of use	Not required at renewal

These rules (eu_renewal, and eu_restitutio below) cover EU trade marks filed at the EUIPO. A Madrid designation of the EU, whether WIPO’s record of it (EM) or the EUIPO’s (EU on the Madrid route), renews with the international registration at WIPO; see Madrid designations without their own rules.

Jurisdiction Quirks

Germany (DPMA): End-of-Month Rule

For marks filed before 2019-01-14, the expiry date is the last day of the month in which the anniversary falls, not the exact anniversary date. For example, a mark filed on 2015-03-15 expires on 2025-03-31, not 2025-03-15. Marks filed on or after 2019-01-14 use the exact anniversary (standard behavior).

Canada (CIPO): Pre-2019 15-Year Terms

Canada changed its trademark law on 2019-06-17:

Before 2019-06-17: Initial term of 15 years, renewal every 15 years
On or after 2019-06-17: Initial term of 10 years, renewal every 10 years

Signa applies the correct term based on the mark’s registration date. Madrid designations of Canada are a different rule. Trademarks Regulations s. 143 states that “Section 46 of the Act does not apply in respect of a Protocol registration”, and s. 144(1) gives such a registration no Canadian term at all: it is on the register “for the period that begins on the day of the registration and that ends at the moment of its cancellation or expungement”. So a designation of Canada does not renew at CIPO. What falls due is the renewal of the international registration, at WIPO, and Signa serves it on the Canadian record as ca_renewal_madrid:

Field	Value
Trigger	`intl_registration_date`
Due	10 years after the international registration, then every 10 years
Window opens	6 months before (Madrid Regulations Rule 30(1)(b))
Grace	6 months, with a surcharge (Madrid Protocol Art. 7(4))
Consequence if missed	`lapse_of_international_registration`
Holiday calendar	`wipo_geneva`, the International Bureau’s, under Rule 4(4)

These are the same dates wipo_international_renewal computes on the WIPO record for the same international registration; the rule exists so a portfolio holding the Canadian designation, and not its WIPO parent, still sees the date that governs. Note that the roll differs from the Canadian route: a CA domestic renewal date is never rolled (Canada’s own config does not opt into the weekend/holiday roll, and reports not_checked), while this one is, because the period belongs to the International Bureau.

Nordic Countries: Trigger Field Change

Sweden and Denmark changed their trigger field from registration_date to filing_date on 2019-01-01, Finland on 2019-05-01. Norway made the same change earlier, on 2010-07-01. Iceland followed on 2020-09-01. The date Signa compares against the change date is not the same in every country. Signa resolves the correct trigger from the application date for Sweden, Finland, Norway and Iceland, and from the registration date for Denmark. Iceland’s pivot turns on the application date, not the registration date: applications received before 2020-09-01 keep a 10-year term measured from the registration date for every renewal, even where registration was granted after the reform, while applications received on or after that day take the 10-year term from the filing date (Act No. 71/2020 art. 39(3); Regulation No. 850/2020 art. 45(1)-(2)). Limit: old-regime records without a registration date. For Sweden, Iceland, Norway and Finland, a direct (national) record filed before the change date keeps the registration-date term, so its renewal needs the registration date. When the record carries no registration date and the office stated no term end, Signa declines instead of guessing: supported: false (or derived.deadlines.supported: false on a trademark) with reason: "requires_office_date", for every status except a mark that is finally dead (abandoned, withdrawn, surrendered, refused or invalidated). Previously Sweden and Iceland served a date measured from the filing date, and Norway and Finland returned an empty schedule reported as supported. A filing-anchored date is not a safe substitute: it can be early for one cycle and years late for the next. Two cases still compute:

Madrid designations are unaffected, because they renew on the international registration date, not on the national registration date.
An office-stated term end anchors the schedule: the office’s expiry_date or renewal_due_date (top-level dates are office-published only; on Compute Deadlines, a supplied renewal_due_date counts as office-stated).

Supplying the registration date also lets the schedule compute. Denmark is not affected, because its change date is compared against the registration date itself. The converse gap declines too. A record with no filing date and a registration on or after the change date takes the new term, which runs from the filing date it lacks, so it declines with reason: "requires_office_date" instead of returning an empty schedule reported as supported.

Portugal (INPI): Marks Granted Before 2019-07-01

Under the Industrial Property Code in force since 2019-07-01 (Decreto-Lei n.º 110/2018), a registration lasts 10 years from the filing date (art. 247.º). A mark granted before that date keeps the term of the previous Code, which ran from the grant (Decreto-Lei n.º 110/2018 art. 7.º n.º 2). The text does not say whether its later renewals run from the filing anniversary or from the end of that term, and a filing-anchored date for this cohort is early for the running term and late after it. So for a national mark granted before 2019-07-01, or with no grant date and filed before it, Signa declines with reason: "requires_office_date" unless the office’s term end is supplied (expiry_date or renewal_due_date). National dates are not moved off weekends or holidays (the Code’s periods are continuous, art. 27.º) and report not_checked. Every stored PT record today is a Madrid designation, which renews at WIPO on the international registration date (pt_renewal_madrid) and is not affected.

Madrid designations without their own rules

A Madrid designation whose jurisdiction has no rules of its own (Russia, Ukraine, Austria and 93 more codes in the data Signa holds today, historic ones such as DT, SU and YU included) is served one rule, madrid_designation_renewal. So is a Madrid designation of the EU, whether WIPO’s record of it (EM) or the EUIPO’s own (EU, Madrid route). The rule serves the codes WIPO designates, a pinned list: the WIPO Standard ST.3 codes of the 117 Madrid members (WIPO’s member list, status on 8 July 2026; the EU as EM, Belgium, Luxembourg and the Netherlands as BX), the territories the Protocol extends to (Curaçao CW, Sint Maarten SX, Bonaire, Sint Eustatius and Saba BQ, Guernsey GG, Jersey JE), and the historic codes WIPO’s register still carries (DD, DT, CS, SU, YU, and AN for the Netherlands Antilles). On POST /v1/deadlines/compute EM is read as EU and UK as GB (which has its own rules), and a code that is no jurisdiction code at all (ZZ) fails only its item with unknown_jurisdiction_code. Renewing a designation is not a national act: the international registration is renewed at WIPO by one payment, the renewal takes effect on the same date for every designation, and a later designation ends with the international registration (Madrid Protocol arts. 3ter(2), 6(1) and 7(1); Regulations Rules 30 and 31(2)). The rule is that renewal:

Parameter	Value
Term	10 years from the international registration date, or from the expiry WIPO states for the designation; a later expiry WIPO published for the international registration counts as its renewal. Every renewal is for 10 years: the Protocol has governed every designation since 31 October 2015 (WIPO Information Notice 39/2015)
Window opens	6 months before the due date (Regulations Rule 30(1)(b))
Grace period	6 months, with a surcharge (Protocol art. 7(4))
Closed days	Moved to WIPO’s next open day (Rule 4(4), `wipo_geneva`)
Consequence	`lapse_of_international_registration`
Rows carry	The designated jurisdiction’s code: `RU` on a Russian designation, `EU` on an EU one (WIPO’s `EM` included, as on the trademark row)

A designation with no international registration date and no stated expiry returns reason: "requires_office_date". A designation that WIPO reports refused, invalidated, surrendered, cancelled or expired past its grace gets no later renewal, even when the international registration was renewed for other countries. A designation whose own status is unknown is served like any other, but a later expiry WIPO published for its international registration is not credited to it: that renewal may have left it out (Regulations Rule 30(2)), so it keeps the term WIPO states for it, lapsed or not. The rule applies only to Madrid designations: a national record of one of these jurisdictions still returns reason: "unsupported_jurisdiction", and every other jurisdiction with its own rules (the US, Portugal and the rest of the table below) keeps them on every route. The EU designation follows WIPO, not the EUIPO renewal rules. The EUIPO does not handle renewal of international registrations designating the EU: WIPO receives the renewal fees and records the renewal (EUIPO Guidelines, Part E, Section 4, paragraph 12), so neither eu_renewal nor eu_restitutio is served on a Madrid designation of the EU, whichever office’s record it is. Both rules now say so in GET /v1/deadline-rules with applies_to: "domestic". EU trade marks filed at the EUIPO are unchanged. The rule is a renewal schedule and nothing else. Prosecution deadlines (facts[] on POST /v1/deadlines/compute) keep the jurisdiction’s own rules: a Madrid designation of the EU keeps the EUIPO provisional-refusal rule, and a jurisdiction without its own rules reads unsupported_jurisdiction for every prosecution type. GET /v1/deadline-rules lists madrid_designation_renewal once, under WO, named “International Registration Renewal (Madrid designations)”, and also returns it for ?jurisdiction= any code it serves (RU, EM, EU, …). Before 1 November 2022 renewal could be paid only 3 months ahead, not 6 (WIPO Information Notice 30/2022). That changes only window_opens of cycles due before about May 2023, all of them past, and the WIPO record’s own wipo_international_renewal serves the same 6 months, so it is not modelled. Renewal only. Cabo Verde, Cambodia and Mozambique also require use declarations filed directly with their national office: Cambodia declarations of actual use or non-use (WIPO Information Notice 11/2016), Mozambique a declaration of intention to use once per renewal cycle, within five years of the office being notified of the designation and then within five years of each renewal (Information Notice 37/2016), and Cabo Verde a declaration of intention to use every five years (Information Notice 27/2022; Cabo Verde’s Industrial Property Code, art. 165). The WIPO Guide to the Madrid System lists all three under “Maintenance (Use) Requirements”. Those dates depend on national events no record carries, so they are not computed, and every row of a designation of one of these three countries says so in its note, naming the notice. Mexico, the Philippines and the United States, the other countries in the Guide’s list, have their own rules, which compute their declarations, with one exception: for a Madrid designation of Mexico, the declaration of use due within three months of the WIPO Gazette publishing the international registration’s renewal (Information Notice 32/2024) is not computed, because no record carries that publication date.

Mexico: Post-Anniversary Windows

Mexico has a unique Declaration of Use requirement:

Due: 3 years after grant
Window opens: The day after the 3rd anniversary (not before)
Window duration: 3 months

This differs from most jurisdictions where the filing window opens before the due date. For a Madrid designation of Mexico, IMPI also requires a declaration of use within three months from the publication in the WIPO Gazette of each renewal of the international registration, once protection in Mexico has been in effect for at least three years (WIPO Information Notice 32/2024). That date depends on the Gazette publication, which no record carries, so it is not computed.

Philippines: Mixed Trigger DAUs

The Philippines requires Declarations of Actual Use at years 3 and 5 after filing, each with different extension rules. The year-3 DAU has a 6-month extension option.

China (CNIPA): The Term Counts Its First Day

Chinese registration terms run from the day the office approves the registration and count that day, so the term ends the day BEFORE the anniversary (Implementing Regulations art. 12(2)). A mark registered 2016-03-07 expires 2026-03-06, and its 12-month renewal window and 6-month grace period are measured from that expiry. Where the anniversary day does not exist in the target month the expiry is the last day of that month instead: a mark registered 2020-02-29 expires 2030-02-28, not 2030-02-27. Chinese deadlines roll to the next working day when they fall on a statutory holiday, and Signa builds that calendar from the State Council’s annual holiday notice, including the make-up working weekends (调休), where a Saturday or Sunday is declared a working day to lengthen a holiday block. A renewal due on Friday 2 January 2026 is therefore due on Sunday 4 January 2026, the first working day. Because each year’s notice is only published the preceding November, the calendar covers 2024–2026 today; deadlines beyond it take the deterministic roll and report due_date_adjustment: "not_checked"; opposition windows closing beyond it are published the same way, with close_adjustment: "not_checked" rather than guessed or withheld. An unverified date is never later than the true one, and silence on a rights-losing deadline is worse than an early date. The one case Signa still declines with window_not_computable is a close that falls in the 20 days before the date you are computing as of, where a rollover could still be holding the window open. A close on the as-of date itself, or more than 20 days before it, is published unverified like any other. The same applies to every calendar Signa builds from annual office notices: cgpdtm_india (one DoPT memorandum per year), wipo_geneva, ph_philippines and mx_mexico (IMPI’s yearly días inhábiles acuerdos). Check close_adjustment before treating a close date as verified. Two Chinese specifics on the opposition side. The 2026 revision of the Trademark Law cuts the opposition window from three months to two on 1 January 2027 (art. 36, in force by art. 87) and says nothing about a period still running on that day. Signa serves the shorter window to that straddling cohort, every publication from 1 October 2026, the first whose three months would still be open on commencement, because a close published too early costs a would-be opponent nothing they can lose by relying on it, while one published too late costs the right itself. A mark published 31 December 2026 is therefore reported as closing 28 February 2027, not 31 March 2027. This is a deliberate, reversible call: it flips back the day a transitional notice or the revised Implementing Regulations settles the question. The Madrid window is set by the Implementing Regulations instead (art. 45: three months from the first day of the month after the WIPO Gazette issue), and the 2026 law does not change it. CNIPA’s draft transitional measures, published for comment on 28 September 2026 and not yet in force, would apply the new two-month window to international registrations whose WIPO publication date is on or after 1 January 2027. Signa already serves that shorter window, counted from the publication date like a national mark, so an IR published 15 January 2027 is reported as closing 15 March 2027, not 30 April 2027. Like the national call, it can only be early, never late, and is re-checked when the final measures are published.

EU, UK, Singapore, Iceland, Japan, and India: Restoration Periods

These jurisdictions offer an additional restoration window after the grace period, during which a lapsed registration can be re-established. Missing it is a permanent loss in each of them.

Code	Window	Runs from
EU	6 months	Grace expiry
GB	6 months	Removal date
SG	6 months	Removal date
IS	2 months	Grace expiry
JP	6 months	Grace expiry
IN	6 months	Grace expiry

The EU window is restitutio in integrum (Article 104 EUTMR). Its end date is the outer limit only: the request must also be filed within two months of the removal of the obstacle, it is granted only where all due care required by the circumstances was taken, and it carries a fee. These windows apply to national (and EU) registrations only. A Madrid designation of any of these jurisdictions gets no restoration row: its term is the international registration’s, renewed only at WIPO with its own six-month grace (Madrid Protocol Article 7(4), Common Regulations Rule 30), and the national remedies are disapplied for it (Japan: Trademark Act Article 68-22(1); UK: Sch. 1 to the Trade Marks (International Registration) Order 2008, which disapplies sections 42 and 43 of the Trade Marks Act 1994). A cancelled designation is therefore served nothing, and an expired one only the international renewal while its grace is open. Transformation of a cancelled international registration into a national application (Protocol Article 9quinquies) is not served: it needs the cause and date of the cancellation, which the record does not carry. Offices often keep a lapsed mark at a live status for months after its term ended. When the office states a term end that has passed and the schedule carries a restoration window for that lapse, the schedule serves the lapsed renewal while it is still in grace and the restoration window, but no later renewal cycle: a mark cannot be both due for restoration now and due for renewal ten years on. While the restoration window is open, derived.expiry_date is that past term end and derived.term.state is in_restoration. The office’s own status and expiry_date are returned unchanged. What happens once the restoration window has closed too is described in The term on record.

The term on record

derived.expiry_date is the end of the term on record, and derived.term says where that term stands on as_of_date. Neither changes the office’s status. The term on record ends at the expiry the office states (expiry_date, or renewal_due_date where that is all it publishes), unless a renewal is on record that the office’s date does not show yet:

a renewal the office recorded (last_renewal_date) in that term’s renewal window or grace period, or later: a renewal by restoration, or one the office recorded months after the term ended (UK renewals often are);
for a Madrid designation, whether a national office’s record of it or WIPO’s own, an expiry WIPO published for the international registration in a later term, unless WIPO’s own record of the designation shows it ended in that country: expired, cancelled, surrendered, invalidated or otherwise inactive (a renewal that left the country out, for example). The term of a designation is renewed centrally at WIPO, and some offices keep the original term end on their own record (IP Australia does), as WIPO’s own record of one country can until it is rewritten. A WIPO date a few months off the office’s, in the same term, renews nothing. The designation’s deadline rows still give the office’s own dates as their trigger;
for the USPTO, which publishes no expiry, the Section 8 and 9 filings in the prosecution history (see USPTO filings already on record).

`term.state`	Meaning
`in_term`	The term runs to `derived.expiry_date`, and its renewal is not past due (the due date itself, moved off a weekend or holiday, is still on time).
`in_grace`	The term ended; the renewal can still be filed late, until `term.grace_expiry_date`.
`in_restoration`	The grace period passed and the jurisdiction’s restoration window is open, until `term.restoration_expiry_date`.
`renewal_not_on_record`	The expiry the office stated, its grace period and any restoration window have passed, and no renewal of that term is on record. For a US registration, also when no expiry is stated: its ten-year renewal (Section 8 and Section 9) is not on record once the grace period has passed, under the conditions in US Domestic Marks above.
`not_applicable`	No registered term to assess: an application or another status that is not registered, a dead mark, a record with no renewal rule (a US designation under the Madrid Protocol, renewed at WIPO), or no schedule. An `expired` mark is assessed only while it can still be renewed or restored, a `cancelled` one only while it can be restored.

An expired mark is served only what can still save it: a renewal while its grace period is open, any other row whose window is open at the computation date, and a restoration window. Once the grace period of its latest renewal whose window has opened has passed with no renewal on record, nothing due after that grace period is served, whether or not an expiry date is stated: the expired status says the term was not renewed, so the obligations of the next term (in the Philippines the declarations of use due within a year of the renewal and at its fifth anniversary) are not owed. A renewal whose window is open is always served. A renewal on record (last_renewal_date, a later stated expiry or, for a Madrid designation, a later expiry WIPO published) keeps the next term’s rows. When the state is renewal_not_on_record, derived.expiry_date stays at the past term end and no later term is computed: derived.deadlines.items has no renewal ten years on and derived.next_deadline is null. The same schedule is served on List Deadlines, portfolio deadlines and the calendar feed, Compute Deadlines and Reconcile. Before October 3, 2026 the next cycle was projected onto such a mark, so a mark surrendered in 2014 with a 2024 expiry showed a 2034 term end. A US registration with no stated expiry and no renewal on record kept the next cycle until October 9, 2026. renewal_not_on_record does not say the mark is dead. Some offices record a lapse months or years after the term ends, renewals reach their records late too, and Signa may not have captured a recorded renewal yet. The office’s status is the office’s answer; derived.term is what the record supports. An office that reports a mark expired the day after its term ends (the UK office does) is still in_grace, then in_restoration, until those windows close. A renewal on record moves the term on record to the next term, which reads in_term, even when the office has not advanced its own expiry yet. term.renewed says whether a renewal on record began the term ending at derived.expiry_date, that is, renewed the term before it: true once the office states a term end past the first term, recorded that renewal, accepted that USPTO renewal filing, or WIPO published an expiry in a later term for a Madrid designation; false for the first term after registration and for a term computed with no renewal of the term before it on record. A renewal of an earlier term does not count: a US registration of 1999 with only its 2009 renewal on record reads false for the term ending in 2029. A registered mark with no office-stated expiry (every USPTO record) keeps the statutory term end: without a term end on record, Signa cannot tell a missed renewal from one it has not captured, so the next cycle is still computed. Such a term reads term.renewed: false until a renewal is on record.

Accuracy limits

Signa’s default is to fail in the direction that cannot cost you a right: where a source runs out, a deadline is reported unadjusted or not at all rather than guessed, and an unadjusted date is EARLIER than the true one, so acting on it is still safe. The list below is the exception set: the places where a served date can be LATER than the true one. Later is the unsafe direction, because a filing made on the served date can land after the real deadline has passed. Each is bounded, each rests on a named gap in the primary sources, and each is listed here rather than left for you to discover.

Where	The served date can be later because	Bound
CN renewals and grace expiries falling on a weekend	Implementing Regulations art. 12(1) verifies only the roll off a statutory holiday (节假日). CNIPA is shut at weekends, but no instrument Signa has pinned says a weekend is a 节假日 for that purpose, so the plain weekend roll is the engine’s general assumption rather than a verified Chinese reading. If CNIPA does not roll weekends, the true date is the weekend day itself.	Only dates that land on a Saturday or Sunday, and only within the pinned calendar years.
IS renewals rolling off 24 or 31 December	L. nr. 88/1971 6. gr. and L. nr. 32/1997 2. gr. make aðfangadagur and gamlársdagur frídagar only from 13.00, so the statute alone gives a half day. Signa treats both as fully closed on the strength of Hugverkastofan’s own December 2020 opening-hours statement. If the office’s practice has changed since, the true deadline is the half day itself.	Only the two dates, and only where a deadline actually lands on one.
BX oppositions on marks published 1 August to 30 September 2013	The Protocol of 22 July 2010 moved BVIE art. 2.14(1) from “the first day of the month following publication” to “publication”, in force 1 October 2013. For that two-month cohort the old text’s window was still running when the new one came into force, and no instrument says which governs. Signa keeps the publication-date pivot, which serves the old text and therefore the later close.	A closed historical cohort: publications between 2013-08-01 and 2013-09-30.
CN Madrid oppositions on IRs published in the WIPO Gazette before 1 January 2027 whose window runs past that day	The Madrid window lives in 实施条例第四十五条 (three months from the first of the following month), which the 2026 Trademark Law leaves to the State Council and which is still unrevised. CNIPA’s draft transitional measures (published for comment on 28 September 2026, not in force) keep that window for IRs published before 1 January 2027 and apply the revised two-month window only from that publication date, and `cn_opposition_madrid` already serves the two-month window from then, opening it on the first day of the month after the Gazette and closing it two months after the Gazette date, the narrowest window any reading of the draft allows. If the final measures instead cut the window for IRs published earlier, a close served for one of them can be up to a month late.	Madrid designations published October to December 2026 only. Resolves when CNIPA publishes the final measures (comments close 12 November 2026); the item is on Signa’s standing source-invalidation checklist.
EUIPO deadlines rolling off an Article 2 day	The Executive Director’s annual decision lists two kinds of non-working day. On an Article 1 day the Office is CLOSED; on an Article 2 day (19 March, 23 June, 9 October, 8 December) it is open, only ordinary post is not delivered in Alicante. Signa rolls both, on the reading of Article 69(1) EUTMDR that the Office’s own decision states (EX-24-9 recital (1)(b)). The roll is right for a paper filing, but an e-filer can file on the original day, and if the Office ever reads Article 69(1) as extending only for post-borne filings, the true deadline is the original date and the served one is a day too late.	Four days a year, and only where a deadline actually lands on one. Nothing else moves.
DE renewals for an application filed before 14 January 2019 and still unregistered	The German month-end cohort is selected by `end_of_month_comparison_field: registration_date`. A still-pending pre-2019 application has no registration date, so the engine falls back to the filing date and treats it as old-cohort, emitting a month-end expiry. Once it registers on or after the cutoff the law gives it the exact anniversary instead, which is earlier. The alternative default would mis-date the far larger registered cohort, so the fallback stands.	A sparse, self-closing cohort: filed before 2019-01-14 and still not registered. Resolves the moment the mark registers.
TR deadlines rolling off a non-working day	No TÜRKPATENT instrument states a roll rule. Signa applies Türkiye’s general-procedure convention (HMK 6100 m. 93/1, İYUK 2577 m. 8/2), under which a period ending on a non-working day runs to the next working day. That is the ordinary reading of Turkish procedural law, but it is an inference about the Kurum’s practice rather than a rule the office has published, and if the Kurum does not follow it the true deadline is the non-working day itself.	Only dates landing on a Turkish non-working day, within the pinned calendar years.
CA opposition `common_extension` for windows closing before 17 June 2019	The 4-month benchmark first extension is verified for the Trademarks Opposition Board notice in force from 17 June 2019. The benchmark under the 2009 notice it replaced is not pinned, so an earlier window is served the 4-month figure with notes saying so, and the true figure may have been shorter.	Advisory only. `common_extension` is guidance about what the Board grants; it never moves `window_opens`, `window_closes` or `status`.

Everything else that is uncertain is reported the other way. A deadline outside a calendar’s pinned coverage reports due_date_adjustment: "not_checked" and keeps the deterministically rolled date, which can only be early; an opposition window Signa cannot compute is returned supported: false with a reason rather than a guess; and a record with no usable anchor returns no deadline at all. See Business-day adjustment for how the adjustment fields say which of these happened.

Covered Jurisdictions

GET /v1/deadline-rules is the current, authoritative list; the table below summarizes it.

Code	Office	Renewal Cycle	Trigger	Proof of Use
US	USPTO (domestic)	10 years	registration_date	Yes (Sections 8, 8+9)
US	USPTO (Madrid)	10 years	registration_date	Yes (Section 71)
EU	EUIPO	10 years	filing_date	No
DE	DPMA	10 years	filing_date	No
GB	UKIPO	10 years	filing_date	No
CH	IGE/IPI	10 years	filing_date	No
FR	INPI	10 years	filing_date	No
BX	BOIP	10 years	filing_date	No
SE	PRV	10 years	filing_date*	No
CA	CIPO (domestic)	10 years	registration_date	No
CA	CIPO (Madrid)	10 years	intl_registration_date‡	No
AU	IP Australia	10 years	filing_date	No
NO	NIPO	10 years	filing_date*	No
DK	DKPTO	10 years	filing_date*	No
FI	PRH	10 years	filing_date*	No
IS	ISIPO	10 years	filing_date*	No
PL	UPRP	10 years	filing_date	No
TH	DIP	10 years	filing_date	No
VN	IP Vietnam	10 years	filing_date	No
PH	IPOPHL	10 years	registration_date	Yes (DAU at years 3, 5)
BR	INPI Brazil	10 years	grant_date	No
MX	IMPI	10 years	grant_date	Yes (DU at year 3)
SG	IPOS	10 years	filing_date	No
JP	JPO	10 years	registration_date	No
IN	CGPDTM	10 years	filing_date	No
TR	TURKPATENT	10 years	filing_date	No
KR	KIPO	10 years	registration_date	No
CN	CNIPA	10 years	registration_date†	No
IT	UIBM	10 years	filing_date	No
ES	OEPM	10 years	filing_date	No
PT	INPI Portugal	10 years	filing_date§	No
WIPO	WIPO	10 years	intl_registration_date	No
Any other Madrid member (Madrid designation)	WIPO	10 years	intl_registration_date¶	No¶

‡ A Madrid designation of Canada has no Canadian term: Trademarks Regulations s. 143 disapplies Act s. 46 to a Protocol registration, so the renewal that falls due is the international registration’s, at WIPO. See “Canada (CIPO): Pre-2019 15-Year Terms” above. ¶ A Madrid designation of a jurisdiction without its own rules (a code WIPO designates), and a Madrid designation of the EU (EM or EU), renews with the international registration (madrid_designation_renewal); Cabo Verde, Cambodia and Mozambique also require national use declarations that are not computed. See “Madrid designations without their own rules” above. § Portugal: a Madrid designation of Portugal renews at WIPO on the international registration date (pt_renewal_madrid). A national mark granted before 2019-07-01 returns reason: "requires_office_date"; see “Portugal (INPI): Marks Granted Before 2019-07-01” above. † China counts the registration day itself, so a CN registration expires the day BEFORE the anniversary (registered 2016-03-07 → expires 2026-03-06). See “China (CNIPA): The Term Counts Its First Day” above. * Changed from registration_date: SE and DK on 2019-01-01, FI on 2019-05-01, NO on 2010-07-01, IS on 2020-09-01. Marks that fall before the change date keep registration_date for every renewal, but the date compared against the boundary differs by country: it is the application date for SE, FI, NO and IS, and the registration date for DK. Iceland’s boundary is keyed on the application date (Act No. 71/2020 art. 39(3); Regulation No. 850/2020 art. 45(1)-(2)).

Opposition windows are a separate engine

Everything above is the maintenance engine: renewals, declarations of use, grace and restoration. Opposition windows run on their own rule corpus, exposed through POST /v1/oppositions/compute and GET /v1/opposition-rules. One difference matters when you compute a window for a Madrid designation rather than a national filing. A designation has two publications that can fill one date field, WIPO’s Gazette of International Marks and the designated office’s own journal, and different offices run their clock from different ones: FR, CH and DE from the WIPO Gazette; GB, FI, PL, NO and the rest from the office journal. Send the optional publication_date_kind on your compute item and a rule that needs the other publication returns status: "unknown" with null dates rather than a wrong statutory bar. GB has no Madrid rule yet, because the current UK Journal source is not available to pin. The per-office table is in Opposition windows.

Filtering by Deadlines

Filters follow field names: expiry_date_* and renewal_due_date_* on Search Trademarks match the dates the office published, not the computed schedule. Offices that publish no such date never match them. The USPTO publishes no expiry date, and a renewal due date only on Madrid extensions (79-series), where it reports the international renewal date, so its domestic marks never match either filter. For the computed deadlines of the marks you manage, list them with List Deadlines for a portfolio or a trademark (with its due_before filter), or subscribe to the portfolio’s calendar feed. renewal_due_before was removed; use renewal_due_date_lt. For office-published renewal dates, use the renewal_due_date range:

curl -s "https://api.signa.so/v1/trademarks?renewal_due_date_gte=2026-01-01&renewal_due_date_lt=2027-01-01" \
  -H "Authorization: Bearer sig_YOUR_KEY"

const marks = await signa.trademarks.list({
  renewal_due_date_gte: "2026-01-01",
  renewal_due_date_lt: "2027-01-01",
});

Getting started

Core concepts

Build with AI

Data

Monitoring

Working with the API

Use cases

How Deadlines Are Computed

Consequence vocabulary

Consequence relabels, 4 September 2026

Trigger Dates

US Trademark Deadlines

US Domestic Marks

US Madrid Marks

USPTO filings already on record

USPTO post-registration office actions

EU Trademark Deadlines

Jurisdiction Quirks

Germany (DPMA): End-of-Month Rule

Canada (CIPO): Pre-2019 15-Year Terms

Nordic Countries: Trigger Field Change

Portugal (INPI): Marks Granted Before 2019-07-01

Madrid designations without their own rules

Mexico: Post-Anniversary Windows

Philippines: Mixed Trigger DAUs

China (CNIPA): The Term Counts Its First Day

EU, UK, Singapore, Iceland, Japan, and India: Restoration Periods

The term on record

Accuracy limits

Covered Jurisdictions

Opposition windows are a separate engine

Filtering by Deadlines

​How Deadlines Are Computed

​Consequence vocabulary

​Consequence relabels, 4 September 2026

​Trigger Dates

​US Trademark Deadlines

​US Domestic Marks

​US Madrid Marks

​USPTO filings already on record

​USPTO post-registration office actions

​EU Trademark Deadlines

​Jurisdiction Quirks

​Germany (DPMA): End-of-Month Rule

​Canada (CIPO): Pre-2019 15-Year Terms

​Nordic Countries: Trigger Field Change

​Portugal (INPI): Marks Granted Before 2019-07-01

​Madrid designations without their own rules

​Mexico: Post-Anniversary Windows

​Philippines: Mixed Trigger DAUs

​China (CNIPA): The Term Counts Its First Day

​EU, UK, Singapore, Iceland, Japan, and India: Restoration Periods

​The term on record

​Accuracy limits

​Covered Jurisdictions

​Opposition windows are a separate engine

​Filtering by Deadlines

How Deadlines Are Computed

Consequence vocabulary

Consequence relabels, 4 September 2026

Trigger Dates

US Trademark Deadlines

US Domestic Marks

US Madrid Marks

USPTO filings already on record

USPTO post-registration office actions

EU Trademark Deadlines

Jurisdiction Quirks

Germany (DPMA): End-of-Month Rule

Canada (CIPO): Pre-2019 15-Year Terms

Nordic Countries: Trigger Field Change

Portugal (INPI): Marks Granted Before 2019-07-01

Madrid designations without their own rules

Mexico: Post-Anniversary Windows

Philippines: Mixed Trigger DAUs

China (CNIPA): The Term Counts Its First Day

EU, UK, Singapore, Iceland, Japan, and India: Restoration Periods

The term on record

Accuracy limits

Covered Jurisdictions

Opposition windows are a separate engine

Filtering by Deadlines