A Template for Requesting Territory Clarification From Your Distributor

Mechanical licensing for cover songs is not always global by default, and the fastest way to find out whether your release is cleared in every country you distributed to is to ask your distributor directly using specific, answerable questions rather than a vague email. Below is a template built to get a usable response, along with an explanation of why each question matters and what a complete answer actually looks like.

This matters more for covers than for original music because the license underlying a cover release is often territory-specific, tied to a particular mechanical licensing mechanism or collecting society relationship, while your original tracks carry no such restriction. If you release covers across 200+ platforms without knowing the licensed territory scope, you risk a takedown in markets where the license doesn’t apply, months after the release already has streams and playlist placements.

Why territory scope is different for covers than originals

Original songs you wrote and own outright can generally be distributed anywhere your distributor has platform relationships, since there’s no third-party rightsholder to clear. A cover song is a derivative work built on someone else’s composition, and the right to reproduce and distribute that composition is licensed on a country-by-country or society-by-society basis in most of the world outside the US compulsory license system.

In the United States, Section 115 of the Copyright Act creates a compulsory mechanical license for covers that meet specific conditions, which is why US-focused distributors can automate cover licensing so cheaply and quickly. Outside the US, mechanical rights are usually administered through local collecting societies or reciprocal agreements between societies, and coverage can vary by country even when the underlying deal looks similar on paper. That’s the practical reason «is my cover licensed» and «is my cover licensed in Country X» are two different questions with two different answers.

What should a territory clarification request include?

A useful request names the release, asks for the specific list of covered territories, and asks what happens in territories not covered — it should not just ask «is this global?» because that invites a one-word answer that may not reflect the real licensing structure. Here is a template you can copy and adapt:

Subject: Territory clarification request — [Track Title] by [Artist Name], UPC [if available]

Hello,

I’m requesting clarification on the territory scope of the mechanical license associated with my cover release, «[Track Title]» by [Artist Name], submitted on [date].

Specifically:
1. Which territories is this license confirmed to cover?
2. Are there any territories where this release was distributed but is NOT covered by the license?
3. If certain territories are excluded, will the release be blocked automatically in those territories, or is that something I need to configure?
4. Is this scope permanent for the life of the release, or could it change if the underlying rights information updates?

Please let me know if you need the ISRC or additional metadata to look this up.

Thank you,
[Your Name]

Question 3 is the one most people skip, and it’s the one that prevents an actual compliance problem. Some systems geo-block automatically outside the cleared territories; others distribute everywhere and rely on the license being broad enough, which shifts risk onto you if it isn’t.

What counts as a complete answer from a distributor?

A complete answer names specific territories or territory groups, not just «yes it’s covered.» If the response you get back is a single sentence confirming global coverage with no territory list and no explanation of the licensing basis, that’s a signal to ask a follow-up rather than assume it’s accurate — vague reassurance is not the same as documentation.

Globex Music includes automatic mechanical licensing with every cover release, structured around the US compulsory mechanism and extended through platform-level agreements for international distribution, so the majority of standard cover releases across the 200+ supported platforms don’t require a manual territory check. That said, if you’re releasing a cover of a composition with an unusual rights history — a song under active dispute, a translated adaptation, or a work where the publisher has historically restricted certain markets — a direct territory question is worth sending before release, not after.

When should you send this request — before or after release?

Before release, if you have any reason to suspect the composition has non-standard rights history; after release, if you’re auditing an existing catalog for compliance. Sending it before release costs you nothing but a short delay, while sending it after a takedown notice costs you the streaming history, playlist momentum, and review time you already spent getting the track live.

If you’re auditing a larger back catalog of covers — the point at which this becomes worth doing systematically is usually once you’ve crossed 15 to 20 cover releases, since that’s roughly where manually remembering the rights history of each source composition stops being reliable. At that scale, a saved version of this template applied to your entire catalog once a year is a reasonable compliance habit, not overkill.

Does asking for territory clarification cost anything or slow down my release?

No — this is an informational request about a license that’s already in place, not a new licensing application, so it does not affect your release’s moderation timeline or incur any fee. Standard cover song review with Globex Music typically completes in one to a few business days regardless of whether you’ve also sent a territory question, since the two processes run independently.

The one thing worth budgeting for is response time on the clarification itself, which varies by distributor and can range from same-day to a week or more depending on how much manual lookup is required. Building that lead time into your release calendar — especially for a cover you already suspect has a complicated rights history — is cheaper than discovering the answer after the track is already generating streams in a territory it was never cleared for.