Your first session as an assistant

New assistants prepare by learning the console. The console is the smallest part of the job and the part most easily looked up while standing in front of it.

What you are actually being hired for is attention — specifically, the capacity to hold every practical detail of the day so that the person making musical decisions does not have to. That is a skill, it is learnable, and nobody teaches it because it does not look like a skill from the outside.

The actual job

Know where everything is. Know where everything is going to be needed, and have it there before anybody asks. Write down what happened. Keep the session file clean and the room fed.

None of that is glamorous and all of it is what gets you asked back. The engineer is holding the musical decisions in their head and has no capacity left for logistics. You are the logistics.

Nobody remembers who set up the mics. Everybody remembers who lost the take.

Before anyone arrives

Get there early enough that being early is invisible. Every input tested and producing signal, every cable labelled at both ends, the session template open with tracks named and record-armed, headphones untangled and plugged in, spare batteries and a spare cable for anything that could fail.

The reason for the redundancy is not perfectionism. It is that every fault discovered during the day costs the room's attention, and the room's attention is the only genuinely scarce resource in a studio.

During

Two rules cover most of it. Do not speak unless spoken to or unless something is on fire, and write everything down.

The first sounds harsh and is not about hierarchy. A session has one channel of spoken attention and it belongs to the person directing the performance. Anything you say costs somebody their thread. Save it, batch it, and deliver it in the gap.

The second is where you become indispensable. A take log with take numbers, timestamps, and what anybody said about each one is worth more at mix time than any amount of technical knowledge. When the producer says the second chorus from the one where she laughed at the end, you are the only person in the building who can find it.

• Take number, time, and a one-line note on what happened.
• Anything the artist or producer said they liked, in their words.
• Any technical event — a cable swap, a gain change, a phantom power toggle.
• Where the session file is saved, and when you last saved it.

Saving, which is the whole job in one word

Save constantly, and save to a new version at every natural boundary — between songs, before any structural change, after any take anybody reacted to. Back the session up before you leave, to a drive that is not the one it lives on.

The one unforgivable failure in this role is losing work. Everything else is recoverable. An assistant who is a bit slow patching but has never lost a take will be working long after someone quicker who lost one.

What gets you asked back

Being easy to have in the room. Anticipating rather than reacting. Not making the day about your learning. Knowing when to be invisible and when to have already solved something.

The technical knowledge accumulates on its own, faster than you expect, just from being present. The habits of attention do not, and they are the actual qualification.