The Pre-Production Process

Pre-production is the period when a recording team decides what it is preparing to make, tests important assumptions, and records what must happen next. This guide is for independent artists, producers, engineers, bands, managers, and other recording-project leads working at home, in a hired room, or with remote contributors.

The goal is a documented go, hold, or rework decision and a usable session packet—not a promise that preparation will make a project cheaper, faster, safer, or more successful.

The five-stage process below is an adaptable Open Music Business framework, not an official industry standard or certification. Its general planning method is globally usable, but rights, contracts, worker status, union terms, accessibility, health, and safety depend on the facts and jurisdiction. U.S. and UK examples were checked on July 29, 2026.

Educational-content limitation: Open Music Business provides general education, not individualized legal, financial, tax, contract, royalty, employment, medical, accessibility, or safety advice. Use current project documents and qualified professionals for consequential decisions.

The short answer

For this guide, pre-production begins when you can describe the recording you may make and ends when an accountable person assigns its readiness status. Preparation depth varies across producers, genres, budgets, recording methods, and projects; the available practitioner evidence and limited comparative research do not support one universal checklist or a rule that every arrangement must be locked before recording. See Sound On Sound’s practitioner interviews and a two-producer comparison of pop and rock session management.

Use five stages:

1. Frame: Define the recording, people, constraints, and approver.
2. Test: Try the creative, performance, facility, and technical assumptions most capable of changing the plan.
3. Resolve: Close consequential rights, engagement, access, safety, and responsibility questions—or hold the affected work.
4. Plan: Assemble the production map, contributor briefs, schedule, files, metadata, and backup approach.
5. Approve: The approver assigns go, hold, or rework.

Readiness can include creative choices that are intentionally open. The useful distinction is among approved, testing, intentionally open, and hold—not simply finished versus unfinished.

Start here: the minimum path

For a low-risk solo or home recording, begin with this compact version:

1. Write down the intended recording, current song version, next deliverable, and who approves changes.
2. Name each uncertainty that could materially change the performance, files, schedule, budget, or rights position.
3. Run a targeted test for each important uncertainty, such as a voice memo, rough demo, rehearsal pass, file-opening test, or short technical pilot.
4. Record the result, current source file, backup responsibility, and any issue that must be resolved by someone else.
5. Assign go, hold, or rework, including the next action, owner, deadline, and affected version.

Add detail according to the project:

• Band: add part responsibilities, rehearsal decisions, shared charts or audio guides, note-routing rules, and a deadlock-breaking approver.
• Hired room or musicians: add current quotes and terms, access and setup windows, deliverables, cancellation or overtime questions, and payment responsibilities.
• Remote contributors: test the real exchange route, software versions, included audio, filenames, and return delivery.
• Higher-consequence project: increase scrutiny when work is difficult to repeat, technically unfamiliar, schedule-sensitive, dependent on disputed contributions, or exposed to unclear rights, engagement, access, or safety conditions.

Where jurisdiction-specific material appears

• Global planning: the five stages, creative tests, project packet, file planning, and readiness gate.
• United States: composition and sound-recording distinctions, sampling, copyright transfers, work made for hire, federal worker-classification status, ADA examples, and federal health or safety guidance.
• United Kingdom: Musicians’ Union recording-engagement prompts and BPI/MU agreement examples.
• Product-specific: Logic Pro and Pro Tools compatibility and backup examples.

Boundaries and essential terms

Songwriting develops the composition. A demo communicates or tests an idea. Pre-production, as defined here, prepares and tests a proposed recording. Recording or tracking captures performances or sound material. Editing, mixing, mastering, and release planning are later stages, although their expected handoffs may affect what must be prepared now.

These terms recur throughout the guide:

• Approver: the person authorized by the project to assign readiness or approve a defined change.
• DAW: digital audio workstation—the software used to record, edit, or exchange an audio project.
• Asset: an external file used by a project, such as recorded audio or another supported media file.
• Stem: in this guide, a team-identified grouped audio export, distinct from the complete multitrack project.
• Source of truth: the file or record the team has designated as the authoritative current version.
• Backup: a separate copy maintained for recovery, not merely another edit inside the working project.
• Restore test: a check that confirms protected material can actually be recovered and opened.
• RIN: DDEX Recording Information Notification, a licensed machine-to-machine format for exchanging studio-event metadata. It is optional, not a required worksheet for every project.

Stage 1: Frame the recording

Start with a one-page project frame:

