Organize voice-over pickup lines
A pickup round should explain what returned, why, and what later resolved it without rewriting the first session.
Freeze the request
Record the cue revision, prior selected take, reason, direction, and issue time. Display labels are useful context but are not authenticated identities or signatures.
Link the response
When a response arrives, review its cue and round outside the tool, then link an existing take. The previous selection remains visible in the round history.
Supersede instead of editing
If an issued request changes materially, create another round or explicit amendment. Do not make the issued packet appear to have always contained the new direction.
Worked example
The sample carries two rounds. P01, Opening clarity, asked for a cleaner final consonant on two lines, kept the warmth of the original selection as its direction, recorded the previous take and the response take for each item, and is resolved. P02, Path direction, asks for a calmer read of a route instruction on cue C042, was issued, and has no response take yet.
Look at what P01 preserves after the fact: which take was selected before the request, which take answered it, the reason, the direction, and the times the round was created, issued, returned and resolved. Six months later that is the difference between a defensible record and a memory.
Method
A pickup round freezes the request. It captures the cue revision, the previously selected take, the reason and the direction at issue time. When a response arrives you review it outside the tool and then link an existing take to the item, which leaves the previous selection visible in the round history rather than replacing it.
If an issued request changes materially, you create another round or an explicit amendment. The issued packet is never edited to look as though it always contained the new direction.
What this does not do
- Display labels for who requested or performed a pickup are user-entered, not authenticated.
- The tool does not send the request or receive the response; it records both.
- A resolved round is not approval of the response.
Do this in the app
Issue the round before the re-record, not after.
- Open station 06 Pickups and create the round with a real reason and direction.
- Issue it, then record the response take at station 04 and link it back to the round item.
- Leave unresolved rounds visible rather than closing them to tidy the view.
Open the local workspace at station 06 Pickups