WORKING WITH MUSIC
Finish and deliver a music production
Finishing is not listening until every doubt disappears. It means meeting a defined request, checking the result and making the delivered version unmistakable.
On this page
Separate intent, review and verification
Intent describes the desired result. Review asks whether you achieved it musically. Verification finds file problems. Correct measurements do not guarantee an engaging mix; a mix people like may still be exported incorrectly.
Example: approved mix, pending files
Version 03 is approved as stereo and instrumental. Before export, confirm sample rate, bit depth, channels, start, tail, filenames and destination. If stems are requested, ask which groups, whether they must reconstruct the mix and which effects they contain. Do not assume stems mean individual tracks or that summing them recreates bus processing.
Ask for actionable revisions
Consolidate one list per round. “The vocal loses clarity at 0:48 when guitars enter” identifies a problem; “make it more professional” needs a follow-up question. Where requests conflict, ask the approval contact to set priorities before starting another version.
Listen to the exported file
Open the actual final file and check the beginning, end, channels, edits and tails. Compare versions at reasonably matched listening levels. Check mono where appropriate. Use the Delivery checker against the request, distinguishing detected properties from matters needing listening or manual confirmation.
Write an unambiguous handover
“Here are Song_A_Mix03, stereo and instrumental, following the confirmed request. A file list is included. These checks remain outstanding: […]. Please confirm that the files open and whether you approve this version or have feedback within the agreed revision round.” Sending a link does not establish approval.
Close without losing context
Keep the approved version, delivered files, terms and confirmation. Define how long source files will be retained and whether DAW sessions are included. Retaining a copy does not authorise portfolio publication. If you keep revising without a defined problem, write down the intended improvement and compare before replacing an approved file.
Continue with HertzKit
Sources and scope
Original HertzKit examples and worksheets. Sources checked on 7 November 2026; foreign guidance does not establish rules in your country. No affiliation or endorsement.