• intended recording and deliverable;
• current songs or versions in scope;
• audience or intended use, if known;
• musical qualities that must survive the process;
• performers, producer, engineer, administrator, and approver;
• actual quotes, estimates, commitments, dates, and contingencies;
• decisions that may change and who can change them;
• work explicitly outside this recording phase; and
• expected handoff after recording.

Use actual exposure rather than assuming every studio or project is expensive. Record quoted charges, cancellation terms, contributor commitments, limited availability, or difficult-to-repeat work where they apply.

Create an uncertainty register beside the frame. For each unknown, record the question, consequence if unresolved, proposed test or specialist, owner, deadline, affected version, evidence, and status.

Conflicting notes should return to the named approver. Log which version each note concerns, what changed, and why. Silence or a missed deadline should remain visible; it should not automatically become approval.

Stage 2: Test the important assumptions

Creative and performance tests

Create a usable starting point for key, tempo, form, arrangement, parts, tuning, click strategy, and dynamics where those choices matter. Then mark each item approved, testing, intentionally open, or hold. Improvisational, electronic, and live-room projects may intentionally preserve more discovery than other approaches.

Possible tests include:

• perform the whole song in the proposed key;
• compare tempos or section lengths;
• map transitions and the energy arc;
• try two instrumentation or density choices in a representative section;
• test whether the ensemble can follow the planned click or tempo approach;
• decide where improvisation is invited and who approves the result; and
• check whether a performer needs notation, chords, lyrics, audio, visual cues, or another communication format.

Record the outcome rather than merely noting that a rehearsal happened. For example: Short intro approved for Version B; final guitar texture intentionally open; artist-producer approves changes.

A reference track or demo can communicate a chosen attribute, but its meaning is contextual. Label what listeners should notice—such as vocal intimacy, section contrast, drum density, or low-end restraint. A small mixing-focused study supports references as communication tools, but it does not prove a particular pre-production result or time saving. See the Audio Engineering Society study.

A rehearsal recording or paid pilot should answer a named question with a defined pass condition. Do not promise that a pilot will prevent a particular amount of re-recording.

People and facility tests

Confirm who is expected, their role, location, schedule, deliverable, communication needs, and approval route. For UK recording engagements, the Musicians’ Union advises written confirmation of the date, time, place, fee, applicable conditions, and authorized signatory. That is a UK planning prompt, not a worldwide rule about contract validity. See the Musicians’ Union recording-contract guidance.

Rates, overtime, additional services, consent structures, and other conditions depend on the applicable agreement and territory. The 2026 BPI/MU materials, checked July 29, 2026, illustrate that specificity; they do not establish terms for other work.

Do not use a freelancer label, payment method, or template to decide worker classification. As of July 29, 2026, U.S. federal policy remains in transition: the Department of Labor says the 2024 FLSA rule remains relevant to private litigation but is not being applied in its investigations, and a replacement has been proposed. Other tests may differ. Check the current Department of Labor status notice and 2026 rulemaking page, then obtain jurisdiction-specific advice when classification matters.

Ask a facility for current project-specific information about access, setup and teardown, staff, rooms, equipment, input and cue needs, storage, accessibility arrangements, emergency procedures, and payment or cancellation terms. An equipment list alone does not establish the project workflow.

Remote and compatibility tests

Remote collaboration can involve latency, asynchronous exchange, platform, compatibility, communication, and handoff constraints. The available evidence is limited and technology changes, so test the intended workflow rather than generalizing from a platform name. See the twenty-musician MR-DAW study and a practice-led study of cloud music production.

Using the same DAW name is not a complete compatibility test. Check actual versions, exchange format, newer features, external assets, plug-ins, included audio, and file-opening behavior. Apple explains how supported Logic assets can be consolidated into a project, while Avid documents version-specific Pro Tools interchange limits. Exact procedures vary by product.

Exchange a short, noncritical project fragment through the planned route. Confirm that the recipient can obtain it, open it, find the expected audio, identify the version, and return the agreed deliverable. Record the versions and test date.

Stage 3: Resolve consequential issues—or hold

Rights and contributor information

In the United States, a musical composition and a sound recording are separate works; registering one does not register the other. Authorship, ownership, registration, and licensing still depend on the facts and agreements. See U.S. Copyright Office Circular 56A.

If preexisting music is involved, identify what was used and how. A sample may implicate an existing sound recording and its underlying musical work, while an interpolation uses composition material without copying the earlier recorded audio. Permissions, statutory licensing, fair use, exceptions, and limitations are fact-specific. Unclear provenance should place sample-dependent work on hold for qualified legal review. See the Copyright Office introduction to sampling and interpolation.

