Madrid Protocol Software: Managing International Trademark Registrations

Why Madrid registrations don't fit a normal trademark record

A trademark filed directly in one country is a single, self-contained record: one application, one office, one renewal date. A trademark filed through the Madrid Protocol is structurally different — it's a single **International Registration (IR)** held with WIPO, with a separate designation in each country the applicant named. Each designation can move through examination independently: one country might grant registration while another issues a provisional refusal, on the same underlying IR.

Software that treats a Madrid filing as just another row in the trademark table loses that structure. The parent-child relationship — one IR, many designations, each with its own status — needs to be modeled directly, or a firm ends up tracking it in a side spreadsheet regardless of what system they paid for.

What Madrid-aware trademark software should track

The essentials

• The International Registration itself — IR number, IR date, holder, and the base mark it was built from.
• A designation per country — each with its own status (pending, provisional refusal, registered, etc.), linked back to the parent IR.
• A WIPO-cycle renewal date — Madrid registrations renew on a schedule tied to WIPO, not necessarily the same cadence as a nationally-filed mark in the same country.
• Open-item visibility — a fast way to see which designations still have something outstanding (a provisional refusal to respond to, an examination pending) across the whole IR portfolio.

Catching marks that were filed via Madrid but never flagged correctly

In practice, portfolios accumulate a specific kind of data-quality problem: a mark was actually filed through Madrid, but somewhere along the way it got recorded as a plain national filing — the IR number ended up in a notes field instead of a structured one, if it was recorded at all. That mark's renewal date is now wrong, because national and Madrid renewal cycles don't necessarily match.

A useful system doesn't just store Madrid data correctly going forward — it helps a firm find and fix marks that were mis-recorded in the past. That means scanning existing records for signals (an "IR" number pattern, mentions of "Madrid" or "WIPO" in notes or references) and surfacing the marks worth a second look, then correcting the record — reclassifying the filing route and recalculating the renewal date onto the correct WIPO cycle — in a couple of clicks rather than a manual audit.

Multi-jurisdiction reporting, done through one lens

The other practical benefit of modeling Madrid properly is reporting. Once designations are structured data rather than notes, a portfolio-wide view can answer questions like "how many of our Madrid designations are still open" or "which countries carry the most outstanding Madrid matters" directly — the same kind of jurisdiction-level reporting covered in our guide to trademark software for the GCC and Middle East, extended to cover international filings alongside direct national ones.

How IPBases handles Madrid: the 2026 module

Updated August 2026: everything described above now ships as a dedicated Madrid module in IPBases, rather than a modeling recommendation:

• IR as a parent record — the International Registration holds the IR number, IR date, holder and base mark, with a designation row per country underneath it. Each designation carries its own status and can be linked to a national trademark record.
• Madrid sweep — a built-in scan of your existing portfolio that surfaces marks showing Madrid signals (IR-number patterns, WIPO/Madrid mentions in notes) and lets you flip a mis-recorded national filing onto the Madrid route — recalculating the renewal onto the WIPO cycle — in one click.
• Central attack / ceased basic mark — if the basic registration ceases, the IR record reflects it so dependent designations are flagged instead of silently looking healthy.
• Per-IR sync and reporting — refresh an IR’s designations and answer “which designations are still open, and where” from structured data, not notes fields.

For the full list of what shipped alongside it, see What’s new in IPBases (2026).