Gabs Utilities

Free studio utility / WAV handoff

Free WAV delivery handoff checklist.

Use this before sending bounced WAVs to a client, label, collaborator, archive or release workflow. It is deliberately practical: confirm the brief, inspect the files, listen in the right places, then send a package that is easier to trust.

Free reference · no signup

Use the checklist ↓ Read handoff guide Automate parts with the CLI View sample report
For real handoff foldersMasters, alternates, stems, label packages, client approvals and archive deliveries.
No fake universal targetUse the client, label or platform brief. If there is no brief, mark your format as provisional.
Human listening stays centralA checklist can catch mechanical mistakes. It cannot approve taste, balance or emotional impact.

The checklist

01

Confirm the delivery contract

Write down what the recipient actually needs before touching files.

  • Client, label, collaborator, archive or release destination.
  • Artist, project, title, revision and approved mix/master identity.
  • Expected asset list: main master, instrumental, clean version, stems, artwork, credits, notes or metadata.
  • Sample rate, bit depth, channel layout, loudness and peak rules only when the brief or destination actually states them.
  • Filename convention, transfer method, deadline and any required checksum or delivery note.
02

Inventory the folder before sending

Look at the package as a recipient would receive it, not as a DAW project you know by heart.

  • Expected files are present and non-empty.
  • No hidden exports, old bounces, private notes, session files, cache folders or ambiguous drafts are mixed into the package.
  • Every file has a clear purpose and a clear version.
  • The folder can be zipped, reopened and understood without extra explanation.
03

Inspect the audio evidence

Check the exported files themselves, not only the DAW meters or the memory of the session.

  • Readable WAV headers, sensible duration and nonzero size.
  • Sample rate, bit depth and channel layout match the brief, or the deviation is documented.
  • No obvious truncation, missing tail, accidental silence, wrong start, wrong ending or wrong version.
  • Stems and alternates share the expected start point and naming pattern.
04

Listen where mistakes hide

Do not rely on one casual full playback. Hit the high-risk moments deliberately.

  • Start, ending, loudest section, quiet section, transitions, breakdowns and final tails.
  • Any edit, automation move, drop, mute, cut, render boundary or bounced external effect.
  • Mono compatibility or phase-sensitive sections when relevant to the music or delivery.
  • For stems, rebuild the mix in a clean session if stem reconstruction is part of the contract.
05

Clean the handoff context

The best audio file can still create a bad delivery experience if the surrounding context is messy.

  • Use unambiguous filenames: artist, title, role, version and date when useful.
  • Add credits, metadata, revision notes, artwork and contact context when the recipient needs them.
  • Remove duplicate “final”, “latest”, “new new”, “v2 old” style files unless they are intentionally included and explained.
  • Create a checksum manifest if the delivery is important, large, repeated or archival.
06

Reopen the final package

The sent package is the product, not the folder you meant to send.

  • Open the final ZIP or transfer folder after export.
  • Confirm the archive contains only the intended files.
  • Check that the delivery note and checksums are inside or beside the package as intended.
  • Send with a short, clear note that names the version and any known deviations.

Red flags worth stopping for

Ambiguous versions

`final.wav`, `final_FINAL.wav` and `master_latest.wav` in the same folder is not a delivery system. Stop and clarify.

Unknown target

If the required format is unknown, label your delivery choice as provisional instead of pretending it is the destination’s rule.

Unopened archive

A ZIP existing on disk is not proof that it contains the correct files. Reopen and inspect it.

No human listen

Technical checks do not replace listening to beginnings, endings, transitions, tails and problem sections.

Copy-paste delivery note

Hi — attached is the delivery package for [artist/title], version [version/date]. It contains [asset list]. Format is [sample rate / bit depth / channel layout] according to [brief or provisional assumption]. Known notes/deviations: [none / list]. Please confirm receipt before using this as the final delivery source.

Automate the mechanical part

The checklist is free and manual. Audio Delivery Preflight CLI automates part of this process locally: inventory, technical file evidence, delivery hygiene, reports and checksums. It does not upload audio, rename files, master music, judge artistic quality or guarantee distributor acceptance.

audio-preflight scan /path/to/delivery --preset digital-release \
  --report-html /path/outside/delivery/preflight-report.html \
  --checksums /path/outside/delivery/SHA256SUMS.txt
See the paid CLI Read handoff guide Inspect a sample report Open press / launch kit Critique the checklist/tool