What Your Site Needs in Place Before Texting Participants

Texting is now the default channel for reaching trial participants, and most sites adopted it faster than they wrote policy for it. That gap is where monitors find problems. Here's what actually has to be in place.

Consent to text is separate from consent to participate

The informed consent form covers research participation. It does not, by itself, authorize electronic messaging to a personal mobile number. Under telephone consumer protection rules, you need express consent for automated or bulk texts to a cell phone — and that consent has to be documented, with a timestamp and the number it applies to.

Practical approach:

• Collect texting consent at first contact, before someone is even consented to a study. A pre-screening call is the natural place: "Is it okay if we text you about appointments and study updates at this number?"
• Record the answer in the CRM with date, time, and who asked.
• Include an opt-out instruction in the first message of any new thread. "Reply STOP to stop" is not decoration; it's the compliance backbone.
• Honor STOP immediately and permanently for that number, across every study. A participant who opts out of one trial's texts should not get texts from a different coordinator next month.

Treat message content as IRB material

Any text that promotes a study, describes it, or is designed to induce enrollment is recruitment material. It needs IRB review, same as a flyer. Appointment reminders and logistics for already-enrolled participants generally don't, but the line blurs fast — a reminder that adds "and ask us about our new diabetes study" just became an ad.

Submit your templates as a set. Sites that submit fifteen templated messages in one packet get approval once and then operate freely for months. Sites that write texts freehand end up with unreviewed recruitment language sitting in a monitor-accessible log.

Keep a template library

Build a small, approved library covering: screening follow-up, visit reminder, visit reschedule, lab or fasting prep, missed-visit outreach, and study-close notification. Coordinators should be composing free text only rarely, and never about study content.

Privacy: assume the phone isn't private

Text messages sit unencrypted on a device anyone can pick up. Two rules cover most of the risk:

1. Never put protected health information in an outbound text. No diagnoses, no lab values, no study name that reveals a condition. "Your appointment is Thursday at 9" is fine. "Your HIV study visit is Thursday" is not.
2. Never use the study drug or indication in the sender name or message body unless the participant has explicitly agreed to that and it's documented.

Participants will text you PHI back. That's their right, and you can't prevent it — but you can avoid escalating it. Respond by phone when the topic turns clinical.

Retention and the source document question

If a text exchange contains anything study-relevant — a reported symptom, a scheduling change that affects a visit window, a protocol question — it's part of the record. Decide now how those get captured. The workable answer for most sites is: texts live in a system that retains and exports them, and anything clinically meaningful gets summarized into a note to file or the participant's chart the same day.

Personal cell phones break all of this. Coordinators texting from their own numbers create records you cannot retain, audit, or transfer when they leave. Use site-owned numbers, full stop.

A short self-audit

Pull last month's texts and check: Was consent documented for every number? Does every recruitment message match an approved template? Any PHI in an outbound message? Any STOP requests still receiving texts? Any threads on a personal phone?

Most sites find one or two issues. Fixing them takes an afternoon. Explaining them to a monitor takes considerably longer.