> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://wiseband.crisp.help/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# # Best Practices: Contributors / Authors / Composers / Remixers

# Best Practices: Contributors / Authors / Composers / Remixers

When creating a release, it is essential to correctly enter all contributors involved in your project.

Information entered in the **Composer**, **Author**, **Lyricist**, **Arranger**, **Remixer**, or any other contributor role fields is transmitted to streaming and download platforms such as Spotify, Apple Music, Deezer, Amazon Music, YouTube Music, and many others.

Incorrect contributor information may lead to metadata errors, delivery delays, or, in some cases, release rejection.



# Why is contributor information important?

Platforms use this information to:

* Correctly identify rights holders
* Associate the right people with each work
* Display accurate credits to listeners
* Facilitate copyright and royalty management

Incorrect names or contributor roles may impact the identification of contributors and the exploitation of your music.



# Required contributor name format

For all contributor fields, names must be entered using the following format:

**First Name Last Name**

## Correct examples

* Jean Martin
* Marie Dupont
* John Smith
* Ana Garcia

## Incorrect examples

* MARTIN Jean
* Jean MARTIN
* J. Martin
* Jean Martin (Author)
* Jean Martin / Marie Dupont

⚠️ Do not add any additional information in contributor fields (roles, companies, pseudonyms, etc.).



# How to enter multiple contributors

When several people share the same role, each contributor must be entered separately.

## Example

For two composers:

* Jean Martin
* Marie Dupont

If only one field is available, separate contributors using a comma:

`Jean Martin, Marie Dupont`



# Using stage names

Contributor fields should contain the contributor’s **legal name** whenever required for rights-holder identification.

Artist names should only be used when explicitly requested in a dedicated field.

## Example

### Correct

* Jean Martin

### Incorrect

* DJ Shadowman



## Exception

If the artist name itself follows a first name + last name format and is the artist’s official professional identity, it may be accepted.

### Example

* Holy Bones



# Contributors with multiple roles

If the same person fulfills several roles within a work, they must be entered in each relevant role.

## Example

Jean Martin is:

* Author
* Composer

He must therefore appear in both fields.

### Author

* Jean Martin

### Composer

* Jean Martin



# Best practices before submitting your release

Before submitting your release, take a few minutes to review your contributor information.

## Checklist

✓ Check the spelling of every contributor.

✓ Always use the **First Name Last Name** format.

✓ Enter each contributor separately.

✓ Use official rights-holder information.

✓ Verify that all roles are assigned correctly.

✓ Avoid abbreviations, nicknames, or additional information in contributor fields.



# Which roles are affected?

This rule applies to all contributor roles available within Wiseband, including:

* Composer
* Author
* Lyricist
* Arranger
* Remixer
* Adapter
* Translator
* Producer
* Any other contributor role available during the distribution process



# Key takeaway

To ensure your release complies with platform requirements, all contributors must be entered in a clear and standardized way:

**First Name Last Name**

Following this rule helps ensure:

* Accurate rights-holder identification
* Higher-quality metadata
* Faster delivery to platforms
* Fewer risks of rejection or distribution delays

💡 If you are unsure how to enter a contributor or a specific role, please contact the Wiseband team before submitting your release.