For U.S. projects, a copyright ownership transfer—other than one occurring by operation of law—generally requires a writing signed by the rights owner or authorized agent. The statute does not itself decide whether a project term is a transfer, license, or something else. See 17 U.S.C. § 204.

U.S. work-made-for-hire status is limited to employee work within scope or qualifying commissioned categories meeting required conditions. A label in a music-services document is not enough to decide status. See Copyright Office Circular 30 and seek legal review where the outcome matters.

A split sheet can record stated information without resolving a dispute. The MLC’s U.S. template includes writer identities, identifiers, affiliations, publishers, percentages, contacts, signatures, and dates, but it does not adjudicate ownership or satisfy every organization or territory. See the MLC Song Split Sheet Toolkit.

Create a rights watchlist for each composition, recording, sample, interpolation, beat, loop, or other preexisting element. Record the claimed source, contributor, supporting documents, responsible reviewer, intended territory or use if known, and status. Do not infer permission or ownership from payment, possession of files, metadata, or a checklist.

Credits and metadata

Collect contributor and recording information while knowledgeable participants can verify it. Recording Academy guidance recommends tracking roles, samples, recording details, formats, owners, publishers, societies, and identifiers; the guidance is advisory and does not allocate ownership. See Credits and Recording Metadata.

DDEX RIN 2.1 can represent studio-event information including performers, roles, instruments, time, location, engineers, tracks, and mix components. RIN is licensed and machine-to-machine, not mandatory for every project. See the DDEX RIN introduction.

At minimum, record each contributor’s name, role, instrument or service, recording date and location, affected song or version, and any unverified ownership, publisher, society, or identifier fields.

Access, hearing, and voice

Ask participants how instructions, schedules, charts, cues, breaks, and approvals should be communicated. For U.S. entities covered by ADA Titles II or III, effective-communication obligations apply to people with communication disabilities, and an appropriate aid depends on the context and the person’s usual communication method. Coverage and implementation are fact-specific. See the U.S. Department of Justice effective-communication guidance.

NIOSH identifies musicians, engineers, producers, and other music workers as exposed to loud-sound risk. Its U.S. occupational-health recommendation is 85 dBA over eight hours, with recommended duration halved for each three-decibel increase. This is not a worldwide legal limit, and individual susceptibility and applicable law vary. Use actual measurements, facility procedures, current law, and an appropriate safety professional for project-specific controls. See NIOSH guidance for musicians and its noise-exposure explanation.

For voice care, NIDCD recommends hydration and vocal rest, avoiding voice use when hoarse or tired, and clinical consultation when a problem is suspected. This general guidance does not prove that every rested or hydrated performer will work better. See Taking Care of Your Voice.

Stop affected work and seek appropriate help when the team encounters a suspected health problem, unmet access need, unsafe exposure, unclear legal authority, or another consequential issue outside its competence.

Stage 4: Plan the session packet

The following template combines the minimum fields and the additional fields that become useful as risk increases. It is a planning aid, not a contract, rights determination, medical assessment, or safety certification.

PROJECT FRAME — minimum
Project and deliverable:
Current source-of-truth version:
Work in scope / out of scope:
Project lead:
Approver and approval route:
Target date:
Actual constraints and priorities:

SONG OR PRODUCTION MAP — minimum
Song / version:
Form, key, tempo, tuning, click status where relevant:
Performers, instruments, inputs, or remote contributions:
Approved decisions:
Decisions being tested:
Intentionally open decisions:
Dependencies or holds:

UNCERTAINTY REGISTER — minimum
Question:
Consequence if unresolved:
Test, document, or specialist needed:
Owner:
Deadline:
Affected version:
Evidence or result:
Status — open / testing / resolved / intentionally open / hold:

DECISION LOG — minimum
Question and alternatives:
Decision:
Approver:
Date:
Affected version:
Follow-up or reopening condition:

BUDGET AND SCHEDULE — when relevant
Quoted, estimated, committed, variable, and contingent items:
Access / setup / recording / breaks / teardown windows:
Cancellation, overtime, expense, and scope-change questions:
Session priorities if time or funds change:
Contingency owner and trigger:

CONTRIBUTOR BRIEF — when relevant
Name, role, contact, and communication needs:
Current demo, reference notes, chart, lyric, or guide:
Schedule, location, access, and equipment assumptions:
Deliverable, format, deadline, revisions, and approval route:
Unverified engagement, credit, confidentiality, or payment questions:

TECHNICAL ADVANCE — when relevant
Room, staff, equipment, inputs, monitoring, and cue assumptions:
DAW and software versions:
Exchange format and included assets:
Pilot or compatibility-test result:
Transfer route and confirmation method:
Emergency, accessibility, and facility questions:

