SECTION ONE: PROCESS OVERVIEW
TITLE: What are you calling this process?
> Transcript checklist
SUMMARY: A one-sentence description of the process.
> Bi-weekly newsletter with an overview of forum activity, to provide updates to our clients, going out every other Saturday.
WHY: Briefly explain why the process is important.
> Since the forum is growing bigger and bigger, it is really easy to miss something that is important for them. This brief overview helps others to go through the most important topics that were discussed over the last 2 weeks.
INTERVAL: How often does this process need to be complete?
> Every other Thursday (as it is checked and polished for grammar by Maria overnight and then final check on Friday by Tomas or Andrew)
SECTION TWO: PROCESS EXECUTION
STEP #1
Set font for document to Calibri 12 (header is Calibri size 16)
STEP #2
Copy the header and footer from an existing transcript and add to the new transcript and that the footer has a disclaimer
STEP #3
Make sure there is a descriptive title at the top:
STEP #4
Make sure that the names of the presenter/host are included as sometimes transcribers will just put Interviewer/Interviewee, so they will need to be replaced with the actual name. Also, make them bold.
Use just first name (e.g. Andrew instead of Andrew Swanscott).
STEP #5
Check for any indications that some of the audio couldn’t be transcribed, for example transcribers will often put [Unintelligible 5:25].
STEP #6
Make sure there are not timestamps in the transcript.
STEP #7
Check the transcript is accurate by comparing to the audio/video.
STEP #8
Paragraphs should be separated by extra line
STEP #9
Once all is complete, save as a pdf file and rename it to an appropriate name, ready for upload to AWS.
SECTION THREE: REPORTING
WHO: Who should be the outcome sent to?
>
WHAT: What are you expecting to see in the outcome?
>
WHEN: When does the person reviewing the outcome want it?
>
HOW: How should the outcome be delivered?
>
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article