Monitoring a catalog involves choosing the titles to track, and then reviewing the reported matches. The useful work begins with an identifiable audio reference and continues with checking the context of each usage.
A potential result must be compared to your files and known permissions. This page explains how to organize this tracking without automatically turning each match into a violation.
From priority title to tracking decision
Start with the titles whose uses need the most tracking: recent release, regularly licensed track, or recording already featured in multiple projects. Identify the correct version and gather known authorisations. TuneLockr tracks usage in real-time on supported platforms; this does not mean coverage of all online content.
For each signal, compare the source to the beneficiary, dates, usage, and territory of available licenses. A match with a client might align with their agreement; an unknown match should be examined before any conclusion. Keep the reasoning for your decision in your tracking and documents.
Regularly review catalogue priorities and new authorisations. Creator includes monitoring one work and Pro three works; check the options and consequences of a change before proceeding. Prices and capabilities of your offer should be reviewed in the account and on the pricing page, without assuming unlimited tracking.
Prioritise assets
Start with strategic releases, synchronised tracks, sensitive works and highly active catalogues.
Qualify signals
A match must be considered in context: existing licence, citation, repost, editorial use or unknown exploitation.
Document
Keep the URL, date, screenshots, platform, account, territory and detected version before taking any action.
Manage next steps
Categorise cases by impact and direct them to the appropriate response: internal review, contact, platform or legal advice.
Choosing references to monitor
Start with the titles for which you know the recordings, released versions, and main authorized usages. Link each reference to your catalog file so that you can recognize an instrumental version, an excerpt, or a pre-planned usage.
Read the signal in its context
Open the indicated source, note the address and date of consultation, then compare the relevant passage to your reference. Note what matches and what remains uncertain. A similarity, an identical title, or an apparent reprise alone do not qualify the situation.
Check already known permissions
Look for a license, a promotion agreement, or a partner that might explain the presence of the piece. Keep the reference of the consulted document. If the identification or scope of the agreement remains uncertain, keep the file under verification.
Document the follow-up
Classify the result in your tracking: explained usage, verification to continue, or request to prepare. Note the person responsible for the next action and the response obtained. For a dispute, have the elements and appropriate steps reviewed before a takedown or accusation is requested.
One sheet per examined result
Title and reference version.
Source URL and date of consultation.
Compared passage and observed elements.
Sought or found authorization.
Decision, responsible party, and next step.
Consider the service scope
Tracking depends on the covered sources, submitted references, and the capabilities of the offer. Absence of results does not demonstrate the absence of any online usage. Consult the operation of monitoring and the offers to prepare your scope.
Sources and guidance
To explore further, consult the official resources of Légifrance. Texts and practices evolve: check the applicable version at the time of your project.
Frequently asked Questions
Does detection prove counterfeiting?
No. It indicates a match or usage to be assessed in its legal and contractual context.
Can you monitor several versions?
Yes, and it is helpful to clearly identify the master, radio edit, remix, instrumental and stems.
What should you do with a false positive?
Document the decision and adjust references or qualification rules to improve follow-up.
Organize your music monitoring: priority titles, versions, permissions, alert review, and tracking indicators.
Choose the titles to monitor with a priority matrix
A catalog cannot be managed by treating all titles as identical urgencies. Start with a limited list of references that you know the version, release date, and main permissions. The matrix below is used to organize your work; its levels are management choices and do not predict either an infraction or the probability of a detection.
Fictitious reference
Observable situation
Proposed review priority
Preparatory action
Clear night — master v4
Released this week and campaign ongoing
Frequent review during the launch
Gather the partners and authorized promotional uses
Open window — instrumental
Several active customer licenses
Review associated with contract deadlines
List the beneficiaries and expected media
Archives 2019 — album version
No new known campaign
Periodic review according to available resources
Ensure the reference file remains findable
Then choose a responsible person for each title. An alert without an owner easily becomes a forgotten file, even when it has been quickly detected. The person in charge of tracking must know where to find the licenses and to whom to send a rights question. They do not need to decide on all the follow-ups alone.
Revise the priority when the context changes
A campaign, a synchronization, or a new collaboration may push a title up the list. Conversely, a quiet period may justify a more spaced review rhythm. Note the reason for the change: "new video license until December" explains the decision; "important title" does not allow a colleague to take over tracking.
Before activating an additional reference in a service, check the capabilities and displayed cost in your account. The work table does not assume unlimited monitoring nor coverage of all platforms. The TuneLockr monitoring presentation describes the available path; your register specifies the titles and responsibilities you have actually retained.
At the end of the month, compare the list to the actual releases. Remove version duplicates from your register without erasing their history. Keep a reason for each addition or removal: this way you can explain the scope followed at a given date.
Link each audio reference to the correct catalog version
A detection becomes difficult to examine when the reference file is named something like "final-final2.wav". Give each recording a stable working identifier and attach the useful variants to it. The commercial title may remain the same; the album master, the radio edit, and the instrumental must be distinguishable in your file.
Field
Fictitious example
Usefulness
Internal identifier
NC-2026-MASTER-04
Link tracking to the exact file
Released version
Stereo master validated on October 8
Avoid comparing an old draft
Linked variants
Radio edit RE-02; instrumental IN-03
Understand an excerpt that differs from the master
A cryptographic fingerprint can serve to verify that two copies of a file are identical. It does not fulfill the same role as audio recognition which seeks matches despite certain file differences. Therefore, do not expect a simple name or document fingerprint to describe all audible transformations.
Prepare a version change
If a new master replaces the previous one, create an entry linked to the old one. Note the circulation date and the recipients to whom the new version has been delivered. An alert concerning the old master may remain explainable after this date: an authorized video may have kept the previously received file.
Do not delete old pieces to make the file cleaner. Move them to a readable history and indicate their status. A person taking over the catalog must understand why two almost similar files were used at different times.
The music version management provides the general framework. For monitoring, especially add the correspondence between the tracked reference, the actually delivered version and the permissions related to it. This link prevents a montage difference from becoming an unexplained anomaly.
Maintain an actionable permission register during an alert
A license file organized only by client name does not always answer the question posed by a detection. The account publishing might belong to an agency, a distributor, or a partner of the beneficiary. Prepare a register that links known uses to audio references while keeping the document that verifies each piece of information.
Information
Example of fictional work
Control to be performed
Audio reference
NC-2026-MASTER-04
Does the contract target this master or another version?
Beneficiary and intermediary
Example Brand, via its agency
Is the observed account linked to the project?
Intended use
Product presentation video
Does the observed use correspond to this purpose?
Media and period
Media and dates specified in the agreement
Is there a written extension?
Reference document
Signed agreement, version 2
Can the reviewer access it?
The absence of an entry in your register first means that the authorization was not found in this tool. It does not, by itself, prove that no agreement exists. Keep a status of “verification to continue” when the label, publisher, or another representative may have additional information.
Avoid summaries that distort an agreement
A “worldwide” or “all media” cell should not be inferred from a vague conversation. Use the relevant terms from the document and keep the link to it. If a clause is ambiguous, note the ambiguity instead of silently resolving it in the table. The register helps to locate and compare documents; it does not replace reading them.
Update the tracking after a new validation, keeping the date and the person who confirmed it. For evolving use, distinguish the initial agreement from its extension. This chronology helps understand why a publication seemed unknown during an initial review, then was explained.
To prepare a new agreement, use the process licensing your music. Correspondence can open a commercial discussion, but its existence does not prove a debt or license acceptance.
Organize a monitoring review with clear roles and outputs
Monitoring produces value when a signal leads to a documented decision. Define a routine compatible with your team: one person opens the new results, another can verify the agreements, and a manager decides on the next steps when the issue justifies it. A small team can combine these roles in one person, provided the stages are kept distinct.
Step
Question to resolve
Expected Outcome
Sorting
Do the link and reference allow for an initial verification?
Assigned file or missing information identified
Comparison
Which passage seems to correspond to which file?
Dated observation, without automatic legal conclusion
Permissions
Does known usage explain the publication?
Document found or question passed to the right contact
Decision
What next action is proportional to the elements?
Responsible person, action, and review date
Set a realistic review duration. It is better to finish a few understandable files than to go through dozens of results without recording decisions. Incomplete alerts should have a next step: “URL inaccessible, new review planned” is more useful than a default final status.
Prepare the handover between two people
Before an absence, provide a short list: followed references, ongoing files, contacts, and dates to monitor. A colleague should not have to browse an entire inbox to know why a use was classified as known. Add a two-sentence note summarizing the consulted documents and the still open question.
This organization is a proposed working method, not an assumed automatic function of the application. Use the statuses actually available in your account and keep the necessary additions in your own register. Do not schedule a withdrawal or accusation based on a mere match score.
At the end of each review, note a recurring obstacle: poorly named files, missing contracts, or duplicated references. Correcting this cause improves subsequent reviews more sustainably than increasing the number of notifications received.
Measure the quality of monitoring without confusing alerts with results
The number of alerts alone does not measure the effectiveness of monitoring. A high volume may reflect an authorized campaign, several copies of the same content, or results that still require verification. Choose indicators that describe your process and keep their definition alongside the figures.
Proposed management indicator
Calculation or rule
What it does not demonstrate
Proportion of files examined
Files examined ÷ files received over the period
The coverage of the entire internet
First review delay
Date of first review minus date of receipt
The delay between publication and detection
Proportion of explained uses
Files linked to a found authorization ÷ files examined
The proportion of all uses that would be lawful
Files with no next action
Number of open files without a responsible person or date
The legal seriousness of situations
Fictitious example: twelve results arrive, ten are examined, six are explained by a campaign, two require an agreement, and two remain uncertain. The examination rate is ten out of twelve, or about 83%. It would be incorrect to deduce a counterfeit rate of 40%: unexplained files are not automatically infringements.
Compare comparable periods
A launch week and a week without releases do not have the same context. Note the campaigns, the number of tracked references, and the scope changes. If you add several works, an increase in results does not prove that the risk has increased at constant scope.
Keep missing data as such. An uncovered platform, an unknown publication date, or an unavailable result do not equate to zero. This discipline is essential when a table is used to decide on a budget or to explain monitoring to an artist.
The assessment can end with three concrete decisions: improving a reference file, requesting a missing document, and revising a title's priority. This way, you measure the quality of your organization without turning a technical metric into a promise of total protection.
🍪 This website uses cookies to improve your web experience.