RIGHTS WATCHLIST — when relevant
Element and source:
Claimed contributor or owner:
Supporting document or correspondence:
Intended use or territory if known:
Responsible reviewer:
Status — documented / disputed / specialist review / hold:

FILE AND RECOVERY PLAN — minimum
Source-of-truth file and naming convention:
Folder or hierarchy:
Included assets and expected exports:
Sender, recipient, delivery location, and confirmation:
Separate backup location and owner:
Restore-test method, date, and result:

READINESS RECORD — minimum
Overall status — go / hold / rework:
Evidence reviewed:
Approver and decision date:
For each hold or rework item — next action, owner, deadline, affected version:
Conditions that reopen the decision:

Choose a descriptive file hierarchy that distinguishes source material, recording files, exports, metadata, credits, mixes, stems, and later mastered material where relevant. The Recording Academy provides one adaptable hierarchy, not a mandatory universal structure.

Maintain separate project backups and test recovery according to project value, confidentiality, systems, and resources. Apple recommends periodic Logic project backups, while CISA recommends offline encrypted backups and availability or integrity testing for critical data in its ransomware guide. These examples do not prescribe one architecture for every music project.

Stage 5: Approve go, hold, or rework

The named approver assigns one outcome:

• Go: The documented work can proceed within the recorded assumptions. Remaining open choices are intentional, owned, and tolerable.
• Hold: A consequential dependency must be addressed before the affected work proceeds.
• Rework: A test changed the creative scope, budget, people, schedule, facility, or technical plan, so the affected plan must be revised and checked again.

These are Open Music Business planning labels, not legal determinations or certifications. A project may be go for rehearsal while sample-dependent recording remains on hold. A material change reopens the affected decision.

Every hold or rework record needs a next action, owner, deadline, and affected version. If those fields are missing, the project has identified a problem but has not yet made an actionable decision.

Worked example: Version B independent single

All scenario facts, dates, amounts, and durations in this example are invented and are not market rates, recommendations, deadlines, or predicted outcomes.

Inputs

A U.S.-based independent single starts with a $2,400 budget envelope and a 10-hour studio booking. The project has a $450 studio deposit and $250 pilot recorded as committed costs, plus estimated engineer and performer costs of $800 and $500. The packet also reserves a $300 contingency. The artist-producer is the approver.

The initial cost method is:

• committed costs: $450 + $250 = $700;
• estimated costs: $800 + $500 = $1,300;
• planned total: $700 + $1,300 + $300 = $2,300; and
• unallocated amount: $2,400 − $2,300 = $100.

The time plan deducts 1.5 hours for setup, 0.75 hour for breaks, 0.75 hour for teardown, and one hour of contingency:

10 hours − 1.5 hours − 0.75 hour − 0.75 hour − 1 hour = 6 usable recording hours.

The creative inputs are two voice-memo arrangements, Version A and Version B. The technical inputs include a remote contributor using a different DAW version. A sample is present, but its provenance and permission status have not been resolved.

Constraint

The creative test produces a clear result: Version B’s shorter intro is approved, while its ending texture remains intentionally open under the artist-producer’s approval. The remote contributor and engineer exchange a 30-second noncritical fragment. It opens, includes the expected audio, carries the agreed version name, and can be returned through the planned route, so that compatibility question is recorded as resolved for the tested versions and format.

The same test cycle introduces an additional performer costing $250 and requiring another 0.5 hour of setup. This changes both limiting conditions:

• revised cost: $700 + $800 + $500 + $300 + $250 = $2,550, which is $150 over the budget envelope; and
• revised usable time: 10 hours − 2 hours setup − 0.75 hour breaks − 0.75 hour teardown − 1 hour contingency = 5.5 hours.

Before: the plan cost $2,300, left $100 unallocated, and provided six usable hours. After: the added performer makes the plan cost $2,550, puts it $150 over budget, and reduces usable time to 5.5 hours. No rounding is needed. These calculations test only the disclosed scenario; they do not predict real project costs or session efficiency.

The unresolved sample creates a separate constraint. The team cannot use possession of the audio as proof of permission, so sample-dependent recording cannot be treated as ready.

Decision

The artist-producer, acting as approver, assigns Rework as the overall decision because the documented budget and scope can no longer proceed unchanged.

The approval decision also records scoped outcomes:

• Go: rehearsal of Version B without the disputed sample;
• Resolved: the remote exchange for the tested versions and format;
• Hold: sample-dependent recording pending provenance documentation and qualified U.S. legal review; and
• Rework: the added performer, budget, setup time, and session priorities.

