Clinical trial supply release desk with sealed kit cartons and a bone-paper document folder under flat north-window daylight
Editorial provenance Published 2026 · Updated monthly

Someone has to read the vendor documentation closely.

Who writes the Suvodav Agent coverage

An independent editorial resource on RTSM, IRT, and clinical trial supply technology — written for US clinical operations teams, not for any platform vendor.

Released
What we publish

Four areas, one narrow field.

Our coverage focuses on four areas, and if a page would not help someone preparing for a vendor shortlist meeting, it does not belong on this site.

  1. 1. RTSM and IRT terminology

    The definitions, the release-condition logic, and what each acronym actually names when you meet it in a vendor deck or an eClinical glossary. This includes the shift from legacy IRT and IWRS language to RTSM, and why the terms stopped meaning the same thing.

  2. 2. Operational delivery criteria

    The criteria that decide whether a platform goes live on schedule — kit allocation rules, amendment turnaround, qualification steps, and the parts of implementation that slip quietly. We describe what to ask a vendor and what a plausible answer sounds like.

  3. 3. Vendors on RTSM shortlists

    Profile pages for products that come up regularly in publicly available RTSM comparison discussions and in vendor evaluation material. Each profile describes what the public product documentation supports, and where it stops short of a sales claim.

  4. 4. Study startup and multinational considerations

    The study-type and country-specific factors that shape go-live and supply planning, from oncology and CNS protocols through rare-disease and multi-country supply. This is the material that sits closest to the real decisions.

We write for clinical operations leads, clinical program managers, and supply chain leads evaluating platforms for oncology, CNS, rare disease, and multinational studies. The audience shapes the writing: short paragraphs, ruled criteria, and no sales enthusiasm.

Who is behind this site

A small team with a procurement research background.

The site is edited by a small independent team with a research background in clinical technology procurement. We are not a vendor, an agency, or a reseller. We publish platform coverage because the information available to buyers is mostly vendor-authored, and that makes it harder to compare than it should be.

We are not affiliated with any vendor named on the site, and we do not accept payment for inclusion in vendor profiles or comparison pages. Where our coverage names a vendor — including any RTSM or IRT product — it is because that vendor appears regularly in publicly available comparison discussions and vendor evaluation material, not because of a commercial relationship. If you are looking for a platform vendor, we are not one, and we will not pretend otherwise.

No affiliation

Not affiliated with any vendor we cover.

Editorial distance is what makes a comparison page worth reading. Vendor names appear because the products come up, not because of a relationship.

No paid placement

Nothing is bought onto this site.

No sponsorship, no referral fee for a vendor introduction, no paid inclusion in profiles, comparisons, or FAQ pages. The editorial team decides what appears.

Public sources only

Every profile is built from public documentation.

Vendor-published product material, release notes where they are public, and the vendor's own website. We describe what the documentation supports and note the gap when a claim outruns it.

Our editorial method

How a vendor page gets written.

Each vendor profile is built from publicly available product documentation and vendor-published materials. We read the material ourselves and describe what it says, not what a sales deck promises.

This is slower than summarising press releases and it produces a more useful page. Where a comparison point depends on study-specific factors we cannot know from outside, we describe the criteria and let the reader apply them.

  1. 01

    Read the public documentation, not the deck.

    Product docs, admin guides, public release notes where they exist, and the vendor's own website. If the material we can read does not describe the functionality, we do not describe it as fact.

  2. 02

    Note where the marketing runs ahead of the docs.

    Where a vendor's marketing claims functionality beyond what the public documentation supports, we note the gap rather than repeating the claim. That gap is often the most useful line on the page.

  3. 03

    Describe the criteria, not the verdict.

    Where an answer depends on protocol, randomisation scheme, kit rules, existing systems, or study types, we write down the criteria and leave the decision to the reader.

  4. 04

    Cite the vendor's position as the vendor's position.

    Where a vendor makes a claim about cost savings, go-live timelines, or study outcomes, we cite it as the vendor's position rather than ours — the evidence behind those claims is usually study-specific and rarely public.

  5. 05

    Initial the page before it ships.

    Every page is reviewed by the same editor who wrote it, and re-reviewed when the vendor makes a material change to their published scope. Nothing goes live on a single pass.

