How to Close a Label Services Campaign Without Losing Access
Collect campaign files, reporting, outstanding tasks, and account access before a label-services handoff. Use a practical acceptance record and platform-specific checks.
The short answer
Close a label-services campaign by agreeing the handoff scope, collecting the promised files and reporting, testing access from the continuing team's accounts, and assigning every unfinished task. Then remove routine partner permissions through each platform's controls. Record what was accepted and what remains unresolved; ending campaign work does not settle rights or agreement disputes.
Three things to know
- 01
A folder link or final report is a handoff input. Acceptance requires checking that the continuing team can open, use, and administer the agreed material.
- 02
Keep delivery, account permissions, spending, and unresolved obligations in separate rows with an owner and a next action.
- 03
Use this sequence for a routine agreed handover. Suspected account compromise requires prompt security action rather than waiting for campaign signoff.
What should the handoff register contain?
Use this constructed six-part register to turn an end-of-campaign conversation into testable items. Adapt it to the agreed scope and permissions.
- 01
Delivery and exclusions
List each promised output, exact version and format, delivery location, restrictions, and anything explicitly outside scope.
- 02
Continuing owner
Name the authorized person who will maintain the file, platform team, campaign link, or scheduled activity.
- 03
Access test
Record the continuing account, role, task tested, date, and result without storing passwords or recovery codes.
- 04
Reporting and spending
Keep dated source exports and separate paid, outstanding, and committed amounts where the scope requires them.
- 05
Unfinished work
Give each unresolved item a status, next action, responsible person, and agreed follow-up date.
- 06
Permission closure
Document authorized routine removals and test continuing access again before marking those items complete.
What does closing a campaign actually mean?
This guide starts after the team has agreed that a defined period of campaign work is ending or moving to another operator. It covers the operational handoff: deliverables, account access, reports, live activity, and unfinished tasks. It does not decide whether an agreement can be terminated, who owns recordings or creative work, or what money remains owed. Keep those questions separate and use qualified music counsel for disputed rights or agreement terms. This is practical preparation, not legal advice.
What should the outgoing partner hand over?
Start with the agreed scope and build a list of the actual promised outputs, not a generic demand for every file the partner has. Depending on that scope, the list might include final creative, editable source files, approved copy, campaign links, scheduled activity, reporting exports, spending records, and open decisions. For each item, record its location, version, format, responsible person, and any usage restrictions already agreed. Mark an item as not included or unresolved when appropriate. Do not assume that receiving a finished asset includes the source project, third-party licence, or right to reuse it in every context.
How can the artist verify that access will continue?
Have the continuing artist or manager sign in with their own account and check each required destination before routine permissions are withdrawn. Test the task they need to perform: opening a report, downloading an agreed asset, viewing current activity, or administering the relevant team. A partner's screen share proves that their login works; it does not prove yours does. Record the account and permission level used for the test, without saving passwords or recovery codes. If the continuing operator lacks the necessary role, keep that access item unresolved and work through the platform's official process.
What should change in Spotify for Artists?
Spotify's current removal instructions are for Team Admins. On the web, an Admin goes to manage.spotify.com/teams, selects the team, opens the three-dot menu beside the member, and chooses Remove. First verify which artist or label team is involved and that an authorized continuing Admin can manage the required team. Do not confuse removing a collaborator's team membership with moving distribution or changing recording rights. If the team is already claimed and its Admin cannot be reached, Spotify's access guidance directs artists to contact support. Keep that recovery step distinct from marking the campaign handoff complete.
Why is a shared Google Drive folder not enough?
Check ownership and permissions on the actual agreed files. Google states that transferring ownership of a folder does not transfer ownership of the files inside it. Transfer eligibility also depends on the account setup: work or school accounts can transfer ownership only within their organization. For personal-account transfers, check whether the recipient has accepted before treating the change as complete. If a direct transfer is unavailable, agree a permitted export or delivery alternative and test the resulting files. Preserve the original records until any retention or deletion decision has been properly agreed; do not delete material merely because a replacement folder exists.
What should the final report and spending record explain?
Use the reporting categories in Velveteen Records' public campaign-report guide as a cross-check: goals, timing, spend, platform signals, audience learning, and open questions. Add the reporting window, currency where relevant, source, and capture date so a new operator can interpret each figure. Separate paid invoices, outstanding invoices, committed spend, and activity still running. Agree who is responsible for any scheduled posts, active ads, or renewals at the handoff time. Do not infer that removing a login cancels billing or stops activity across unrelated tools; confirm the relevant status in each service.
What would a useful handoff record look like?
Constructed example: a single-release campaign has a final video, a reporting workbook, a campaign landing page, and an artist-team role. Record each in a separate row with the agreed delivery, continuing owner, access test, status, and next action. The video might be accepted after the recipient downloads and opens the specified version. The workbook might remain pending because an ownership transfer has not been accepted. The landing page might need a named person to maintain its destination links. The team role can be removed after the authorized continuing operator verifies access. These are example statuses, not results from a Records campaign.
When is the handoff ready to sign off?
Sign off the items that were actually checked and list the rest as exceptions with an owner and follow-up date. Ask both teams to acknowledge the same record rather than treating silence or an expired link as acceptance. Once the routine access changes are authorized and completed, test the continuing accounts again and save the final permissions record without exposing credentials. If there is suspected unauthorized access, use the platform's security and recovery controls promptly instead of waiting for this routine sequence. A completed handoff can still contain a separately tracked invoice, rights question, or agreed follow-up duty.
How is this handoff approach supported?
Practical notes
- The handoff register and single-release example are constructed operating tools. They do not describe a private Records client, contractual standard, guaranteed delivery, or campaign result.
- The reporting cross-check uses the categories in Velveteen Records' published campaign-report guide. The platform-access guide supplies the related setup context; this article focuses on tested acceptance at the end of agreed services.
- Platform instructions were checked on October 21, 2026. File delivery and permission changes should follow the actual agreement and authorized account controls; this guide is not legal advice.
Source notes
- Spotify Support, Removing team members from Spotify for Artists, checked October 21, 2026: Team Admin scope and web removal steps. https://support.spotify.com/us/artists/article/removing-team-members-from-spotify-for-artists/
- Spotify Support, Getting access to Spotify for Artists, checked October 21, 2026: claimed-team invitations and support when the Admin cannot be reached. https://support.spotify.com/us/artists/article/getting-access-to-spotify-for-artists/
- Google Drive Help, Make someone else the owner of your file, checked October 21, 2026: folder ownership does not transfer the files inside, account eligibility restrictions, and personal-account transfer acceptance. https://support.google.com/drive/answer/2494892
- Velveteen Records, How to Write a Post-Release Campaign Report and How to Set Up Platform Team Access Before a Release Campaign, current registry text checked October 21, 2026. https://velveteenrecords.co/guides/how-to-write-a-post-release-campaign-report and https://velveteenrecords.co/guides/how-to-set-up-platform-team-access-before-a-release-campaign
Frequently asked questions
- Should we wait until the next release to organize the handoff?
- Arrange it around the agreed campaign end while the people and source records are available. Keep any later duties explicit instead of depending on informal access continuing indefinitely.
- Can the incoming team receive the outgoing partner's password?
- Use the platform's proper invitation, role, or recovery process instead. A handoff should establish authorized continuing access without passing around a personal login or its recovery credentials.
- Do screenshots replace the reporting workbook or source export?
- Screenshots can preserve a point-in-time view, but they may omit filters, dates, calculations, or underlying rows. Agree the required reporting format and identify any information the recipient still cannot verify.
- What if the outgoing partner cannot transfer a file directly?
- Check the platform and account restrictions, then agree a permitted delivery alternative with the relevant rights holder or administrator. Keep it unresolved until the continuing team has tested the agreed result.
- Should a disputed invoice be marked paid to finish the handoff?
- Keep its actual status and the responsible person visible. Operational signoff does not require inventing a payment outcome or resolving a dispute without the appropriate professional advice.