Delivering to a Client

Delivery succeeds when the client does not have to ask again, not when the folder is complete

Delivery is not sending an audio file. The client wants something usable immediately, and answers they can find without calling you.

What you are delivering

A package: master, stems, a version matrix (main, instrumental, short cut, bed), a one-page note, and an archived session. Scope follows the contract; nothing extra is implied.

Three steps

1. List what the contract promises: format, sample rate, bit depth, duration, version count, revision rounds and deadline. 2. Build the version matrix with one file per version, names carrying version and date instead of relying on folder structure. 3. Write the one-page note (tools, changes, licence and credit) and archive the session where it can be reopened.

Pages and tools to use

• Master delivery formats — format, sample rate, bit depth and true-peak margin stated once.
• Stems delivery — stems are for downstream work; naming and grouping must be usable as-is.
• Contract checklist — scope, disclosure, rights, revisions and exit, agreed before work starts.
• Client review workflow — three options at a time, staged feedback, revisions with a boundary.
• Documentation of process — tools, versions, prompts, seeds and edits written down.

Acceptance checks

• Every checklist item matches: format, sample rate, bit depth, duration, version count, with no assumed gaps.
• Loudness meets the agreement (e.g. −14 LUFS, true peak ≤ −1 dBTP) and stays consistent across versions.
• Revision rounds and feedback timestamps are logged, and the client confirms receipt within 48 hours.

Sources

• 本页为场景导航，链接目标为已发布条目（2026-10-31 核对）

Used for fact-checking only; all prose is original.