Audience: All users (Sponsor, CRO, Site, and Contact Center staff)
Purpose: Understand how patients experience recruitment and referral in a Honey program setup compared to a standalone study.
TABLE OF CONTENTS
What does the patient experience?
From the patient’s point of view, participating in a program (multiple studies or cohorts grouped under a unified structure) feels the same as participating in a single study.
There is no visual or functional difference in the landing page, self-assessment process, or communication flow.
| Feature | What the patient sees |
| Landing page | One entry point, with no indication that multiple studies or cohorts are involved |
| Pre-screener | A single, user-friendly self-assessment form |
| Follow-up | Standard emails, texts, or phone calls from site or phone team |
| Language | All content is shown in the patient's selected locale/language |
| Consent experience | Unchanged: handled per study site process |
What happens behind the scenes
While the patient sees one unified experience, Honey is automatically:
- Routing them to the most appropriate study or cohort based on eligibility, geography, and program logic
- Avoiding duplicate outreach by ensuring the patient is not referred to multiple studies simultaneously
- Tracking and logging their referral to a specific study within the program, so site staff knows exactly which protocol they are supporting
This routing logic is invisible to the patient but ensures operational efficiency for sponsors and sites.
Summary
Even in a program with multiple cohorts or protocols, patients experience a single, seamless flow, just like with any standalone study.
Honey handles the complexity on the backend so patients have a straightforward, low-friction path from interest to referral.
Related articles
What's the experience for the site in a program?
What's the benefit of using a program?
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