# Release requests
Source: https://docs.aden.space/docs/help/release/release-requests

Turn a track share link into a release request. Pick a due date and what to ask for (master, cover, credits, ISRC, release date); the person with the link delivers it on the share page, where each file is checked against store specs as it lands and the list ticks itself off.
{/* Generated by `bun docs:publish` from docs/features/release-requests.md: edit the spec, not this file. */}

## What it is [#what-it-is]

A release request is a share link that also asks for the release. Instead of
collecting the master, the cover and the credits yourself over email, you
send the artist one link with a due date. They deliver everything on the
share page, and you see what has arrived and what is still missing.

## Using it [#using-it]

**From the share dialog.** Share a track as a link and add **Ask for
delivery**: pick a due date and what to ask for (master, cover art, credits
and splits, ISRC, release date). Add the artist's email to make the link
theirs.

**From the track.** The track's **Delivery** page (track **+** menu, the
sidebar, or ⌘K: "request delivery for Afterglow") has **Request delivery**,
which makes the same link and copies it. It lists the open requests with
their due dates; copy a link again or close a request there.

**What the artist sees.** The share page shows **Deliver this release** above
the versions: a checklist with one button per item. They sign in, then
upload the master (it becomes the track's final version), upload the cover,
fill in who did what and the splits,
and add the ISRC or release date. They don't join your team: the link is
what lets them deliver. Each item ticks itself off as it is filled in.

**Covers are checked before they upload.** A cover that stores would reject
(too small, not square, CMYK, transparent) is refused on the spot with what
to fix, measured against Apple Music's spec, the strictest major store. The
master is checked the same way once it's uploaded.

**Next time is faster.** A new request starts from what your team asked for
last time.

Your organisation's **Releases** page shows each release's nearest due date
next to what it still needs, in red once it's overdue.