The added performer is not silently accepted, and the sample question is not guessed away.

Output

The updated packet identifies Version B as the current arrangement, preserves the ending texture as intentionally open, records the remote test result, names the engineer as backup owner, and keeps the sample hold visible.

The budget-rework record contains:

• Next action: remove the added part, document an approved change to the budget envelope, or reprioritize the session;
• Owner: artist-producer;
• Deadline: August 5, 2026; and
• Affected version: Version B production map.

The rights-hold record contains:

• Next action: document provenance and obtain qualified legal review before sample-dependent recording;
• Owner: project lead;
• Deadline: August 12, 2026, or before the affected recording, whichever comes first; and
• Affected version: Version B sample-dependent recording plan.

This output is actionable because each non-go item has a status, next action, owner, deadline, and affected version.

Failure branch

Two conditions would allow the affected plan to be reconsidered: the budget or scope must be brought within an approved envelope, and the sample question must be resolved by an appropriately qualified reviewer. If either condition is not met, the packet changes instead of merely recording that failure is possible.

If no expanded budget is approved, the additional performer and 0.5-hour setup are removed from Version B. Planned cost returns from $2,550 to $2,300, the $100 unallocated amount returns, and usable recording time returns from 5.5 to 6 hours. If the sample is not cleared, the disputed material is removed from the rehearsal and recording agenda, the rights watchlist remains on hold, and only the sample-free Version B rehearsal retains go status. Any later budget authorization, scope change, or qualified rights conclusion reopens only the affected readiness record.

Visual callout — Version B readiness map: Show the Inputs ($2,400 envelope, $2,300 initial plan, six usable hours, Version B, tested remote exchange, and unresolved sample), the Constraint ($2,550 revised cost, $150 overage, 5.5 usable hours, and unresolved sample authority), the Decision (Approve assigns the outcomes), the Output (sample-free rehearsal goes, remote exchange is resolved, sample-dependent recording is held, and added-performer scope is reworked), and the Failure branch (without budget authorization or sample clearance, remove the added performer and disputed sample, restore the $2,300 plan and six usable hours, and proceed only with sample-free rehearsal). Approve is the decision node, with direct branches to Go, Hold, and Rework.

Text alternative for the visual: Version B begins with a $2,300 plan inside a $2,400 envelope and six usable hours. Testing adds a performer, moving the plan to $2,550 and 5.5 usable hours, while sample authority remains unresolved. The approver assigns go to sample-free rehearsal, hold to sample-dependent recording, and rework to the added-performer plan. If budget authorization and sample clearance do not occur, the added performer and disputed sample leave the plan, restoring the $2,300 cost and six usable hours.

Common failure modes and escalation points

• Do not require universal arrangement lock; distinguish approved, testing, intentionally open, and hold.
• Do not promise that a demo, rehearsal, or pilot will save a particular amount of time or money.
• Do not use a reference without naming the attribute and decision it informs.
• Do not copy rates or engagement structures across territories; check current applicable terms.
• Do not let a label decide ownership, permission, work-made-for-hire status, or worker classification.
• Do not assume compatible software; test the actual versions, features, assets, and exchange behavior.
• Do not confuse another project version with a separate, tested recovery plan.
• Do not leave credits and metadata until knowledgeable contributors are unavailable.
• Do not convert missed approvals or silence into consent.
• Do not treat access needs as late exceptions; ask about communication and participation during planning.
• Do not use a production checklist as a legal, medical, accessibility, or safety assessment.

Consult the relevant producer, engineer, studio, union, lawyer, accountant, accessibility specialist, safety professional, or health professional when a consequential issue falls outside the team’s competence. Place only the affected work on hold when the issue can be scoped safely.

Specialist Open Music Business handoffs

For writing and musical design:

• Songwriting Fundamentals — article ID songwriting-fundamentals.
• Demo Recording Tips — article ID demo-recording-tips.
• The Art of Arranging a Song — article ID arranging-a-song.
• Using Reference Tracks in Mixing — article ID reference-tracks.

For people and recording setup:

• Choosing the Right Producer — article ID choosing-a-producer.
• Home Studio Basics — article ID home-studio-basics.
• Working With Session Musicians — article ID working-with-session-musicians.

For the session and later handoffs:

• The Studio Session Workflow — article ID studio-session-workflow.
• Studio Session Etiquette — article ID studio-session-etiquette.
• Demo vs Final Mix: Knowing When to Stop — article ID demo-vs-final-mix.

A useful pre-production process does not eliminate discovery. It identifies which discoveries are welcome, which assumptions have been tested, which decisions control the plan, and which unresolved issues must not be guessed away.