I begin during the recording process. I invite the exec's "handler"
to the recording session to provide any guidance on clarity
or "redos." As we get to the end of the conversation, I make sure
there is an opportunity for those "redos" or clarifications. I also
ask if there is anything they have concerns about and might not want
in the final version. Then I edit to a "draft version" for review.
I stress in my communications to let me know if there is anything
they would like me to "take out." This way, when I "take out" those
snippets, there will be no surprises in what is left. I add intro,
music, and such and send it straight to the I.T. guy for posting.
Since I'm doing an internal corp. podcast, I don't have the contracts
like Todd, but I will remember his points as I think they are right
--- In email@example.com, "Wade Rockett" <wade@...> wrote:
> Hi, all. If you've ever produced podcasts for clients, where you
> a lot of raw audio and edit it down into one short episode, could
> please share how you handled the client review cycle?
> I'm envisioning sending them an episode and having them come back
> with, "Did John Smith mention how awesome Feature X of our product
> when you talked to him? What about Features Y and Z? Get that in
> there." or "We'd like to bring out the competitive angle of this
> more." (In this scenario there's no going back and getting another
> It seems like you'd always be in danger of burning through your
> budgeted hours this way. Not sure how best to head that off, though.
> Any ideas or advice?
> One suggestion was to give the client a transcript of the raw audio
> first, with the parts we intend to include highlighted.