All articles
ComplianceSeptember 24, 2026·3 min read

Compliance Essentials for Texting Trial Participants

Texting participants feels informal, which is exactly why sites get it wrong. Here's what IRBs, monitors, and privacy rules actually expect from your SMS outreach.

By Trialflow Team

Texting is now the default way most sites reach participants. It's also the channel where compliance gets sloppiest, because it feels informal. A text is a study communication with the same documentation, privacy, and IRB expectations as a phone call or letter. Here's what actually needs to be in place.

Get consent for the channel itself

There are two separate consents at play, and sites frequently conflate them.

Consent to contact by text. Under U.S. telemarketing rules, recruitment texts to someone who hasn't asked to hear from you are the risky category. Once a person has affirmatively given you their mobile number for study contact, you're on much firmer ground. Capture that permission explicitly — a checkbox on your web form, a documented verbal agreement logged in your CRM, or a signed pre-screening authorization. Record when and how it was given.

Consent to receive study information. Texting an enrolled participant about visit logistics is different from texting a prescreened lead about a new indication. Don't assume permission for one covers the other. If someone consented to contact about a diabetes study and you want to text them about a migraine trial, that's a new ask — unless your registry consent language covered future studies, which it should.

Always include opt-out language in the first message of any new thread, honor STOP immediately and automatically, and never re-add someone who opted out because a new coordinator found their number in an old spreadsheet.

Get the text approved

IRBs treat recruitment texts as recruitment materials. That means template messages sent to prospective participants need submission and approval, same as a flyer. Practical approach:

  • Submit a library of templates, not one-offs. Include your initial outreach, reminder, and re-engagement messages in a single submission.
  • Include placeholder syntax so the IRB sees exactly what varies: first name, site name, appointment time.
  • Keep operational messages separate. Appointment reminders for already-enrolled participants generally don't require the same review, but check your IRB's position in writing rather than assuming.

A short amendment cadence — batching template updates quarterly — beats submitting individually and waiting each time.

Mind what goes in the message body

Text content lands on a lock screen a spouse or coworker can read. Two rules:

  1. Don't name the condition in outbound messages unless the participant initiated the thread and the indication is already disclosed. "Following up on your interest in our research study" works. "Following up about your hepatitis C screening" does not.
  2. Don't request PHI over text. No lab values, no medication lists, no photos of symptoms. Move that to a phone call or a secure portal and document the handoff.

Keep records the monitor can see

SMS threads living on a coordinator's personal phone are a finding waiting to happen. You need:

  • A site-owned number or platform, never personal devices
  • Retention of all sent and received messages for the study record retention period
  • Timestamped logs tied to the participant record
  • Access that survives staff turnover

If a coordinator leaves and their texts leave with them, you cannot reconstruct participant communication history for an audit.

Write the SOP

One page covering: who may text, approved templates and where they live, opt-out handling, prohibited content, escalation to phone, and retention. Train to it, document the training, and re-review whenever you change platforms. Most texting findings come from having no written standard at all, not from a bad message.

Enrolling studies shouldn't be this hard

Trialflow gives research sites one platform for lead management, AI trial matching, and recruitment analytics.

Request a Demo