Independent editorial coverage
Suvodav Agent is a plain-language resource on RTSM, IRT, and the clinical trial supply technology behind them — written for the operations teams who have to live with the platform after go-live.
Coverage built from published vendor documentation — not from a demo call.
Randomization and supply inside one system — and the reason the two jobs live together.
RTSM stands for randomization and trial supply management. The acronym is doing two jobs at once, which is why so many teams treat it as one purchase when it is really two tightly coupled ones. Randomization assigns a subject to a treatment arm under whatever scheme the protocol specifies, static or dynamic. Supply management decides which kit number that subject gets, whether the site has enough kits for the next enrollee, and when the depot needs to ship more.
The reason the two live in one system is that the kit allocation depends on the randomization result. Split them across vendors and every resupply decision becomes a handoff. That coupling is why RTSM replaced the older IRT label rather than sitting alongside it.
For a US clinical operations lead, the practical consequence is that an RTSM evaluation has to answer two different questions well. On the randomization side: does the system support the scheme the protocol actually needs, including dynamic allocation when the population is small or unevenly distributed across sites? On the supply side: does it hold the resupply logic the depots and sites will run against — threshold rules, pool assignment, and the kit expiry handling that a long study will eventually stress?
Depot bench
Kit allocation runs off the randomization result, so the shelf and the treatment list have to agree word for word.
You will still see IRT, IWRS, and IVRS in current contracts, job postings, and product names. IRT means interactive response technology, the umbrella term from the era when sites called a phone line or opened a web form to get an assignment. IWRS is the web version, IVRS the voice one. Nothing about the underlying work changed when vendors moved to RTSM as the preferred label — what changed is scope.
Modern systems pull in resupply algorithms, depot visibility, and emergency unblinding into the same interface. If a vendor quotes you an IWRS and an RTSM as separate line items, that is the place to ask a direct question: what does the second line add, and which of the two carries the kit allocation logic your protocol depends on?
Legacy term
IRT
Interactive response technology — the umbrella term that covered both randomization and kit assignment.
Legacy term
IWRS
The web implementation — sites signed in to a browser and pulled an assignment themselves.
Current term
RTSM
Randomization and trial supply management — the label in use now, and a wider scope than the terms it replaced.
Staging shelf
Where kit pools are held and where the resupply decision either works or exposes itself.
Frameworks name
Static randomization
A fixed list is prepared before enrolment; assignments are pulled from it in order.
Frameworks name
Dynamic randomization
The next assignment is recalculated against current imbalance — useful in small or scattered populations.
Framework
Resupply thresholds
The trigger that tells the depot a site is running low, and the logic that ships ahead of the next enrollee.
Framework
Emergency unblinding
A site-side path that works at 3 a.m. and does not require the sponsor's clinical lead to be awake.
Four names come up again and again in RTSM shortlists — each with a different shape of commitment.
Enterprise positioning through the Rave family
Appears in nearly every comparison guide, usually through the Rave family and its enterprise-scale positioning. Worth reading as a platform that carries broad trial infrastructure as much as an RTSM.
Modular, connected to Veeva EDC and eCOA
Presented as a modular option that connects with Veeva EDC and Veeva eCOA, with configurable supply algorithms and emergency unblinding described in the vendor's own materials. The narrower commitment is the point.
Built natively into the Viedoc eClinical suite
Built natively into the Viedoc eClinical suite, with static and dynamic randomization and real-time kit management. The pitch is that you avoid a separate IWRS login — one fewer credential, one fewer reconciliation hop.
Integrated eClinical aimed at unified trial operations
Takes a different route, positioning a fully integrated eClinical platform aimed at unifying trial operations rather than selling RTSM as a standalone module. You buy a support channel more than a product.
Feature matrices converge. The arguments do not. Three questions separate shortlists in practice, and none of them arrive in a standard scorecard.
Who configures the protocol — the study team or the vendor's build queue?
A system that lets the study team change randomization parameters without a ticket is a different operating model from one that routes every amendment through the vendor. Both are defensible; the phrase in a contract is not.
What happens to a live study when the protocol is amended?
Duration matters more than capability. Ask how long the system stays locked during a change, and whether new kit logic can be staged in parallel with the running study. A demo will show the change working; it will not show what the site does on the day.
Does the RTSM talk to EDC, eCOA, and eConsent without middleware?
This one matters more than it sounds. Every integration point is a place where a reconciliation report can disagree with the source data, and reconciliation disagreements consume study coordinator time in a way that never shows up in a demo.
The release condition
Randomization decides the arm; supply decides which kit number that subject receives. When the two lived in separate systems, every resupply decision was a handoff between vendors, and every handoff needed reconciliation. RTSM is the label the industry settled on because it names both jobs and puts them behind one interface: one randomization record, one kit allocation, one place a coordinator looks when a site gets an urgent assignment at an awkward hour. Suvoda Agent writes about that shift because it is the decision most teams are still working through.
Multinational trials
Language support moves from nice-to-have to a site activation blocker. Kit allocation rules have to account for depot locations, import timelines, and country-specific labeling. Emergency unblinding procedures need to work for a site eight time zones from the sponsor's clinical lead.
Country coverage claims in vendor materials deserve scrutiny: ask which countries are served by a local depot and which route through a regional hub. Our multinational trials page goes through the supply, language, and coverage questions in order.
We are not affiliated with any vendor on this site. We do not sell RTSM, resell licenses, or take referral fees for platform introductions.
Our vendor profiles are built from publicly available product documentation and vendor-published materials, and they say so. Where a vendor's marketing makes a claim we cannot verify from published sources, we note the gap rather than repeat the claim.
Our comparison page scores platforms on criteria that affect study delivery: build speed, amendment turnaround, interoperability, and operational fit for the study types you actually run. When we are wrong, we want to hear about it.
RTSM does not operate alone. Trial Interactive, for instance, positions a connected eClinical platform that covers study management from site identification through closeout, with site collaboration and remote monitoring in the same product.
That shape of offering appeals to sponsors who are tired of stitching point solutions together, though it also means the RTSM is one module inside a larger commercial relationship. Neither approach is wrong. What matters is that you know which one you are buying, because the swap cost later is very different.
A rare disease study with a small, geographically scattered population has almost nothing in common with a Phase III oncology trial running at forty sites across twelve countries. The first needs careful attention to resupply thresholds and site training on low enrolment volume. The second needs robust depot coordination, multi-language support, and a randomization scheme that holds up under scrutiny.
The same platform can serve both, but the configuration work, the validation burden, and the support arrangement will not look similar. Read the guide with your protocol open in the next tab.
Study shape
Small, scattered population
Resupply thresholds and site training carry more weight than raw randomisation throughput.
Study shape
Large multi-country trial
Depot coordination, multi-language support, and a randomisation scheme that holds up under scrutiny.
Read with
Your protocol open
Guide, comparison, and profiles are more useful when your own scheme is on the next tab.
Read with
Your study team in the room
Configuration work, validation burden, and support arrangement do not look similar across studies.
The RTSM deployment timeline often gets quoted in weeks and delivered in months. The startup steps are where that gap lives.
Specification review
The protocol's randomization and supply rules read back to the team before build.
Build and configuration
The system is set up to the specification; the queue length here decides the go-live date.
User acceptance testing
Scripted scenarios for randomization, resupply, unblinding, and the site-facing UI.
Vendor qualification
Sponsor-side review of the vendor's own quality documentation and change control.
Change control and go-live
The handover that puts the system live, with the change procedures still live behind it.
UAT on an RTSM is not a checkbox exercise: it needs scripted scenarios for randomization, resupply, unblinding, and the site-facing UI, run by people who will use the system. We wrote a page on this because it is the single most common source of schedule slippage we see discussed in public vendor forums and conference material.
Six months in, no one cares which platform won the feature matrix. They care whether the amendment that just landed can be configured without a change order, whether the resupply alerts fire before the site runs out of kits, and whether the reconciliation reports reconcile.
Those are the questions our editorial approach is built around. We look at long-term operational value, not launch-day impressions, because most of the cost of an RTSM decision arrives after the go-live email.
A coordinator's day
A quiet workstation, a release wall of pinned sheets, and one sealed carton on the corner of the desk. The RTSM decides most of what happens to that carton — and rarely in the week the vendor demoed it.
Suvodav Agent covers RTSM, IRT, IWRS, and the wider clinical technology stack that sits around them. The site is written for operations leads in the United States who need to make a platform decision and want the documentation read before the contract is signed. We name platforms because the decision is a comparison; we do not position ourselves as a vendor of any platform.
Where public vendor documentation and a vendor's own marketing disagree, we say which one we are reading. Where a claim cannot be traced to a published source, we record the gap. If a platform has moved since our last review, the correction note on that profile is the fastest way to fix the record — we would rather be corrected than quietly wrong.
Corrections from readers are the fastest way to keep the comparison pages honest.
Pick the page that matches your current decision. If you are still defining terms, the RTSM and IRT guide is the right entry. If you have a shortlist and need criteria, go to the comparison. If you are building the shortlist itself, start with the vendor profiles. If you are planning a go-live, read study startup first.
Still defining terms
The RTSM and IRT guide
Terminology, what the systems cover, and how to read vendor claims without a salesperson in the room.
Read the guideYou have a shortlist
The platform comparison
Evaluation criteria, including the ones vendors tend to leave off their own scorecards.
Compare platformsBuilding the shortlist
The vendor profiles
A short, factual read on each named platform, so you can decide who to call.
See the profilesPlanning a go-live
The study startup timeline
UAT, vendor qualification, and change control — the ordinary reasons a two-week quote becomes three months.
Plan startupAnd if something here is wrong, or a vendor has moved since we last reviewed it, our contact page is the fastest way to reach the editorial team.
No. We publish independent editorial coverage of RTSM, IRT, and clinical trial supply technology. We do not sell licenses, resell platforms, or take referral fees for vendor introductions. Named vendors on the site are covered from publicly available product documentation, and each profile says where the information came from.
RTSM is the current preferred label and stands for randomization and trial supply management. IRT means interactive response technology, the older umbrella term covering both functions. IWRS and IVRS are the web and voice implementations of IRT. In practice, the same randomization and kit allocation work sits behind all four acronyms, though current RTSM systems tend to include more supply and unblinding functionality than the older IWRS products did.
Sometimes, and the reason is worth understanding. Native integration removes one class of build work, the interface between two systems, along with the reconciliation that interface would have required. What it does not remove is UAT, vendor qualification, or the configuration work specific to your protocol. Viedoc RTSM is built natively into the Viedoc eClinical suite and Veeva RTSM connects with Veeva EDC and Veeva eCOA, so both make the integration argument. Whether the saving is real for your study depends on how much of your timeline was integration work to begin with.
Country coverage, depot coordination, and language support tend to decide more multinational RTSM outcomes than the randomization engine does. Ask specifically which countries are supported by a local depot versus a regional hub, how kit labeling changes per country, and how the system handles emergency unblinding when the site is far from the sponsor's clinical lead. Our multinational trials page walks through each of these in sequence.
Look at where the rest of your clinical data lives and how much you value swap cost. A modular RTSM like Veeva's gives you a narrower commitment. A platform like Almac Trial Coordinator or Trial Interactive trades that flexibility for one vendor relationship and one support channel. Neither is better in the abstract; the deciding factor is usually what you already run and how tolerant your organization is of multi-vendor coordination overhead.
Start where your decision is
The guide is the plain-language starting point; the comparison is where criteria get scored; the profiles are the short, factual read on each platform. If something on this site is out of date, the editorial team would rather hear about it than leave it standing.
Editorial office
Suvodav Agent
1201 Innovation Drive, Suite 300
Cambridge, MA 02142, USA
+1-617-555-0198
[email protected]
Monday to Friday, 9:00 AM – 6:00 PM
Independent coverage of RTSM, IRT, and clinical trial supply technology.
