A useful way through
- Write the intended output: a demo, a finished song, a rehearsal reference or a soundtrack sketch. Name the people who approve it.
- List the material ready now and the decisions still needed. Include the expected instruments, performers and arrangement questions.
- Agree practical details with the actual studio: timing, accessible arrival, engineer, file formats, backups and revision scope.
- Create a handover checklist with file names, versions and ownership or permission questions to resolve. Keep an untouched copy of the delivered originals.
Read the map as text
LISTENING MAP · 01 · Purpose · 02 · Ready material · 03 · Session · responsibilities · 04 · Files and · revisions
- Purpose
- Ready material
- Session responsibilities
- Files and revisions
A filled one-page brief for a small demo
This is a fictional planning example for a solo songwriter. It specifies a possible session; it is not a booking, price quotation or report of a recording that took place.
| Purpose | Let two collaborators hear the song's structure and words before deciding on a band arrangement. A finished commercial master is outside this session. |
|---|---|
| Material ready | One lyric sheet, a chord chart and a phone reference named Window-reference-v02. Mark the changed final verse on the lyric sheet before recording. |
| Proposed session | 10:00–10:15: setup and a short level check. 10:15–10:35: guide take and playback. 10:35–11:05: three complete takes. 11:05–11:20: choose the reference take and list repairs. 11:20–11:30: export, copy and playback check. |
| Responsibilities | Songwriter brings approved words and confirms the arrangement. Recording collaborator names takes and marks interruptions. Both agree the reference take before leaving. |
| Proposed delivery | One stereo reference WAV at the format agreed before setup, the editable session if both parties agree to hand it over, and a short take log. Decide separately whether dry tracks are required. |
| Open decisions | Simultaneous vocal and guitar or overdubs? Click track or free timing? What software and export format can the recipient open? Who may share the demo? |
Make the handover testable
Name a reference Window-v03-take02-reference.wav, not final-final.wav. Beside it, keep a README giving the song version, selected take, agreed format, any unfinished edits and the recipient. If the recipient cannot open the session software, an editable project alone is not a usable delivery.
Before approving the handover, the collaborators should open the copied reference, listen to its beginning and ending, and check it against the agreed song version. This describes a proposed acceptance check; no such client handover is claimed here.
Change the plan when the work changes
If setup overruns by twenty minutes, choose a smaller agreed result, such as one complete reference take and a repair list. Do not silently turn the missing time into an unapproved promise of mixing or mastering. The versioned songwriting example shows the information worth preserving before the session.
New fictional brief and filenames created for this guide. Confirm actual time, equipment, delivery rights and terms with the people doing the session.
Your take-away checklist
Before a recording session: make a one-page brief
- □ Purpose: ____________________
- □ Ready material: ____________________
- □ Session responsibilities: ____________________
- □ Files and revisions: ____________________
Before you act
Use the linked artist, publisher or presenter for exact credits and current availability. These listening and planning exercises are additional exercises, not quotations from a lesson by Michael Thurber.
Sources & context
Thurber’s artist site describes a Williamsburg production suite and separate learning paths in production, songwriting, theory and bass. That description supplies context for this planning guide; equipment lists and lesson availability should be confirmed directly before any booking.