Day One Onboarding

What's a Surge scribe?

• Preservation of FMZ stats & EP
• Potential to move to full scribe
• Flipping Between FMZ and VFMZ

What's a CSL?

• Find us on PSI under Custom Management section.

Introduction to VFMZ

• Use your FMZ creds
• Logged in vs docking a job
• Changes that you see when you get a job docked: spell check, mark complete, close docking
• Report Broken Video
• Playback Gap
• Help line
• Download Local Media on F8 tab
• F11/F12 changes font size in text window
• Use CTRL instead of ALT + a letter key for shortcuts (Ctrl+Shift+Up to capitalize a word)

Keys to Custom Jobs:

• Due dates & Scheduling
• Auto forfeit
• My Schedule Page
• Job Requirements/Reference Sheet
• Sample Docking a Job
• Macros don't cross-contaminate from VFMZ > FMZ, but they do go from FMZ > VFMZ

Surge Scribe Standards

• Go through each heading and briefly explain
• They will need to copy/paste this into their browser from Job Reqs. section

Watch Videos ~25 minutes

- Paste all into chat

https://www.ctscribes.com/cosa/video/DocsandInfo.mp4
https://www.ctscribes.com/cosa/video/RSes.mp4
https://www.ctscribes.com/cosa/video/Markers.mp4
https://www.ctscribes.com/cosa/video/Research.mp4
https://www.ctscribes.com/cosa/video/AdvMacros2.mp4

Assign Mock Jobs

• Preview script of mock job
• Use the above to link to navigate to the given processed files. Allow a lookback of a few weeks in CTS if there hasn't been a mock circulated in a while. First, recycle the shortest job to each scribe and have ready to go for after Orientation. Once those jobs are docked, the remaining mocks can start to be assigned. Be sure to assign each job to EACH new scribe separately. Recycles are naturally "due" the following day they are assigned, so check scribes' schedules to avoid any jobs being forfeited. Adjust "due" dates if need be to match up with scribe schedules.
• When QAing the jobs, I tend to be extra lenient and really only correct a small handful of "major" things. Keep in mind these are the first jobs they are getting back, and we don't want them instantly feel swamped with corrections to address. The jobs are very easy, and these scribes are very good. Henceforth, The mocks are usually pretty good quality. I'll address an accuracy or a spelling or any other issue and relate it back to things we talked about that day. I will be extra explanatory in comments when doing so. Do what is possible to extend the "no pressure" vibe into the first few instances of QAing within reason. Once those corrections are made, the "answer key" for that job should be pasted in so the scribes get a near perfect consistent job back to review.
• No discretionary line breaks in paragraph format

Preview of Day Two Onboard

• Reminder to always check Custom first

Wrap Up

• Q&A Session
• Give offline

Day Two Onboarding

• Remind that they will get these three jobs back fully QAed, so this is just a quick review.

Review Mock Jobs

• Focus on speaker ID
• Key spellings in MW
• Use of Google to confirm name spelling
• Proper nouns and special content
• Bookmarks

Buzzr Jobs

• Explanation of what they are
• Sound markers

Suggested Macros:
(music) - mscp
(foreign) - ffip
(buzzer) - bzp
(ding) - dinp
(clock ticking) - cltp
(applause) - aplp
(chatter) - chhp

• Reminder that RS can offer further detail than Job Reqs section
• Speaker IDs dash no space
• Handling multiple speakers
• Stutters/Fillers
• Links to Job Traits
• Double dash vs ellipses

Wrap Up

• Assign three Buzzr jobs to each scribe
• Open for Q&A