Artist Data Room Checklist: What to Send Your Team
An artist data room should send each recipient only the records needed for their job. Give a manager a current career and rights overview, a publicist the approved press layer, a lawyer the relevant agreements and ownership evidence, and a grant jury the application subset. Keep a source, version, owner, sensitivity, expiry, and revocation record for every share.
Lead visual
A music team is a responsibility map
Artist
owns the direction
Manager
turns plans into motion
Lawyer
protects deal terms
Partner
amplifies the release
Career · Team
Team decision map
Use this for
Understand what a partner actually does before you give up money, rights, or control.
Watch for
The wrong support can cost more control than it returns in leverage.
Check
Role, incentives, fee, term, deliverables, approval rights, and what stays in your hands.
Result
A clearer yes, no, or not-yet decision about the next person or company around your project.
Key takeaways
- Build one controlled index, then create a smaller view for each recipient and mandate.
- A manager needs decisions and career evidence. A publicist needs approved, usable press assets. A lawyer needs the records behind a specific legal question.
- A grant jury gets the application subset, including the relevant budget and project evidence, not your whole career archive.
- Record owner, source, version, sensitivity, approver, recipient, access date, expiry, and revocation for each share.
- Use individual accounts, platform roles, and multifactor authentication where supported. Do not make a shared password the handoff plan.
What belongs in the master index?
Keep the master index broad enough to support the work, but make every item easy to classify. The verified data-room model covers identity, catalog, rights, financial, campaign, live, brand, legal, and team-access records. Add a source, owner, version, sensitivity, and review date to each record. The index tells you what exists. A recipient view decides what leaves it.
Master index fields
Record the context beside the file
Identity and entities
Stage name, legal entity, approved contact route, and ownership context
Restrict identity material and share only what the mandate needs.
Catalog and rights
Releases, recordings, compositions, identifiers, splits, and registrations
Lets a manager or lawyer trace a claim to its underlying record.
Press and brand
Current bio, photos, artwork, credits, links, and usage limits
Creates a safe shareable layer for publicity and applications.
Finance and proof
Budget, statements, approved analytics export, source, and date range
Stops a screenshot or old budget from becoming an unqualified career claim.
Access and decisions
Recipient, role, approver, start, expiry, review trigger, and revocation
Makes the room auditable when a project or relationship changes.
What should each recipient receive?
Start with the recipient's decision. You are giving them enough evidence to do one job, not asking them to explore your entire archive. The table below is a working boundary. Adjust it when a contract, application, or campaign names a different requirement.
| Share | Keep out by default | |
|---|---|---|
| Manager | Career brief, catalog and rights map, release plan, live evidence, income categories, team map, and open decisions | Passwords, identity documents, tax records, and unrelated agreements |
| Publicist | Approved one-sheet or EPK, bio, photos, artwork, credits, focus track, release facts, and usage limits | Banking, private contracts, raw analytics, and unreleased files outside the campaign |
| Lawyer | The relevant agreement, ownership evidence, timeline, correspondence, and the question you need answered | A full archive that obscures the issue or unrelated confidential records |
| Grant jury | The requested application, project budget, eligibility evidence, and dated project materials | A standing folder, login access, or private records the application does not request |
How do you turn the index into a handoff?
Recipient-specific handoff
Five states from request to removal
- 01
01
Name the job
Write the decision, recipient, records, owner, and required end date before creating a share.
- 02
02
Prepare the view
Use current versions, remove unrelated material, and mark sensitivity and usage limits.
- 03
03
Approve access
Confirm the agreement or application requirement, then choose the minimum role or file access.
- 04
04
Log the share
Record the source, recipient, approver, access date, expiry, and any permitted download or reuse.
- 05
05
Review and revoke
At the expiry or relationship change, transfer work, remove access, and record what happened.
Purpose: evaluate a 12-month release and live plan Current records: career brief v3, catalog map v2, live evidence Jan to Jun 2026 Open decisions: manager scope, release sequence, booking territory Excluded: passwords, tax records, identity documents, unrelated contracts Owner: artist Access: named manager account, review 30 Sep 2026, revoke at end of mandate
- “Purpose”
- A defined job keeps the share from becoming a permanent archive handoff.
- “Excluded”
- Naming sensitive material that is out of scope makes the boundary visible before access is granted.
- “review 30 Sep 2026”
- An expiry or review date creates a point where stale access can be removed.
Which assets make the press layer usable?
A publicist or application reviewer should not have to assemble your basic identity from scattered links. Keep the approved bio, image set, artwork, credits, and working links together, with usage limits and a contact owner. Apple Music for Artists' EPK guidance is a useful primary reference for the public-facing layer. The existing artist one-sheet and EPK guide covers that asset in more detail.
Keep the press layer separate from the evidence layer. Streaming proof, splits, budgets, and agreements may support a manager, lawyer, or application, but they are not automatically press assets. Give each file a date and source so the recipient can tell a current record from an old export.
How should access be protected?
Use individual accounts and delegated platform roles where they exist. Spotify for Artists documents team access, and CISA recommends multifactor authentication and least privilege as security practices. In practical terms, give a recipient the smallest role that completes the job, make the access accountable to a named person, and remove it when the reason for access ends.
If a lawyer needs one agreement, send that agreement and its supporting evidence. If a publicist needs a photo, send the approved photo and its usage terms. If a manager needs a career view, send the current view and log the review date. Smaller handoffs are easier to keep current and easier to revoke.
Primary sources and related guides
For the wider team sequence, see the building your music team guide and its contract checklist before giving anyone continuing access.
Frequently asked questions
Should I send one artist data room link to everyone?+
No. Create recipient-specific views from one controlled index. A publicist may need approved photos and a bio, while a lawyer may need a contract and rights records. Banking, identity, tax, unreleased, and login material should stay out unless the mandate requires it.
What should I send a music manager first?+
Start with a current career brief, catalog and rights summary, release plan, live evidence, income categories, team map, and the decisions you need help making. Add source links and dates so the manager can see what is current without treating a screenshot as permanent evidence.
What should a publicist receive from an artist?+
Send the approved press layer: one-sheet or EPK, current bio, approved photos, artwork, credits, focus track links, release facts, contact owner, and usage limits. Keep contracts, banking, private analytics exports, and unreleased material out unless the campaign specifically needs them.
Do I send a grant jury my full data room?+
No. Send the exact application materials and evidence the program requests, with the relevant budget and project proof. A jury packet is a time-limited submission, not a standing invitation to browse your identity, contracts, passwords, or unrelated catalog records.
What happens to access when a team relationship ends?+
Review the agreement, preserve records you need, transfer current work, remove platform roles and shared links, rotate credentials where necessary, and record the revocation. CISA's least-privilege guidance supports removing access that no longer serves a defined job.
Get better release strategy in your inbox
Release planning checklists, royalty explainers, and artist strategy notes from Velveteen. No daily noise.
Was this useful? Send a signal or flag a correction.
Keep reading
Pillar guide
Build your music team
A role, evidence, and access-control system for managers, agents, lawyers, publicists, accountants, and every document they need.
Related guide
Contracts to review
The five clauses that matter in management, agency, and publicist agreements, including the sunset clause that protects income you generated yourself and why Canadian artists on cross-border deals need US counsel too.
Related guide
Artist one-sheet / EPK
What an artist one sheet is, how it differs from a full EPK, what goes on each, the real photo specs, and where to host it.
Build your one-sheet in minutes
Drop in your bio, links, and proof points and get a clean, copy-ready one-sheet for curators, blogs, bookers, and anyone else asking who you are.