Session Recall Notes: What to Write Down and How

By /

Session recall notes are the written record of everything needed to reopen a recording, mix or master and get back to the same sound: the files, the DAW settings, the outboard gear positions, the mic setup and the changes a client asked for. Write them while you work, keep them in the project folder, and you can pick up a session weeks later without guessing. This guide covers what to include, how to document hardware, a workflow that holds up on busy days, and how to keep client feedback attached to the same record.

Audome
audome.com
Keep Audio Feedback With Your Projects
Audome brings audio project management and timestamped feedback together, helping collaborators keep revisions and communication in one hub.

Explore Audome

TL;DR

  • Session recall notes capture what the DAW cannot restore on its own: mic choice and placement, preamp settings, outboard gear controls and client decisions.
  • Log project identity, dates, formats (sample rate, bit depth), signal path and per-track details. Add precise control positions for any hardware.
  • Keep notes in a dedicated documentation folder with descriptive names and YYYYMMDD dates, so they travel with the project.
  • Take notes while listening to a rough mix and again after opening the session, then cross items off as you fix them.
  • Log client requests with timestamps and version numbers, so “a bit more vocal” never turns into an argument.

Table of Contents

What session recall notes are and why they matter

A recall note answers one question: if I had to rebuild this exactly, what would I need to know? Projects often stretch across days, weeks or months and jump between songs. Carlos Lellis, in Music Production: Recording, explains that session notes and recall or track sheets preserve the file, the DAW regions or tape reels, and the equipment parameters that keep that work continuous. His framing is practical: documentation prevents wasted time and costly mistakes when a project is spread out or changes songs.

The same habit pays off across the audio trades:

  • Recording: mic, position, pad state and preamp settings.
  • Mixing: hardware insert settings, bus routing, automation notes and client revision requests.
  • Mastering: processing chain notes that make remasters and handoffs painless. Nick Messitte of iZotope describes mastering notes as useful for exactly those cases.
  • Podcasts: timestamped notes on interviews, which Messitte also points to as a help during editing.

If you only take one thing from this page: the more of your chain lives outside the computer, the more your notes matter.

What a session recall sheet should include

The fields below follow the forms engineer Barry Rudolph publishes in his session documentation set. Use them as a checklist and cut what a given job does not need.

Project basics

  • Artist or client, project and song title
  • Dates, plus the studio, engineer, assistants and start times
  • Track names, performers and track numbers

Technical formats

  • Recording and mix formats
  • DAW or machine details, sample rate, bit depth and sync source
  • Format of the saved files

Mix details

  • Console, automation and monitoring setup
  • Mix-bus path
  • General notes

Rudolph’s track sheet adds artist, song title, track number, track name, performer, comments, start time, sample rate and bit length for each track. That is a tidy minimum.

Tracking details people forget

Mark Marshall’s guide at Pro Audio Files says session documentation should cover microphone choice, microphone position, pad state, drum kit, cymbals, sticks, changed drum heads and guitar-volume settings. These are the details nobody remembers three weeks later when the overdub session arrives and the guitar suddenly sounds different.

Key details to record for session recall

Documenting gear, signal chains and DAW settings

The digital recall gap

It is tempting to assume the session file holds everything. Marshall points out that DAW channel strips recall internally, while microphone positions and mic-pre details do not. His central point: digital recall does not remove the need for documentation, it moves the undocumented risk toward microphones, preamps, physical setup and anything before the converters. Write those down.

Outboard gear

Hardware does not restore itself. Messitte advises keeping a recall sheet whenever audio leaves the box for hardware processing, so you can dial in the intended settings when you return to the track. He also recommends writing precise control positions rather than relying only on photos: for example, clicks above or below a reference mark, switch states, ratio and mode.

A quick example entry for a hardware compressor on a lead vocal:

Field Entry
Track Lead vocal, take 4 comp
Device Stereo bus compressor on insert 2
Ratio / mode 4:1, fast attack, auto release
Threshold 2 clicks below reference mark
Makeup Noon
Notes Hits 3 dB of gain reduction on the chorus

The exact form matters less than the discipline of writing a value for every control that affects the sound.

Photos as backup

When the room is moving fast, photos help. Kyle P. Snyder, writing at ProSoundWeb, notes that photographs can capture front panels and microphone placement when there is no time to write, though they may not give a detailed diagram or precise settings. Treat photos as a safety net and written values as the record.

Plugins and DAW changes

Plugin settings recall with the session, but your reasoning does not. A one-line note such as “rolled off 80 Hz on bus because kick masked the bass” saves the next person from undoing a decision they do not understand. Log any change to sample rate, bit depth, sync or plugin chain order, since those affect how the session reopens.

A workflow that keeps notes accurate

Choose a method you will actually use

Snyder presents paper take sheets, track sheets and session logs as practical ways to capture information during busy work, and treats the method as context-dependent: paper is immediate, photos are fast, and the best choice is whatever captures usable evidence under time pressure. If you also capture voice memos or quick phone clips of the room setup, the same logic applies to recording on your phone in the moment: get the information down first, tidy it later.

Give notes a home in the project folder

