Production workflow: templates, versioning, freeze and bounce.

Projects do not die from a lack of ideas: they die from missing templates, tracks named “Audio 4 copy 2”, versions saved over the good one and a computer running out of CPU halfway through a bar. A simple, consistent workflow can prevent that deterioration.

This guide describes that workflow in six pieces: a Production template, Organisation with clear Names, Versioning that deletes nothing, the choice between Freeze/flatten and Consolidate/bounce, the relationship with Resampling and CPU optimisation, and finally Backups and Collaboration through Stem exchange.

The workflow that prevents lost work

The principle organising everything is this: opening tomorrow’s project should take less effort than closing it today. Every workflow decision is a way of paying that bill in advance:

• Build the template once and save yourself the same adjustments on every track.
• Name things properly once, and the project reads clearly without opening tracks.
• Save versions in every session, and never depend on undo.
• Freeze or consolidate at the right moment, and the computer keeps up.
• Back up while working, rather than after losing something.

The rest of this guide gives the operational detail behind those five statements.

Production template: the template that saves half an hour

A Production template is not a project full of things: it is a project containing only what you always need. A useful template usually contains four blocks:

1. Reference tracks. A track with the reference master you use to compare level and spectrum and, where appropriate, a click or guide track.
2. Buses. Drum, bass, harmony and effects groups, with their reverb and delay sends already routed and named.
3. Default MIDI. An instrument loaded on a MIDI track with the correct channel, ready for the first hit to sound.
4. Project settings. Tempo, time signature, key, loop length and track colours, so the project starts with your rules.

Save it as your DAW’s startup template and open it instead of an empty project. The temptation to include everything—twenty instruments and ten effects—is a mistake: every element the template carries consumes CPU before you make a sound and delays the first note. Start with the minimum that saves repetition and add only what you have repeated three times.

Organisation and names: the convention that holds the project together

A project’s Organisation can be read in two places: track names and folder structure. Neither requires heroic discipline, just a fixed convention.

Track names. Number, function and variation where applicable: 01_kick, 02_sub, 03_saw_lead_A. Avoid arbitrary capitals, trailing spaces and descriptions such as “new” or “final2”. If a track changes function, rename it then; the minute it takes costs far less than reading twenty generic tracks halfway through a mix.

Folder structure. A project folder containing Audio/, Renders/, Backups/ and, if you collaborate, Stems/. Within Audio/, use subfolders by type (drums, bass, fx) or origin. The rule that prevents red channels is to copy the project’s samples into the project, rather than reference scattered folders.

Library management, with tags and playlists that work for projects as well as DJ collections, is developed in Organise your library with playlists, tags and metadata.

Versioning: v1, v2, dates and why nothing gets deleted

Versioning answers a specific question: can I go back to how it was yesterday? Saving over the file does not allow that; saving a version does.

• Name format: tema_v01, tema_v02… with a date in the folder or name, tema_v03_2026-09-30.
• When to create a version: at the end of every session that adds something, and always before a destructive change (consolidating, deleting groups, changing templates).
• When not to: every five minutes. Generating forty versions per session will not create order; one or two per session is a sustainable pace.

Many DAWs have their own incremental or version saving: FL Studio, for example, documents saving a new version as a route to sequential backups and distinguishes the .flp, which does not include samples, from the .zip package, which does include the audio used. Using those functions is better than inventing a parallel folder.

Resist the temptation to delete old versions to save space: audio takes up little space compared with the cost of reconstructing a discarded idea you wanted to recover.

Freeze/flatten and Consolidate/bounce

This is where the workflow meets the CPU, and where most confusion occurs because each DAW uses different names for similar ideas.

Freeze/flatten operates at track level. Freezing makes the DAW temporarily record the track with its effects and play that audio instead of recalculating it: the track remains editable, but without using CPU. Flatten goes one step further and permanently replaces the track with that audio, losing the original chain. Freeze while exploring; flatten only when you are sure.

Consolidate/bounce operates at section or clip level. Consolidating joins audio fragments into a new file within the same track; bounce, or pasting in place, converts a MIDI section with its effects into audio. These finish an edit: once the passage is right, stop recalculating it on every playback.

One question settles the choice: do I still want to edit the chain? If yes, freeze. If no, consolidate or flatten. And a warning: save a version before a destructive change. Irreversible operations and versioning go hand in hand.

Resampling and CPU optimisation

Resampling means re-recording the output of a bus or the master onto a new track, then working on that audio again. It is not primarily a CPU measure: it is a design technique. It freezes decisions, forces commitment to the sound already obtained and lets you process something that can no longer be reproduced (feedback effects, self-modifying chains). As a precaution, record at the project’s sample rate and bit depth and check the level before re-recording: anything clipped there stays clipped.

CPU optimisation is the set of levers that keep a project alive:

• Measure before changing anything. The CPU meter and per-track load indicators show which track is demanding; without that reading, you turn off plugins at random.
• Turn off what is not playing. Disabling instruments and effects on silent tracks is usually the quickest lever.
• Adjust the buffer to the task. Low for recording and playing, high for mixing; the reasoning is in Install a DAW: drivers, audio device, buffer and sample rate.
• Freeze rather than struggle. If a pad track with three synthesizers uses half the CPU, freeze it.
• Avoid doing the work twice. Converting sample rates or opening projects at a rate different from the interface’s adds unnecessary computation.

Backups, Collaboration and Stem exchange

Backups. Apply the 3-2-1 rule to projects: three copies, two different media and one away from the equipment. The local project version counts as a copy, but not a backup if it lives on the same drive. Combine saving versions with an automatic copy on an external drive and another in the cloud; the full procedure, also applied to libraries, is in Backups with the 3-2-1 rule.

Collaboration. Before sending anything, decide what to share:

• Native project: only open it if the collaborator can load your plugins. If they use another DAW or lack your libraries, the project will arrive with gaps.
• Stems: export each group to separate tracks, without mastering, at the project’s sample rate and bit depth, using the names you have already defined and a reference mix so the goal is clear.
• MIDI and audio together: send MIDI for editable tracks and audio for those whose sound is already designed, letting the other person correct notes without breaking the sound.

Good Stem exchange follows three rules: the same sample rate in every file, unclipped levels with headroom, and a notes file containing tempo, key and each stem’s contents. If the collaborator needs your plugins, return to format compatibility in Plugin formats to understand what they can and cannot open.

Next step

The production workflow is in place; what remains is to keep it going with projects in project folders and their copies on three media. The concrete next step is to apply the 3-2-1 rule to everything you have built: Backups and safety copies with the 3-2-1 rule.