Platform
Clinical research site operations, connected from protocol to visit.
ResFlow turns configured protocol schedules into participant timelines, clinic bookings and daily actions for research sites. Sponsors and monitors remain connected stakeholders with controlled oversight where authorised.
Book a 30-minute walkthroughStudy configuration
- Operational problem
- Protocol schedules live in documents while clinic work lives somewhere else.
- What ResFlow does
- Sites configure screening periods, anchor events, visit types, target days and permitted windows for each study.
- What it does not replace
- ResFlow does not replace the sponsor protocol document, EDC build or regulatory submission systems.
Protocol milestone visits
Visit 3
Target 6 Jul
Tele Visit 6
Target 3 Aug
Visit 4
Target 31 Aug
EOS
Target 14 Dec
Protocol visit schedule
Milestone visits with targets and windows ready for participant timelines.
Product interface shown with fictional data
Participant progress
- Operational problem
- Screening, eligibility and randomisation status are hard to see beside the next booking.
- What ResFlow does
- Participant profiles bring together status, milestones and upcoming operational steps in one place.
- What it does not replace
- ResFlow is not an eCRF or source-data system for clinical findings.
RF-1088
Northbridge Sleep Study · Screening attempt 1
Next visit
Visit 4 · target 18 Aug
Window
16 Aug – 20 Aug
Booking
Not booked
Coordinator
A. Patel
Participant profile
Fictional participant RF-1088 with status and next visit context.
Product interface shown with fictional data
Visit-window generation
- Operational problem
- Calculating windows manually for every randomised participant is slow and error-prone.
- What ResFlow does
- After configured anchor events such as randomisation, ResFlow generates target dates and windows for protocol visits.
- What it does not replace
- Windows are only as accurate as the protocol rules the site configures.
Protocol milestone visits
Visit 3
Target 6 Jul
Tele Visit 6
Target 3 Aug
Visit 4
Target 31 Aug
EOS
Target 14 Dec
Operational timeline
Completed, scheduled and not-due visits shown with fictional data.
Product interface shown with fictional data
Booking management
- Operational problem
- Clinic diaries become disconnected from protocol visit status.
- What ResFlow does
- Appointments can be linked directly to protocol visits so booking and study progress stay connected.
- What it does not replace
- ResFlow is not a full hospital EPR or generic consumer scheduling marketplace.
Clinic bookings
Visit, participant identifier and booking status in a compact tracker view.
Product interface shown with fictional data
Daily operational views
- Operational problem
- Teams discover overdue work only after checking several lists.
- What ResFlow does
- Site dashboards and due views surface appointments today, visits due soon and outstanding actions.
- What it does not replace
- ResFlow does not claim automatic regulatory compliance reporting.
Active studies
4
Appointments today
7
Visits due soon
3
Today’s clinic list
- RF-1042 · Visit 3Booked
- RF-1088 · Tele VisitDue soon
- RF-1101 · Randomisation09:30
Site dashboard
Active studies and today’s clinic list with fictional identifiers.
Product interface shown with fictional data
Site team roles
- Operational problem
- Shared spreadsheets cannot enforce who may edit protocol or team settings.
- What ResFlow does
- Organisation membership and role-based permissions control who can manage studies, bookings and team access.
- What it does not replace
- ResFlow is not a full HR or identity-provider platform.
Site team
Team roles
Account admin, coordinator, investigator and monitor examples.
Product interface shown with fictional data
Monitor workspace and redaction
- Operational problem
- Monitors need oversight without receiving unnecessary participant identifiers.
- What ResFlow does
- Authorised monitors can receive limited study visibility while participant-identifiable fields are redacted automatically.
- What it does not replace
- Monitor access does not grant write access to site operational records.
Study oversight (PII redacted)
Monitor view
Operational status with participant contact details restricted.
Product interface shown with fictional data
Audit history
- Operational problem
- Sites need accountability for who changed participant, booking or protocol records.
- What ResFlow does
- Meaningful operational changes are written to an append-only audit trail with user, timestamp and organisation context.
- What it does not replace
- The audit trail is an operational accountability aid, not a substitute for sponsor TMF requirements.
Site team
Accountable site operations
Team access is part of the same controlled workspace that produces audit history.
Product interface shown with fictional data
Participant import is available for bringing existing lists into a study. Selected operational exports (such as study logs and position tracker data) are also available. Protocol amendment workflows beyond study configuration updates should be confirmed during onboarding for your site’s needs.
Discuss your workflow