Revisions are a normal part of game audio work. A director may ask for a darker tone, a designer may request a shorter loop, and a producer may want the theme slightly brighter after a review. The problem begins when these notes arrive in messages, calls, and marked-up builds, and nobody can say which version is current. A clear revision system protects your time and keeps every studio working from the same file.
Give every version a clear name
Use a consistent naming pattern for every track and export. A good name includes the project, the cue, the version number, and the date, for example a short code followed by the revision letter. Avoid names such as final or final2, because they quickly lose meaning. When a studio refers to a file by name, you should be able to find it immediately. Readers may also want to visit tvn24.
Store older versions rather than overwriting them. A studio may later decide that the first draft was better, and an archive lets you restore it in minutes. Keep the archive organised by project, and remove only files you are certain nobody needs.
Log feedback as it arrives
Every piece of feedback should go into a single log. Record who gave it, when, what they asked for, and which version it refers to. A simple table is enough. The log reveals patterns, such as one stakeholder who always asks for changes late, or a repeated request that suggests the original brief was unclear. You can also visit blog-buster.net for more reading.
Write feedback in the studio’s own words wherever possible. Paraphrasing can change the meaning, and a short quotation keeps the request precise. When a note is unclear, reply with a question and a suggested interpretation before you start the revision.
- Note the project, cue, and version number for each request.
- Record the person who asked and the date of the request.
- Mark whether the change is a fix, a preference, or new scope.
- Link each note to the file that it refers to.
Separate fixes from new ideas
Not every note deserves the same treatment. A fix corrects a problem, such as a clipping peak or a loop that does not repeat cleanly. A preference adjusts taste, such as a brighter instrument choice. New scope adds work that was not in the original agreement, such as an extra stinger for a feature that appeared late. Treat each category differently. Fixes are usually included, preferences may be included within limits, and new scope should be quoted separately.
Explain this distinction politely. Clients rarely object when they understand that added work has a cost, especially when you show the list of changes that were already completed under the original agreement.
Confirm approvals in writing
When a studio approves a version, ask for the approval in writing and note the file name in your records. A short message such as confirming the version as final for the current build protects both sides. Without written approval, you may find yourself revisiting a track months later because nobody remembers who signed off on what.
Keep the approval messages with the project files, and make sure the final export matches the approved version. Some studios update builds without telling the composer, so check the in-game result when you can. If you cannot test the implementation yourself, ask for a short clip or screen recording that confirms the music plays where it should.
For a related read on this site, see Explaining Renovation Noise to Young Children Without Scaring. Choose a template that records the version, the approver, and the date, and keep it open during every project. A shared log is especially useful when several people give feedback, because it shows what has already been agreed. Review the log before each milestone, and bring any open items to the next call so that nothing is left unresolved when the build is locked. Ask the studio to confirm the log entries in writing once a month, so that both sides remain aligned. Keeping the log tidy also makes it easier to answer questions from a future developer who inherits the project. For questions about contract wording or ownership of revisions, speak with a qualified professional.
A revision system is only useful if you use it every time. When each version has a name, each note has a record, and each approval is written down, your studio relationships become calmer and more predictable. Clients feel confident that you know exactly where every track stands, and you spend less time searching for files and more time making music.