Conflict of interest and independence

Nothing on this site is for sale.

We do not sell RTSM licenses, resell platforms, or take referral fees for vendor introductions. We do not accept paid placement in vendor profiles, comparison pages, or FAQ content. When a vendor approaches us with new marketing material, we review it the same way we review anything else — which means we look for the documentation behind the claim. If we cannot verify it, we do not publish it as fact. The editorial team is the only party that decides what appears on the site.

Terminology we use Superseded term → current term
IRT RTSM Randomization and Trial Supply Management — the term vendors and sponsors use when the platform covers both randomisation and supply in one system.
IWRS RTSM (supply side) Interactive Web Response System — the supply management half of what used to be sold as a separate system. Where the guidance names supply management, this is the term.
IVRS IRVRS Interactive Voice Response System — still in use for sites without reliable internet, but now usually a module of a broader RTSM platform.
What we do not do

There is no numbered score, and no platform recommendation.

We do not provide legal, regulatory, or quality advice, and nothing on the site should be read as such. We do not recommend a specific platform for a specific study. We do not score vendors on a numbered scale, because the numbers depend on the study and the reader. And we do not publish claims about study outcomes, cost savings, or go-live timelines as universal facts — where a vendor makes that kind of claim, we cite it as the vendor's position rather than ours.

What we will do instead.

  • Describe the criteria that decide a platform choice for your study type and supply model.
  • Describe how each platform positions itself against those criteria, using its own public documentation.
  • Flag where vendor positioning and public documentation disagree, and leave the decision to you.
  • Route corrections, additions, and disagreements to the same editor who wrote the page.
Clinical trial freight staging apron at dusk with strapped shipment pallets and a lone worker walking away
How we update coverage

Coverage moves when the market moves.

Vendor positioning and product scope change, sometimes faster than annual review cycles would catch. We revisit vendor profiles when a vendor makes a material change to their published product scope, and we update the comparison criteria when the market's priorities shift.

We also act on corrections. When a reader sends us a factual correction with a source we can check, we review it and update the relevant page if warranted.

Next review: monthly cycle
Why the narrow focus

A narrow field, read carefully.

RTSM and clinical trial supply technology is a small enough field that general eClinical coverage tends to blur the distinctions that matter most to buyers. Randomization and supply management sit close enough together that generic descriptions often treat them as one thing, which they are not.

By staying narrow, we can spend space on the kit allocation rules, amendment turnaround, and qualification steps that decide whether a study goes live on time. Narrow coverage done carefully is more useful than broad coverage done by summarising vendor decks.

How to reach the editorial team.

Corrections, topic suggestions, and questions all go through the contact page and reach the same small team that writes the coverage. We read everything, though we cannot respond to every message.

Hours
Monday to Friday, 9:00 AM – 6:00 PM (ET)

Sending a correction? Include the page and, where possible, the source you are relying on. Suggesting a topic? Tell us what decision it would help you make — that context is what tells us whether a topic is worth a page.

Editorial questions we are asked
Is Suvodav Agent affiliated with any of the vendors named on the site?

No. We are not affiliated with any vendor we cover and we do not accept payment for inclusion. Vendor names appear because those products come up regularly in publicly available RTSM comparison discussions. Each profile is built from publicly available product documentation and vendor-published materials.

Do you accept payments or sponsorships?

No. We do not accept paid placement, sponsorship, or referral fees for vendor coverage. The editorial team decides what appears on the site and how vendors are described. When a vendor sends us marketing material, we review it the same way we review any public source: by looking for documentation behind the claims.

Can you recommend a platform for our specific study?

No, and you should be cautious about anyone who offers to do so without looking at your protocol. What we can do is describe the criteria that decide the answer and how each platform positions itself against them. The final decision depends on your randomization scheme, supply rules, existing systems, and the study types you run.

How do I report an error or suggest a topic?

Use the contact page. For corrections, include the page and, where possible, the source you are relying on. For topic suggestions, describe the decision the topic would help you make. That context tells us whether a topic fits the site's coverage and where it belongs in the existing structure.

Where the coverage goes next.

If you are preparing for a vendor shortlist meeting, the RTSM and IRT guide and the platform comparison are the two pages most readers start with. The vendor profiles follow from there.