BandLab Proof Folder Checklist for AI Music Releases
Gary WhittakerBandLab Proof Folder Checklist: What to Save Before You Release an AI Song
A release-ready AI song needs more than a final audio file. It needs a record of what happened.
If your song started in Suno or another AI music tool, then moved into BandLab for editing, vocals, mastering, export, or cleanup, you should save the steps that got you there.
This does not guarantee copyright protection, distributor approval, monetization, or legal safety. It gives you a cleaner record of your work before you choose BandLab Distribution, DistroKid, or any other release path.
Your proof folder should show the song’s journey from AI draft to release candidate
At minimum, save the original AI export, lyrics, prompt notes, BandLab project version, human recording notes, mastering notes, final export, artwork notes, credits, and AI disclosure notes.
The goal is simple: if you look at the folder later, you should understand what came from AI, what you changed, what you added, and which version you released.
Source Records
Save the original AI export, prompts, lyrics, tool used, creation date, and any stems or MIDI files.
BandLab Records
Save project versions, human recordings, mix notes, mastering tests, track exports, and final mixdowns.
Release Records
Save credits, artwork notes, AI disclosure notes, distributor decision, and final upload information.
Why AI music creators need a proof folder
AI music creators often move fast. They generate a song, improve it, export it, and then forget what changed.
That becomes a problem when you need to answer basic release questions:
- Which version was the original AI export?
- Which version did you edit in BandLab?
- Were the lyrics written by you, AI, or both?
- Did you record human vocals or instruments?
- Did you use loops, samples, sounds, or beats?
- Did you use stems or separated tracks?
- Which master did you choose?
- What should you disclose during distribution?
A proof folder helps you answer those questions without guessing.
Simple AI music proof folder structure
You do not need an advanced system. Start with a clean folder structure you can repeat for every release.
- 01 Original AI Export
- 02 Prompts and Lyrics
- 03 Suno or AI Tool Notes
- 04 BandLab Project Versions
- 05 Human Recordings
- 06 Stems and Track Exports
- 07 Mastering Tests
- 08 Final Export
- 09 Artwork and Visual Notes
- 10 Credits and Release Notes
The folder does not need to be perfect. It needs to be understandable six months from now.
Save the original AI export
Before you edit in BandLab, save the original export from Suno or your AI music tool.
Save:
- Original MP3 export
- Original WAV export, if available
- Original video export, if relevant
- Original full song export from Studio, if used
- Selected time-range exports, if used
- Multitrack stems, if available
- MIDI files extracted from stems, if used
Name files clearly. Do not call the original export “final.”
Save prompts, lyrics, and style notes
Your proof folder should show how the song started.
- Original prompt
- Style prompt or genre prompt
- Lyrics used in the generation
- Human lyric edits
- AI lyric edits
- Song title changes
- Tempo, key, or style notes if known
- Notes about what you were trying to create
This helps separate the creative idea, the AI-generated output, and the edits you made later.
Save AI tool notes
Your proof folder should identify the tools used to create or change the song.
- AI music tool used
- Model or version, if known
- Date generated
- Whether you used extend, cover, remaster, stems, Studio, or other edit tools
- Whether the AI generated lyrics
- Whether the AI generated vocals
- Whether the AI generated melody or arrangement
- Whether the AI generated instrumental performance
These notes matter because distributor AI disclosure questions may ask what parts of the song were generated by AI.
Save BandLab project versions
Once the song enters BandLab, save version notes so you know what changed.
- BandLab project name
- Date imported
- Imported source file
- BandLab edit version 1
- BandLab edit version 2
- Final BandLab project version
- Notes on sections changed
- Notes on arrangement cleanup
- Notes on any effects used
If you cannot explain the difference between versions, your naming system is not clear enough.
Save human recording notes
If you add human performance in BandLab, document it.
- Lead vocal performer
- Background vocal performer
- Ad-lib performer
- Spoken-word or narration performer
- Instrument performer
- Date recorded
- Sections recorded
- Recording device or setup, if useful
- Raw vocal or instrument file
- Cleaned or processed vocal version
Human contribution can strengthen your creator record, but only if you save what happened.
Save stems and track exports carefully
Stems can be useful, but they can also create confusion if you do not track where they came from.
- Suno stems
- BandLab track exports
- BandLab mixdown
- Splitter output, if used
- MIDI exports, if used
- Any edited stem versions
- Notes about whether stems were source exports or separated after the fact
A separated stem is not always the same thing as an original studio multitrack file. Label it honestly.
Save mastering test notes
If you use BandLab Mastering, do not just export one version and forget the decision.
- Master test 1
- Master test 2
- Master test 3, if used
- Which version you chose
- Why you chose it
- What devices you checked
- Any clipping or loudness concerns
- Whether the master changed the vocal, bass, or harshness
Mastering should be final polish. If the mix has obvious problems, fix those before mastering.
Save the final export separately
The final export should be easy to find.
- Final WAV export, if available
- Final MP3 or M4A backup, if relevant
- Final video export, if relevant
- Final lyric file
- Final artwork file
- Final credits file
- Final distributor notes
Keep the final export in its own folder. Do not mix it with draft versions.
Save source notes for sounds, loops, beats, and samples
If you add anything beyond the original AI export and your own performance, write it down.
- BandLab Sounds used
- Loops used
- Beats used
- Imported samples
- Third-party sound packs
- Collaborator files
- License notes
- Source URLs or library names
Do not wait until release day to figure out where a loop or sample came from.
Save collaboration and forking notes
BandLab can be collaborative. That is useful, but it also means you need records.
- Who collaborated on the project
- What each person contributed
- Whether the project was private or public
- Whether the project was forkable
- Whether anyone else has permission to reuse or change the project
- Whether collaborators agreed on credits
- Whether collaborators agreed on release plans
For most release candidates, keep the project private until you understand the collaboration and forking settings.
Prepare credits before distribution
Before choosing BandLab Distribution, DistroKid, or another distributor, prepare your credits.
- Artist name
- Song title
- Songwriter credits
- Producer credits
- Vocal performer credits
- Instrument performer credits
- Collaborator credits
- AI involvement notes
- Cover, remix, or original status
- Explicit lyrics status
Do not build credits from memory at the upload screen. Prepare them before upload.
Prepare AI disclosure notes
If you use DistroKid, AI Credits may ask whether parts of the track were generated by AI.
Save notes for:
- AI-generated lyrics
- AI-generated vocals or audio
- AI-generated instrumental performance
- AI-generated melody
- AI-generated arrangement
- Whether all audio was AI-generated
- Whether part of the audio was human and part was AI
- Whether AI was only used for mixing, mastering, or workflow support
This is one of the main reasons the proof folder matters. You should not be guessing when the distributor asks.
The full BandLab proof folder checklist
Use this before release.
- Original AI export saved
- Prompts saved
- Lyrics saved
- AI tool and model notes saved
- Suno or AI generation date saved
- BandLab project name saved
- BandLab version notes saved
- Human recording notes saved
- Stems or track exports saved
- Mastering tests saved
- Final export saved separately
- Artwork notes saved
- Loop, sample, sound, or beat sources saved
- Collaboration and forking notes saved
- Songwriter and performer credits saved
- AI disclosure notes saved
- Distributor decision saved
- Final upload details saved
What not to do before release
- Do not delete the original AI export.
- Do not call every version “final.”
- Do not forget which tool created which part.
- Do not add loops or samples without saving source notes.
- Do not make release candidates forkable without understanding the setting.
- Do not upload before preparing credits.
- Do not answer AI disclosure questions from memory.
- Do not assume BandLab mastering fixes release-readiness.
- Do not treat a proof folder as legal advice.
What to read next
Use these guides based on your current stage.
Still preparing the song?
Start with the BandLab After Suno workflow.
Need the main prep system?
Use the general BandLab AI Music Prep Guide.
Choosing a release path?
Compare BandLab and DistroKid workflow roles.
Need one-song help?
Use VIP support when you need help applying this to a real release candidate.
Use BandLab because it fits the job
BandLab can help you prepare, polish, export, and document AI music before release. Use the free workflow first. Consider Membership only if the extra tools solve a real problem in your process.
Some links on JackRighteous.com may be referral or affiliate links. If you use them, Jack Righteous may receive a benefit at no extra cost to you. Use them only if the tool fits your workflow.
FAQ: BandLab proof folders for AI music
Is a proof folder the same as copyright registration?
No. A proof folder is an internal record of your workflow. It is not a substitute for legal advice, copyright registration, publishing administration, or distributor approval.
Do I need a proof folder for every AI song?
You should build one for any AI-assisted song you may release, pitch, monetize, or promote seriously.
What is the most important file to save first?
Save the original AI export before editing. That gives you the source record before BandLab changes, mastering, or human additions.
Should I save Suno stems and BandLab exports?
Yes, if you use them. Label them clearly so you know whether a file came from Suno, BandLab, Splitter, or another tool.
Do I need proof notes if I only used BandLab Mastering?
Yes, save the mastering notes and final export. If the song itself was AI-generated, mastering does not erase the need to document AI involvement.
Does a proof folder guarantee my song is safe to release?
No. It helps you organize your records. It does not guarantee rights clearance, store approval, playlist placement, monetization, or legal protection.
Official references used for this guide
Use these official sources to verify current details before making export, mastering, AI disclosure, or release decisions.