An audio project delivery page is one link that holds everything a client needs at the end of a job: the approved files, clear labels, handoff notes, the project status and a way to approve or ask for changes. Build it so a client can open it cold, know which file is final, and never need to email you to ask “which one is the right one?”
This guide covers what goes on the page, how to organize it, how to show status and revisions, and a simple template for mixing, mastering, podcast and post-production work.
TL;DR
- A delivery page lists the approved main mix, agreed alternates, stems if contracted, and a labeled MP3 reference, plus a short notes file (Soneam’s mix delivery checklist).
- Put the project status and version at the top, and say plainly what the client should do next: review, approve or request a revision.
- Use one naming convention and folder structure from project setup, so every file explains itself.
- Protect the page with a password or revocable link, and track downloads.
- Keep review comments and final approval in the same place as the files, not scattered across email and chat.
Table of Contents
- What a project delivery page actually is
- What to include on the page
- How to list and organize deliverables
- Check the work before the page goes out
- How to show status and revision progress
- Make feedback and approval unmistakable
- Protect the delivery
- A delivery page template you can copy
- Our perspective: the delivery page is part of the product
- Build your delivery page in Audome
- Common mistakes to avoid
- FAQ
- Sources
What a project delivery page actually is
In general project management, “project delivery” often means a whole framework or methodology. Most of what ranks for the phrase is about that: portfolios, delivery models, construction contracts. This article is about something narrower and more practical: the page you send to a client when audio work is ready to hand over.
Think of it as the front desk of a finished project. The client does not need your session, your folder tree or your history of bounces. They need to see what was agreed, what is done, what to listen to, and what to do next.
A good delivery page does four jobs:
- Identifies the project. Name, client, version and current status.
- Lists the deliverables. Every file, labeled, grouped and easy to download.
- Explains the handoff. Technical notes, usage information and anything printed into the mix.
- Closes the loop. Feedback, approval and, if the job is not finished, what happens next.
What to include on the page
Start with the files themselves, then add the context that makes them usable.
The audio files
A solid mix delivery includes the approved main mix, any agreed alternates, stems if they are part of the contract, and a labeled MP3 reference. Soneam’s checklist lists these as the core of a delivery, and it is a sensible baseline for any studio.
Typical alternates include:
- Instrumental
- TV mix (vocals removed except backing)
- Vocal-up and vocal-down versions
- Clean and explicit versions
- A cappella
Only list what was agreed. A page cluttered with extras makes the real final harder to spot.
The handoff notes
Notes should state the tempo, key, session sample rate, what is printed into the mix, and which file is which, according to the same Soneam guide. Add file-use information too: whether the files are for release, for sync, or for review only.
A short notes block might read:
Tempo: 92 BPM. Key: F minor. Session rate: 48 kHz. Reverb and tape saturation are printed on the lead vocal. Stems are full-length and start at 0:00 so they line up in any session.
For a podcast, swap that for loudness target, episode number, chapter markers and which intro and outro versions are included.
Metadata that travels with the file
Notes on a web page can get separated from the audio. Metadata inside the file cannot. The Broadcast Wave Format’s axml chunk, for example, can carry an ISRC and other structured information in a machine-readable form, as explained in Code Group Music’s guide to embedding ISRC in WAV files. If you deliver masters for release, agree with the client who is responsible for codes and credits, and embed what you can. For a wider look at which fields to lock down before release, these music metadata rules for independent artists are a good checklist to share with a client.
Extra documents for post-production
Film, TV and dubbing work needs more paperwork. Delivery documentation in professional audio post can include conform documents such as EDLs and change lists, QC reports, loudness measurement reports and the production audio archive, as Forte’s post-production deliverables checklist describes. Put each one on the page as its own labeled item, not buried in a zip. Our own walkthrough of a seven-step QC audio review shows how to turn QC findings into a report a client can read.
How to list and organize deliverables
Clients skim. Organization is what makes a page feel professional.
Group by purpose, not by date
Use short groups with plain names:
- Final masters (the files they will release or broadcast)
- Alternates
- Stems
- Reference MP3
- Documents (notes, cue sheets, reports, lyrics, credits)
Put the group the client cares about most at the top, nearly always the final main mix.
Name files so they explain themselves
A professional workflow agrees file-naming conventions, folder structure and versioning rules during project setup, as this dubbing workflow overview points out. Do the same for every job, even small ones. A file called final_FINAL_v3_realfinal.wav shows up in every studio’s history, and it is exactly what a delivery page should prevent.
A readable pattern includes project, title, version, mix type and sample rate:
ClientName_SongTitle_v04_Main_48k24.wav
If you want a fuller template, we wrote up a nine-field file naming policy and a six-step mix version naming system you can adapt.
Show format and size next to each file
Beside each item, show the format, sample rate and bit depth (for example, WAV, 48 kHz, 24-bit) and the file size. Clients on slow connections will thank you, and engineers on the other end can see at a glance whether a file matches their session.
Our post on exporting audio deliverables for clients goes deeper on formats and export settings.
Check the work before the page goes out
The page is only as good as what it links to. Before you send it:
- Confirm the session sample rate and your export routing.
- Listen to the full render for clicks, missing audio and incomplete fades.
- Export the agreed files.
- Name them consistently.
- Send a review link.
- Protect the final delivery.
That sequence follows the process Soneam recommends, and it works as a personal pre-flight list. The listening pass matters most. A full real-time listen catches the problems a bounce can hide, such as a dropped region or a fade that ends early.
How to show status and revision progress
Status is the part most delivery pages skip, and it is the part clients ask about most. A simple status line saves a round of emails.
Use a short, fixed set of statuses
Pick four or five and use them on every project. For example:
| Status | What it tells the client | What they do next |
|---|---|---|
| In progress | Work has started, nothing to review yet | Nothing |
| Ready for review | A version is uploaded for listening | Listen and leave comments |
| Revision in progress | Your notes are being worked on | Wait for the next version |
| Approved | The client signed off on a specific version | Download final files |
| Delivered | Final files and documents are available | Confirm receipt, archive |
The exact words matter less than keeping them the same. Each status should answer two questions: where are we, and whose turn is it?
Show the version number with the status
Pair every status with a version. “v3, Ready for review” is clear. “Ready for review” alone is not, because the client may be thinking of v2. Composers working with many cues use the same idea on production sheets, marking each cue’s version number as Revision or Approved (Thomas Bryla’s production sheet approach is one example). The principle applies equally to a multi-song album or a podcast season: status per item, not just per project.
Keep old versions out of the way
The page should surface the current version and tuck earlier ones below, labeled and dated. Clients sometimes want to compare v2 against v4, but they should never have to guess which one is current. Our guide to project tracking for faster audio post-production shows how to keep that history tidy.
Make feedback and approval unmistakable
A delivery page that ends at “here are your files” leaves the hardest part to email. Approval needs a clear place.
Feedback tied to the audio
Vague notes like “the vocal feels buried in the second chorus” cost time. Notes anchored to a moment in the waveform (“1:42, vocal is buried”) do not. Ask clients to comment at the exact time they are listening, and keep every comment next to the version it refers to. When feedback arrives that way, your next pass is a list of fixes, not a puzzle.
Define what approval means
Write one sentence on the page that says what approval triggers. For example: “Approving v4 confirms the mix is final and releases the master files for download.” If your contract limits revisions or bills extra rounds, state it here too, in a short line near the review area, so nobody is surprised later.
Record who approved and when
Approval should leave a trace: the version, the person and the date. If a question comes up months later, you can point to it. Our producer client workflow guide walks through how to build that into your normal routine.
Protect the delivery
Unreleased audio is valuable. Soneam recommends password protection, revocable links, download tracking and a checksum for final deliveries (their checklist). In practice:
- Password or private link so only the client sees it.
- Revocable access so you can shut the link off if it is forwarded or the project ends.
- Download tracking so you know the client actually collected the files.
- Checksum so a client can verify a large file arrived intact.
We compare several ways to do this in five methods for password-protected downloads, from zipped archives to signed URLs.
A delivery page template you can copy
Here is a layout that works for most audio jobs. Adjust the wording to fit your studio.
- Header: Project name, client name, your logo.
- Status bar: Current version and status, plus the next action in one line.
- Final deliverables: Main mix, alternates, stems, each with format and size.
- Reference MP3: For quick listening on a phone.
- Handoff notes: Tempo, key, session rate, printed effects, file-use terms.
- Documents: Cue sheets, credits, QC and loudness reports where relevant.
- Review area: Time-stamped comments and an approve button or approval line.
- Version history: Earlier versions, dated and labeled.
- Contact: How to reach you for anything not covered.
For a podcast, replace alternates and stems with episode files, show notes, chapter markers and transcripts. For a mastering job, include the DDP or WAV masters, a PQ or track list, and the format each streaming or physical release needs. Our guide to label-ready final masters covers what to check before you release them.
Our perspective: the delivery page is part of the product
We talk to a lot of engineers and producers, and the pattern is consistent. The mix is excellent, and then the handoff goes sideways: a link that expired, a client who downloaded v2 instead of v4, feedback split across text messages, a voicemail and a PDF.
The client does not judge the work only by the audio. They judge it by how it arrived. A tidy delivery page tells them you are organized and that the project is under control.
That is why we built Audome around a single hub for the whole job: uploads, version tracking, time-stamped feedback on the waveform, and client portals that can carry your own branding. Clients can review without creating an account, files are shared in their original quality up to 96 kHz/24-bit, and revision limits and paid revisions can be handled in the same place. Our aim is that the delivery page is not a separate chore at the end. It is what the project looks like from the first upload.
If you have ever re-sent a final file because a client could not find the last one, you already know what that saves.
— Kreg
Build your delivery page in Audome
If you would rather not assemble this from a shared folder, a document and an email thread, Audome gives you the pieces in one place: project pages, automatic version tracking, password-protected and branded client portals, download controls and time-stamped feedback.
Plans start with the Studio plan at $12.50 per month or $150 per year, and the Pro plan is $48 per month or $576 per year. You can see what each includes on the Audome pricing page, or look at the Audome home page for an overview of the platform.
Common mistakes to avoid
- Sending too many files. Every extra file is a chance for the client to pick the wrong one.
- Hiding the status. If the client cannot tell whose turn it is, they will email you.
- Skipping notes. A stem set with no tempo, key or sample rate wastes the next engineer’s time.
- Leaving links open forever. Set access that fits the job and revoke it when it is done.
- Mixing feedback channels. Pick one place for comments and say so on the page.
- Changing names mid-project. Agree the naming scheme up front and keep it. Our collaboration workflow guide explains how to set that up.
FAQ
What is a project delivery page?
It is a single page or link where you give a client the finished files and everything around them: labels, notes, status, version and approval. It replaces scattered emails and shared folders with one clear place to find the final work.
What should be on an audio delivery page?
At minimum: the approved main mix, agreed alternates, stems if contracted, a reference MP3 and a notes file with tempo, key and session sample rate. Add the project status, version number and a way to approve or request changes. Post-production jobs may also need reports and conform documents.
How do I show project status to a client?
Use a short, fixed set of labels such as In progress, Ready for review, Revision in progress, Approved and Delivered, and show them next to the version number. Add one line saying what the client should do next, so the page answers the question before they ask.
Should the delivery link be password protected?
Yes, for unreleased work. A password or private link keeps the audio with the intended people, and revocable access lets you close the page when the project is done. Download tracking also tells you whether the client collected the final files.
How many revisions should a delivery page allow?
That comes from your contract, not the page. Whatever you agreed, state it briefly near the review area, including how extra rounds are handled, so the client sees the rule before they send feedback.
Sources
- Mix Delivery Checklist: What to Send a Client, Soneam
- Embed ISRC in WAV Files: BWF axml Guide, Code Group Music
- Post-Production Audio Deliverables Checklist, Forte
- The Dubbing Process Explained: End-to-End Workflow, Sukudo Studios
- Project Management 104, Thomas Bryla