Published by PitchChanger · Updated · How these guides are made
How to use this workflow
Freeze the version being reviewed
Send an identifiable file and avoid replacing it under the same link without a new revision label. State the requested use: private rehearsal, editing reference or another agreed purpose. Ask the reviewer to confirm the actual version they opened before recording the decision.
Ask for a decision and preserve exceptions
Give each issue a short identifier and a location in that revision. Ask whether it blocks the named use, is accepted for that use or still needs review. Record the reviewer’s actual response and date. Do not infer acceptance from a download, a read receipt or a lack of feedback.
An original approval register with four states
The following fictional register illustrates decision states; no person has reviewed or approved these files. A practice file has a minor residual vocal in one passage and a missing ending in another revision. Those issues have different consequences, so a single “sounds good” checkbox would lose the reason for the decision.
The decision belongs to the named use. Accepting residue for learning an entrance does not approve the same file for public release. Record who may decide each requirement within the collaboration and escalate an unclear response rather than silently expanding its scope.
Swipe or scroll sideways to read all columns.
| Revision and use | Issue | Illustrative state | Meaning |
|---|---|---|---|
| r01 / rehearsal | Residual backing voice at 00:32 | Conditional example | Accepted only for private entrance practice |
| r02 / complete rehearsal | Final chord missing | Needs revision example | Ending must be restored |
| r03 / rehearsal | Checked named issues resolved | Approved example | Only if reviewer actually confirms |
| r04 / any use | No response received | Not reviewed | Follow up; no inferred approval |
Keep an issue open until the replacement is checked
Give the missing ending an ID such as END-01. The editor may mark it “changed in r03,” but the reviewer should separately mark it “verified resolved in r03” after hearing the saved file. These are two different events. Preserve the original location and add a new location if timing has changed.
A useful proposed record reads: “END-01, reported on r02, required full final chord. Editor reports restoration in r03; reviewer confirmation pending.” Do not substitute this sentence for a real observation. If the reviewer approves while another issue remains, retain the issue and its accepted limitation beside the approval rather than deleting it from the log.
Separate technical checks from the approval decision
An export can meet the required encoding settings while failing the musical task, for example by omitting a count-in the player needs. Conversely, a musician can like a rehearsal mix without having checked a required channel layout. Keep the factual export checks and the reviewer’s listening decision as separate fields.
Use the existing specification worksheet for format, rate, channel and filename checks. Use this approval register to capture the recipient’s decision after those checks and the listening review. PitchChanger does not collect signatures, manage approvals or send review messages; maintain this record in your own notes or collaboration system. If a new revision changes the approved audio, ask for the relevant review again.
Common questions
Is silence from the reviewer approval?
Do not infer that in this workflow. Record not reviewed and obtain an explicit decision through the collaboration’s agreed process.
Does rehearsal approval cover publication?
Only if the reviewer explicitly approved that use and the other necessary requirements are satisfied. Keep the intended use and limitations attached to the exact revision.