Rudolph’s folder hierarchy guide recommends separate areas for recording documents and notes, mixing documents and notes, and credits and metadata, next to multitracks, mixes, approved mixes and mastered files. It also recommends descriptive names and YYYYMMDD dates without hyphens. So a file might be called 20261106_MixNotes_LeadVocal_v3.pdf. Sorted alphabetically, that always lands in date order.

Take notes at three moments

  1. Before you touch anything. Messitte recommends taking notes while listening to a rough mix, then repeating the process after opening the session. The result is an ordered battle plan instead of memory.
  2. During final passes. Keep notes specific and measurable: the section, the problem and an approximate dB change. Cross each item off as you address it.
  3. When audio leaves or returns. Any time a stem goes to hardware or a mastering engineer, update the sheet before you close the session.

Log client changes

Messitte suggests logging client changes so you can reproduce requests like “split the difference” between two mixes. That only works if the log says which versions were compared and what the final values were. Our guide to audio version history covers how to name and track every mix and master, and 6 fields every mix note needs shows how to make client notes specific enough to act on.

Log client changes

Templates you can adapt

You do not need to design a form from scratch. Rudolph provides recording, tracking, mixing, transfer and track-sheet forms covering project identity, technical formats, mix details and notes. The Audio Magazine offers a generic mix recall sheet with fields for studio, project, date, engineer, session or song, channel, source, fader, pan, insert, EQ, dynamics, sends and notes.

Device-specific sheets work even better for repeat gear. Rudolph’s preset parameter log records preset name, parameter type and value, including reverb time, size, pre-delay, diffusion, density, modulation and delay settings. His recall sheet library shows that templates can be built around a particular front panel, not one universal form.

How to adapt them:

  • Tracking day: emphasize mic, position, preamp and room notes.
  • Mix: emphasize inserts, sends, bus processing and a revision log.
  • Mastering: emphasize chain order, settings, target loudness and delivery formats.
  • Podcast: emphasize timestamps, edit decisions and episode metadata.

Keep one master template per job type and duplicate it for each project.

Perspective

Most recall notes fail for one reason: they live somewhere other than the work. The sheet is in a drawer, the client email is in an inbox, and the revision requests are in a text thread. When you reopen the project, you rebuild the story from scraps.

We built Audome around the opposite idea. Keep the project, the files, the versions and the feedback in one hub, so the record of what happened sits next to the audio it describes. Clients can leave time-stamped comments on the waveform, so “the vocal feels buried” becomes a note pinned to an exact moment. Automated version tracking shows which mix a comment was about. And because audio is shared in high resolution, up to 96kHz/24-bit, everyone is judging the file you actually made.

Hardware settings still belong on your sheet, and we would never tell you otherwise. But the decisions that cost the most time are usually the human ones: who asked for what, on which version, and whether it was approved. That is the part we want to take off your plate.

Kreg

Keeping the record after delivery

Recall notes are most valuable months later, when a client returns for a remaster, a alternate version or a stem pack. A few habits make that easy:

  • Archive notes with the final files. Our guide on backing up client projects recommends one working copy and two archives, and notes belong in all of them.
  • Write a short wrap-up. A project recap summary captures final versions, fees and what was delivered in one page.
  • Set a retention rule. Decide how long you keep sessions and what retrieval costs; our piece on a studio file retention policy walks through it.
  • Lock the approved version. A clear approval process means the notes point to one final file, not three.

For the wider picture of how notes fit into the day, see our recording studio workflow guide.

Put client feedback and versions in one place

If your recall sheets cover the room and the rack, Audome covers the conversation with the client. You upload mixes, share them through a branded, password-protected client portal, and clients comment on the waveform without needing to log in. Versions are tracked automatically, revision limits can be set, and paid revisions can be billed through Stripe.

Audome

Plans start with a free trial. Studio is $12.50 per month or $150 per year, and Pro is $48 per month or $576 per year. See what each includes on the Audome pricing page, or look around the Audome homepage first.

FAQ

What is the difference between a recall sheet and session notes?

A recall sheet is a structured form for settings: gear controls, routing, formats and track details. Session notes are broader and include decisions, problems, client requests and to-do items. Most engineers keep both together in the project’s documentation folder.

Do I still need recall notes if I work entirely in the box?

Yes, though the content shifts. The DAW restores channel strips and plugins, but mic choice, mic position, preamp settings and the physical setup are not saved in the session, as Mark Marshall explains. Even for a fully in-the-box mix, a short log of client changes and version decisions saves time.

What file format should I use for recall notes?

Use whatever you will open in five years: a PDF, a plain text file or a scanned paper sheet all work. Name the file descriptively and start it with a YYYYMMDD date, then store it in the project’s documentation folder next to the audio.

How detailed should hardware notes be?

Detailed enough that someone else could set the unit up without hearing the result. Write control positions, switch states, ratio and mode, and reference points such as clicks above or below a mark. Add a photo of the front panel as a backup.

When should I write the notes?

At the start of a session, while listening to a rough mix, at each major change, and whenever audio goes out to hardware or to another engineer. Writing as you go is faster and more accurate than reconstructing the session at the end of the day.

Sources

Scroll to Top