Utilisation de Suno AI pour la création musicale
AI Music Human Direction Record: Map Human, AI and Third-Party Contributions Before Release
APPLY Step 4 of 5: document one real AI-assisted song through its platform history, human decisions, generated elements, third-party material, permissions, rights summary and release-readiness status.
Reviewed and updated: August 1, 2026
Before releasing an AI-assisted song, document what the platform generated, what you wrote or performed, what you uploaded, what you changed and which rights remain uncertain. A Human Direction Record does not create copyright, but it can help you explain your contribution, prepare accurate registrations, answer distributor questions and avoid making rights claims you cannot support.
This APPLY guide is designed as a working session. Choose one real song and complete each step with that project open beside you. By the end, you should have a project folder, a contribution map, a one-page rights summary and a clear release status.
This article provides educational and organizational guidance, not legal advice. Copyright, contract and platform rules differ by country and can change.
Create a Rights Record for One Real Song
Do not complete this workflow from memory months after release. Select one song now and define the exact version you are reviewing.
- One working or final title
- One primary AI platform
- One intended release version
- One project owner
- One organized project folder
Your finished record should contain four practical deliverables:
1. Human Direction Record
A chronological account of the project: starting material, prompts, generations, uploads, performances, edits, collaborators and final exports.
2. Contribution Map
A component-by-component breakdown showing what was human-created, AI-generated, uploaded, licensed, supplied by someone else or still uncertain.
3. One-Page Rights Summary
A concise explanation of the platform conditions, human contributions, AI-generated elements, third-party material, collaborators and unresolved questions.
4. Release Decision
Assign the project one of three outcomes: ready for release preparation, needs clarification or professional review recommended.
Important: an organized record can support your explanation of the project. It does not determine ownership, create copyright or guarantee that a registration will be accepted.
Build the Project Folder First
Create a dedicated folder before answering rights questions. A clear folder structure makes the evolution of the work understandable without relying on memory.
Song Title – Rights Record │ ├── 01 Platform and Terms ├── 02 Prompts and Generations ├── 03 Lyrics and Composition ├── 04 Uploaded Audio ├── 05 Stems and Source Files ├── 06 DAW Sessions and Edits ├── 07 Performances ├── 08 Collaborators and Splits ├── 09 Release and Distribution ├── 10 Registration └── 11 Final Rights Summary
Use a consistent file-naming pattern:
YYYY-MM-DD_Project_Element_Version
2026-08-01_Song-Title_Lyrics-V03.docx2026-08-02_Song-Title_Suno-Generation-04.wav2026-08-04_Song-Title_Lead-Vocal-Raw.wav2026-08-06_Song-Title_Master-V02.wav
Save originals as well as edited versions. The goal is not to preserve every meaningless export. The goal is to preserve enough evidence to explain how the final work developed.
Step 1 — Document the AI Platform and Creation Conditions
Your current subscription does not prove which plan was active when an older song was created. Record the conditions that applied when the relevant output was generated.
Record the platform facts
- Platform name
- Model or version, when displayed
- Account identifier
- Subscription tier
- Subscription start and end dates
- Generation date
- Song URL or project ID
- Public or private status
- Feature used: create, extend, remix, cover, persona, upload or another tool
- Whether another user’s material was involved
- Whether the platform terms later changed
Suno-specific questions
- Was the song created under Basic, Pro or Premier?
- Was the paid subscription active when the relevant output was generated?
- Was the song later edited or extended under a different plan?
- Did the project include uploaded audio?
- Was another user’s song remixed?
- Was the track publicly shared?
- Is attribution required?
- Is the commercial-use position clear?
Suno’s current terms distinguish Basic-plan outputs from outputs made while subscribed to Pro or Premier. Paid access can provide contractual commercial-use rights for qualifying outputs made during the active subscription, but Suno does not guarantee that copyright will vest or that outputs will be unique. Upgrading later does not normally grant retroactive commercial rights to earlier Basic-plan songs.
Evidence to save
- Account-tier screenshot
- Receipt or billing record
- Creation date and project URL
- Relevant Terms of Service
- Relevant official help article
- Support correspondence, if any
Assign one status: confirmed, partly confirmed, unconfirmed or restricted.
For a broader platform explanation, read Jack Righteous on Suno AI.
Step 2 — Identify What Existed Before the AI Generation
Creators often begin documenting only after the platform produces a song. Start earlier. Identify the material that existed before the first generation.
- Original lyrics
- Melody or vocal demo
- Chord progression
- Instrumental recording
- Beat or rhythm
- Story, concept or emotional direction
- Song structure
- Reference track
- Collaborator contribution
Separate general ideas from specific expression. “A reggae song about perseverance” is a concept. A written lyric, a recorded melody or a completed arrangement is specific creative material.
| Element | Existed before AI? | Created by | Evidence saved | Notes |
|---|---|---|---|---|
| Title | ||||
| Concept | ||||
| Lyrics | ||||
| Melody | ||||
| Chords | ||||
| Vocal or instrumental performance | ||||
| Arrangement | ||||
| Reference material |
Step 3 — Save the Prompt and Generation History
Prompt history can show direction, intention and development. It does not automatically prove copyright ownership. The stronger question is whether you created or controlled specific expressive material in the final work.
Save:
- Original prompt
- Style instructions and exclusions
- Lyrics entered into the platform
- Structure tags
- Persona or voice settings
- Uploaded source files
- Generation dates and order
- Selected and rejected outputs
- Reason for selecting or rejecting each important version
| Version | Date | Prompt change | Output created | Decision |
|---|---|---|---|---|
| 01 | ||||
| 02 | ||||
| 03 |
Do not assume that more prompts, more generations, more credits or more time automatically create stronger authorship. Record the process honestly and focus on the material you actually contributed or changed.
Step 4 — Build the AI Music Contribution Map
This is the centre of the workflow. Review the final song component by component. More than one category may apply to the same element.
| Song component | Human-created | AI-generated | Uploaded | Third-party | Uncertain | Evidence | |
|---|---|---|---|---|---|---|---|
| Lyrics | |||||||
| Lead melody | |||||||
| Harmony and chords | |||||||
| Drums and rhythm | |||||||
| Bass line | |||||||
| Arrangement and structure | |||||||
| Lead vocal | |||||||
| Background vocals | |||||||
| Instrument performances | |||||||
| Samples and loops | |||||||
| Sound design | |||||||
| Mixing and mastering | |||||||
| Cover artwork |
Example: you record a melody, upload it, allow AI to transform it and then rearrange the result. That element may be human-created, uploaded, AI-processed and later human-edited. Do not force it into one box.
Step 5 — Record Who Wrote and Revised the Lyrics
Classify the final lyric set:
- Fully human-written
- AI-generated
- Human-edited AI lyrics
- Translated lyrics
- Co-written lyrics
- Public-domain source material
- Quoted, sampled or adapted text
Evidence to preserve
- First draft
- Revision history
- Voice notes
- Document metadata
- Chat history
- Translation drafts
- Co-writer messages and agreements
When lyrics move into another language
Record who created the original lyrics, who translated them, whether the translation was literal or adaptive, and whether rhyme, meaning, syllable count or cultural references were rewritten. A creative translation may raise separate authorship and compensation questions.
When a reference track influenced the lyrics
Check whether wording, phrase structure, rhyme patterns, hook language or narrative progression were copied too closely. A reference can guide direction without granting permission to reproduce protected expression.
Step 6 — Separate Composition From Arrangement
Review the underlying music separately from the production around it.
Composition elements
- Melody
- Harmony and chords
- Rhythm
- Hook
- Countermelody
- Bass line
- Song form
Arrangement elements
- Intro and ending
- Verse and chorus order
- Bridge and breakdown
- Instrument entrances
- Transitions
- Dynamic development
Save the original generation, the first edited version and the final arrangement. Explain each substantial change.
| Section | Initial output | Human change | Final result |
|---|---|---|---|
| Intro | |||
| Chorus | |||
| Bridge | |||
| Ending |
Step 7 — Record Human Vocals and Instruments
For every human performance, capture:
- Performer’s legal and creative name
- Vocal or instrument role
- Recording date
- Raw recording file
- Recording location
- Take or session number
- Whether AI transformed the performance
- Whether the original remains identifiable
- Payment, credit and agreement status
Distinguish human lead vocals from generated vocals, human backing vocals from generated backing vocals, recorded instruments from generated instruments and uploaded performances from the AI treatment applied to them.
Do not treat another person’s vocal, lyric or instrumental contribution as yours simply because it was uploaded through your account.
Step 8 — Separate Technical Cleanup From Creative Production
Editing, mixing and mastering may contain both routine technical work and expressive creative decisions.
Mainly technical examples
- Noise removal
- Gain adjustment
- Basic EQ and compression
- Loudness normalization
- File conversion
- Clipping repair
Potentially expressive examples
- Rebuilding the song form
- Creating new transitions
- Combining stems from different generations
- Replacing or rewriting sections
- Recording new performances
- Creating a bridge or ending
- Editing vocals into a new rhythm
- Designing original effects or sound relationships
DAW evidence checklist
- Session file and autosaves
- Exported stems
- Markers and project notes
- Plugin and instrument list
- Edit-decision notes
- Versioned mixes
- Final master
| Date | File version | Change made | Technical or expressive? | Evidence |
|---|---|---|---|---|
Do not claim that every mix decision creates a strong copyright interest. Describe what changed and allow the legal significance to be assessed separately.
Step 9 — Check Everything You Did Not Create
Review all third-party and externally sourced material:
- Samples and loops
- Beat leases and instrumentals
- Reference tracks
- Cover songs and interpolations
- Existing lyrics or melodies
- Public-domain works
- Creative Commons works
- Stock audio
- Collaborator uploads
- Client-provided material
- Vocal clones or imitations
- Brand names and trademarks
| Material | Source | Licence or permission | Commercial use allowed? | Attribution required? | Evidence |
|---|---|---|---|---|---|
Reference-track risk questions
- Did you copy lyrics?
- Did you retain a recognizable melody or riff?
- Did you reproduce the hook structure too closely?
- Did you imitate an identifiable singer’s identity?
- Did you use protected audio?
- Could listeners reasonably mistake the result for the reference work?
Step 10 — Identify Every Human Contributor
List everyone who contributed as a lyricist, composer, vocalist, instrumentalist, producer, arranger, engineer, translator, artwork creator, editor, client or project owner.
Record:
- Full legal and creative name
- Contact details
- Contribution
- Date
- Payment
- Credit
- Proposed ownership share
- Revenue share
- Permission and agreement status
Credit, payment, ownership, royalties and permission are not interchangeable.
| Contributor | Role | Contribution | Credit | Payment | Ownership discussed? | Agreement saved? |
|---|---|---|---|---|---|---|
Step 11 — Complete Two Different Rights Maps
A song can involve a musical composition and a sound recording. Complete a separate map for each.
Composition map
- Lyrics
- Melody
- Harmony and rhythm
- Song structure
- Human and AI contributions
- Composition collaborators
- Proposed claimant or owner
Sound-recording map
- Lead and background vocals
- Instrument performances
- Generated performances
- Production and sound design
- Editing, mixing and mastering
- Recording collaborators
- Master owner
| Question | Composition | Sound recording |
|---|---|---|
| What is the work? | Underlying words and music | The particular recorded performance |
| Human contributors | ||
| AI-generated elements | ||
| Owner or claimant | ||
| Registration plan | ||
| Unresolved questions |
For the underlying legal distinctions, return to AI Music Copyright in 2026: Human Authorship, Suno Rights and Registration.
Step 12 — Produce a One-Page AI Music Rights Summary
Condense the completed record into a document that a collaborator, distributor, client, publisher or lawyer can understand quickly.
Project identification
- Song title and artist
- Project owner
- Creation dates and final-master date
- Platform, model and subscription tier
Human-created material
- Lyrics
- Composition
- Performances
- Arrangement
- Production
- Artwork
AI-generated material
- Music
- Vocals
- Lyrics
- Instrument parts
- Sound design
Third-party material
- Source
- Licence
- Restrictions
- Attribution
Collaborators
- Names and roles
- Agreements
- Credits and splits
Platform rights
- Commercial permission
- Attribution requirements
- Public-sharing status
- Upload or remix limitations
Registration plan
- Country
- Composition, sound recording or both
- Human-authored material to claim
- Generated material to identify, exclude or disclose
Unresolved questions
- Missing agreement
- Unclear plan history
- Unlicensed source
- Potential similarity
- Professional advice required
In the United States, the Copyright Office says AI-assisted works may be protected when a human author determines sufficient expressive elements, including human-created material, creative arrangement or meaningful modification. Mere prompting is not enough by itself. Applications should identify the human-authored material being claimed and appropriately exclude generated material that is not being claimed.
In Canada, registration is voluntary and can provide a certificate usable as evidence, but CIPO does not examine the work or verify originality, authorship or ownership, and it does not accept a copy of the work with the application.
For registration and royalty accounts, continue to Music Registration & Royalty Collection in 2026.
Step 13 — Decide Whether the Song Is Ready
Ready for release preparation
Use this status when the platform conditions are documented, human and generated contributions are mapped, third-party material is cleared, collaborator terms are recorded and you can answer distribution questions accurately.
This does not guarantee copyright or prevent future claims.
Needs clarification
Use this status when the project has a missing generation date, unclear subscription history, incomplete collaborator agreement, uncertain sample licence, mixed human and AI lyrics without a record, questionable reference-track similarity or verbal ownership discussions that were never documented.
Professional review recommended
Use this status when the project includes unlicensed copyrighted material, disputed authorship, an identifiable cloned or imitated voice, a client demanding complete exclusivity, another creator’s remixed song, a major synchronization or advertising deal, difficult registration claims, or an existing takedown or infringement allegation.
Worked Example — Human Lyrics, Suno Instrumental and New Vocal
Consider this project:
- The creator writes all lyrics.
- The creator writes a rough vocal melody and records a phone demo.
- The demo is uploaded to Suno.
- Suno generates a full arrangement and guide vocal.
- The creator exports stems.
- The generated vocal is removed.
- The creator records a new lead vocal.
- The creator writes a new bridge and ending.
- The stems are rearranged in a DAW.
- The creator mixes and masters the final recording.
Contribution map
- Human-created: lyrics, original vocal melody, lead performance, bridge, ending and expressive arrangement changes
- AI-generated: initial instrumental parts, guide vocal and parts of the source arrangement
- Uploaded: phone demo and original melody performance
- Human production: stem selection, vocal replacement, arrangement reconstruction, mix and final master
- Uncertain: copyright status of generated instrumental expression
Responsible summary
The creator may have stronger claims in the original lyrics, melody, new performance, added sections and expressive production. The creator should not automatically describe every generated instrument or musical phrase as wholly human-authored. The platform plan, creation date and commercial-use conditions still need to be documented.
Ten Documentation Mistakes to Avoid
- Saving only the final MP3. Keep source files and meaningful versions.
- Deleting all rejected generations. Preserve important branches that explain the development.
- Failing to record the active plan. Current account status may not prove historical rights.
- Treating a prompt as complete proof of ownership. Record the expressive material you created.
- Combining composition and recording rights. Map them separately.
- Claiming all generated elements as human-authored. Describe AI involvement accurately.
- Ignoring collaborators. Credit, payment and ownership must be discussed explicitly.
- Using samples without saving licences. Preserve the actual terms and receipt.
- Relying only on screenshots. Save original files, project sessions and exports.
- Rebuilding the history from memory. Update the record while the project is active.
What a Human Direction Record Can and Cannot Do
It may help you:
- Establish a timeline
- Identify contributors
- Explain your creative process
- Separate generated and human material
- Prepare registration information
- Answer distributor or client questions
- Support collaborator discussions
- Help a lawyer assess the project
- Reduce avoidable disputes
It cannot:
- Automatically create copyright
- Guarantee registration
- Replace licences or agreements
- Override platform terms
- Eliminate similarity claims
- Resolve disputed ownership
- Replace legal advice
Continue Through the AI Music Rights Path
LEARN
Learn how platform rights, commercial permission, copyright and enforcement differ.
APPLY
Complete the Human Direction Record for one song using this page.
BUILD
Open Rights + Contribution Master Tracker 2.0. Turn the completed checklist into an editable online project record with an evidence index, Human Direction Record, separate composition and sound-recording maps, collaborator and permission files, risk tracking, registration-preparation notes and a printable Draft, Reviewed or Final PDF.
Build Your Human Direction Record
Choose one song and complete the record before your next release. Eligible Jack Righteous members can use Member Guidance & Support to organize project files, the contribution map and the final release summary.
Member guidance is educational and organizational. It is not legal advice or a determination of copyright ownership.
For release planning, use the AI Music Distribution Guide 2026. For income pathways, review the AI Music Monetization Guide.
For the wider creator journey, begin with Start Here: AI Music, Suno AI & Creator Path for 2026.
Primary Sources
Continue the Suno workflow
Do not stop at one Suno feature or prompt.
Connect setup, song development, editing, rights and release through the complete Suno guide and workflow hub.
Discussion