What's in a (file) name? Protection from screw-ups!
Please forgive the following rant about file naming. Better now than at crunch time, after dozens of tiny edits have been made to the wrong version of the script.
Workshops can move around in an agenda, so skip WS1, WS2 and use the topic instead: e.g., ObjHandling.
The writer's first draft for internal review is D1V1. Reviewers append their initials as they pass it along: ObjHandling_D1V1_dh becomes ObjHandling_D1V1_dh_mk, and so on through ObjHandling_D1V1_dh_mk_rp_sn_tr_cp.
After incorporating internal revisions to V1, the writer submits D1V2 for internal review.
Writers should start a new email thread at this point with a new subject header. That keeps D1V2 from getting buried between multiple replies to a thread named, "RE: FW: RE: Objection Handling 1st draft."
Repeat the above for D1V3 and D1V4 through - God help us - D1V12.
When the file goes to the client, delete the version number. ObjHandling_D1V12_dh_mk becomes ObjHandling_D1. No need for them to see how many attempts and hand-offs it took to get it right. Preserve the mystery.
When the client's comments come back, begin again with D2V1 ....
Lively Writing, on Time and on Target
When your message needs to engage and persuade, be sure to approach it from the Write Angle. Udi Shorr writes marketing and sales-training presentations for live audiences, video, print, and the Web. You benefit from years of marketing experience with Fortune 500 clients.