IRSC Finder: A Practical Afternoon Checklist

If you searched for an IRSC finder, you may be looking for an ISRC, the identifier for a specific sound recording. The transposed letters are easy to miss, but the bigger challenge is matching the right code to the right version. Use this afternoon checklist to check your records, search reliable databases, and document what still needs follow-up. A lookup result is a lead, not proof that two recordings are the same.

1. Set up a clean lookup sheet

Before opening a search tool, make a working table. One row per recording, with columns for:

• Your asset ID or file name
• Track title and alternate titles
• Main artist and featured artists
• Release title and release date, if known
• Version, such as original, radio edit, remix, live take, or remaster
• ISRC found, source, and match confidence
• Follow-up status and notes

Use the recording, not just the song title, as your unit of work. An ISRC identifies a sound recording, not the composition, artist, album product, or UPC. Different recordings of the same song can have different identifiers. (isrc.ifpi.org)

Start with a manageable batch, such as one release or one folder of masters. Set a timer for 15 minutes to gather source information before searching. If titles are inconsistent, note the exact spelling from the distributor statement or release metadata instead of normalizing everything by memory.

2. Check the records you already control

Look in this order, from strongest first-party evidence to useful clues:

1. Distributor dashboard and delivery reports. Check the track-level metadata for the original delivery and any later redelivery. Record the code exactly as shown.

2. Label, artist, or rights-owner catalog. Search release spreadsheets, repertoire exports, delivery confirmations, and archived emails.

3. The audio file and its metadata. Inspect the file’s embedded tags, but treat an absent field as inconclusive. The official ISRC FAQ notes that formats may support the field, while embedding is not universal. (isrc.ifpi.org)

4. Release paperwork or mastering records. These can help distinguish a version, though they may not contain the identifier.

Do not create a code from a title, release date, or another track’s code. Do not assume a distributor’s code is missing just because the local file has no ISRC tag. Keep a source note for every code you copy so another person can retrace the lookup.

3. Search the official database, then widen carefully

Use the International ISRC Database for artist and title searches, including basic or partial queries when your metadata is incomplete. It supports search by artist and title, and the official FAQ says the database uses fuzzy matching. The database reflects repertoire data submitted to SoundExchange, so a missing result does not prove that a recording has no ISRC. Data may not have been submitted or may not have appeared in the database yet. (isrc.ifpi.org)

For U.S. repertoire, SoundExchange also provides an ISRC search service. Its database is populated with recording data submitted by rights owners, distributors, and ISRC managers. If your organization manages a large repertoire, SoundExchange describes a separate matching service for eligible licensees to submit catalog files for matching. (soundexchange.com)

Try more than one query for a difficult entry: exact title and artist, title without punctuation, alternate title, and release name. Search for the recording’s version explicitly when the tool allows it. A generic title can return a plausible result for a different artist, edit, or recording, so never accept a match on title alone.

4. Verify the candidate against the audio and release

For every candidate code, compare the result with your asset. Confirm as many of these as the source provides:

• Artist and track title
• Release context
• Duration and version label
• Whether it is the studio master, live recording, remix, edit, or remaster
• Whether the code already appears in your own delivery records

Use a simple status system: confirmed, probable, conflict, or not found. “Confirmed” should mean the recording identity matches, not merely that the title looks right. If two sources disagree, preserve both records and flag the conflict for the label, distributor, or rights owner. Do not silently overwrite the catalog value.

Version handling deserves extra care. The International ISRC FAQ says a code remains with a recording even if ownership changes. It also identifies remixes and edits as examples of changes that require a new ISRC, while a remaster generally may keep the existing code unless significant new creative input changes the recording. For borderline cases, consult the official guidance and the rights owner rather than guessing. (isrc.ifpi.org)

5. Close the gaps without assigning duplicates

For each “not found” entry, check the distributor or rights-owner records again, including older delivery exports. If the track was released, ask the party that delivered or assigned its code. Database absence alone is not enough to conclude that the recording has no ISRC.

If you are responsible for assigning one to a recording that has never had one, follow the official ISRC process and confirm that you have authority to assign it. The International ISRC Agency says only the rights owner may assign a code, or an appropriately appointed ISRC Manager acting on the rights owner’s instruction. Never reuse an existing code for a different recording. (isrc.ifpi.org)

At the end of the afternoon, filter the sheet to “conflict” and “not found.” Those rows are your follow-up queue. Keep the lookup source and date with the result, and preserve the original file metadata before making edits.

6. Make the result useful in your music library

An ISRC is an identity field. It does not describe whether a track is instrumental, its mood, tempo, key, genre, or suitability for a brief. Keep those descriptive tags alongside identifiers, but do not confuse the two jobs.

For a catalog cleanup, connect your local folder to TrackTag Studio, the batch AI audio analyzer to index files as tagged or untagged and organize descriptive track metadata. TrackTag’s local scan reads file names and sizes on your machine; a file is not uploaded unless you explicitly analyze it. TrackTag Studio can export results for a whole batch, selected tracks, or individual files, giving you a practical way to pair a cleaned identifier sheet with searchable audio descriptions. It is a tagging workflow, not an ISRC lookup or verification service.

If you are working through a larger backlog, see the guide to batch tagging music files and the checklist for preparing a catalog for music library submission. The best end state is simple: every recording has a traceable identifier source, version conflicts are flagged rather than guessed away, and descriptive tags help your team find the audio after the identifier work is done.