A 30-Day Onboarding Plan for Coordinators Doing Recruitment

Most new coordinators get trained on the protocol and the EDC, then get handed a stack of referrals and told to start calling. Recruitment is treated as common sense. It isn't. It's a skill with its own judgment calls, and it's usually the first place a new hire's inexperience shows up in your enrollment numbers.

Here's a training structure that gets a new CRC productive on recruitment within their first few weeks without burning leads.

Week one: listen before you talk

Before a new coordinator makes a single outbound call, have them listen to real ones. If you record calls (with appropriate consent and policy in place), build a short library: a call that converted smoothly, a call where the caller was hesitant and the coordinator recovered, a call that ended in a clean "no thanks," and a call that went badly. Walk through each one together and name what happened.

Also have them sit in on two or three screening visits. Coordinators who have watched a screening visit pre-screen better, because they understand what they're actually setting up.

Week two: shadow, then reverse-shadow

Shadowing alone creates false confidence. Add reverse-shadowing: the new CRC runs the call while an experienced coordinator listens on mute and debriefs immediately after. Three or four of these, with feedback in the first five minutes while it's fresh, does more than a week of observation.

Give them the easier population first. New hires should start on inbound leads — people who raised their hand — not cold database outreach or complicated re-contact work.

Teach the decision points, not just the script

Scripts are necessary but they don't cover the moments that matter. Train explicitly on:

• When to stop pre-screening. If someone clearly fails a hard exclusion, don't walk the rest of the questionnaire. Say so kindly and ask if they'd like to stay on the list for future studies.
• How to handle "let me think about it." Not a no. The move is a specific follow-up time, confirmed out loud, plus a text.
• What goes in the note. A note that says "left voicemail" is useless. A note that says "LVM, works nights, said to call after 2pm" is a lead someone else can pick up.
• When to escalate. Medical questions, complaints, anything that sounds like an adverse event, anyone who seems confused about what a trial is.

Make the documentation standard explicit

Most recruitment data quality problems trace back to training, not laziness. Show new coordinators exactly how to log disposition codes and why. Walk through a feasibility report or an enrollment funnel with them so they can see how their field entries roll up into the numbers leadership uses to win studies. People document carefully when they understand who reads it.

Set volume expectations in writing

Vague expectations create anxiety and uneven output. Tell a new CRC what a reasonable day looks like at week two versus week eight — number of outreach attempts, expected contact rate, how many days a lead can sit untouched. Then review against it weekly for the first month or two.

Build in a thirty-day skills check

Pick three recent calls, three sets of notes, and one no-show follow-up the new coordinator handled. Review them together with the same rubric you used in week one. This surfaces drift early, and it tells the coordinator that recruitment quality is evaluated the same way data entry is.

The sites that onboard recruitment deliberately tend to see new coordinators carrying real enrollment load by their second month. The ones that don't spend the next year wondering why their lead-to-randomization rate depends on who answered the phone.