The agent network behind your IP: Why it matters more than you think

Every IP team knows the work happens locally. Rights are territorial, most offices require foreign applicants to act through a locally registered representative or to maintain a local address for service, and a portfolio spanning thirty jurisdictions can mean thirty separate sets of procedural rules applied by as many separate firms. The requirement varies by action: a straightforward annuity payment often does not need local representation, while a recordal or a response to an office action usually does. None of that is news to anyone who has managed a global portfolio.

What gets less attention is who those firms actually are, how they were selected, and what happens when one of them underperforms. Provider evaluations tend to concentrate on pricing, platform, and service levels. The agent network, the infrastructure that executes every instruction in every jurisdiction, is usually assumed rather than assessed. Coverage maps get reviewed. Selection criteria, audit practice, sub-agent disclosure, and fee structure rarely do.

That gap matters because the network is where operational risk concentrates. A provider’s platform can be excellent and its reporting current while a filing in a single jurisdiction sits with a firm that is overloaded, unresponsive, or quietly working through a third party you have never been told about. Portfolios do not fail at the provider level. They fail in one jurisdiction, on one deadline, and usually without warning.

Coverage is the baseline, not the differentiator

Most providers can produce a map showing global reach. What that map does not show is whether the firm in each of those jurisdictions was selected against defined criteria, is reviewed on an ongoing basis, and is working at a volume it can actually absorb.

Capacity is the first thing to check, because it is where performance quietly degrades. A firm that handles occasional filings well may not have the staffing to process a large annuity cycle without errors accumulating. Those errors tend to surface as small things first: a confirmation that arrives late, a fee paid at the wrong rate, a docket entry that does not match the register. A provider should know, from its own data rather than the agent’s assurances, which firms in its network handle what volumes and to what standard.

The second is substantive capability. Responding to an office action, curing a formality defect, or dealing with a local requirement such as a legalized power of attorney is not administrative work, and the difference between a firm that handles it and one that forwards it back to you is the difference between a matter that stays on track and one that consumes your team’s week.

The third is verification. There is a meaningful gap between a provider that relays an agent’s confirmation and one that checks the register itself before confirming to the client. Relaying means the provider’s records are only as accurate as the agent’s reporting. Independent verification is what catches the payment made against the wrong application number, or the renewal recorded in a national system that does not match what the agent reported. That check is not visible in any coverage map, and it is the clearest signal of whether a network is managed or simply listed.

Where weak networks create exposure

Sub-agents you were never told about. A provider appoints a firm in one jurisdiction, and that firm routes the work to another. Nothing about this is inherently improper, and in some markets it is unavoidable. The problem is disclosure. If you do not know who is handling the file, you cannot assess their capacity, you cannot confirm there is no conflict, and you have no line of accountability when something goes wrong. Ask whether sub-agents are used and whether they are named.

Conflicts. The firm maintaining your portfolio in a given jurisdiction may also act for your competitor, or may be adverse to you in an opposition elsewhere. Screening practice varies between providers, and whether it happens at all is a fair question to put to yours. For routine renewal work the risk is low, but it is not zero, and it rises once a matter becomes contentious.

Lapses that are recoverable, but not cheaply. A missed annuity deadline is often recoverable. Article 5bis of the Paris Convention requires member countries to allow a grace period of not less than six months for the payment of maintenance fees, subject to a surcharge where national law provides for one. Beyond that grace period, the same article gives member countries the right to provide for restoration of lapsed patents, but does not require it, so whether a lapsed right can be revived at all depends on the jurisdiction. Where restoration exists, the standard differs: the EPO requires all due care under Article 122(1) EPC, while the USPTO applies an unintentional standard. Requests that fail to meet the stricter standard are refused. The point is not that a missed deadline destroys the right. It is that recovery costs a surcharge, then agent time, then a petition that may not succeed, and that the exposure is uneven across a portfolio because the rules are not uniform.

Fee structures that cannot be audited. When agents invoice independently, in their own currencies, on their own cycles, the true cost of the portfolio becomes difficult to forecast and harder to check. The questions that matter are narrow and specific. Are official fees passed through at cost, or marked up? What exchange rate is applied, and on what date? Are agent charges disclosed in the estimate, or billed after the fact? A provider that cannot answer these cleanly is one to press.

Data moving through systems you have not reviewed. Portfolio data sent to agents by email or external file transfer sits in systems you have not assessed, typically with no record of who opened it. For teams subject to cross-border transfer requirements, that exposure is a compliance question as well as a security one.

Good agents, badly coordinated, still produce bad outcomes

A provider can hold strong relationships in every jurisdiction and still deliver poorly if the coordination between them is loose. The network is only as effective as the model through which it is managed, and that model is the provider’s responsibility, not the client’s.

Centralized coordination means the IP team is not managing individual firm relationships across dozens of jurisdictions, chasing confirmations, or reconciling invoices in six currencies. It also means the provider sees a problem in a specific jurisdiction before the client does. The practical test is simple: when an agent goes quiet ten days out from a deadline, does anyone notice, and who escalates?

How agents access client data is a design decision with consequences. A provider that transmits portfolio files to agents externally has introduced a new system into the chain with every instruction. A provider that gives agents controlled access to data inside its own platform keeps the data in one environment and retains a record of who accessed what and when. The second model is auditable. The first is a collection of email threads.

The last piece is what happens when an agent falls below standard. Providers should be able to describe their process without hesitating: how performance is tracked, what triggers a review, and whether a firm has actually been replaced. If no firm has ever been replaced, that is worth understanding before you assume the network is actively managed.

Questions worth putting to your provider

Ask these directly, in an RFP or a renewal conversation. The answers are more revealing than any coverage map.

• How are agents selected, and against what criteria?
• Do you use sub-agents in any jurisdiction, and are they disclosed to us by name?
• Are official fees passed through at cost? What FX rate do you apply, and as of what date?
• Are agent charges included in the upfront estimate or billed separately afterward?
• Do agents receive our portfolio data, or access it within your platform?
• Is every submission verified against the register before it is confirmed to us?
• How is agent performance monitored, and when did you last remove a firm from the network?
• If a deadline is missed through agent error, who bears the surcharge and restoration cost?
• Can we keep our own agent relationships in jurisdictions where we have them?
• A provider running a managed network answers all of these without needing to check. Hesitation on the fee and sub-agent questions in particular tells you something.

How Sun IP is structured

We coordinate agents centrally through the Sun IP platform across 145+ jurisdictions with no coverage limitations. Agents work with client data inside the platform rather than receiving it externally, which keeps the data in one controlled environment and leaves a complete record of access. Every submission is verified before it is confirmed back to the client, agent relationships are monitored on an ongoing basis, and clients who have their own established local firms can continue working with them through the platform rather than being moved onto our network by default.

None of that is unusual to describe. What matters is whether a provider can show it when asked. If you are evaluating a provider this cycle, or reviewing the one you already use, the list above is a reasonable place to start, whoever you put it to.

If you would like to see how our network is structured and what it would mean for your portfolio, get in touch.