---
title: "How to evaluate ICH M11 protocol authoring software | Trelice"
description: "A buyer's checklist for ICH M11 protocol authoring software: questions for vendors, what to watch in a demo, and when a suite or Word fits better."
canonical_url: "https://www.trelice.com/resources/how-to-evaluate-m11-authoring-vendors"
---

Guide November 14, 2026 · 5 min read

# How to evaluate ICH M11 protocol authoring software

A buyer's checklist: the questions to ask every vendor, what to watch in a demo, and when a suite or a Word-based tool is the better choice.

By [Ilan Slonim](/about), Founder and CEO, Trelice. Published November 14, 2026.

Teams choosing protocol authoring software are usually weighing three options: staying in Word, adopting a structured authoring platform, or buying a suite where authoring is one module. This checklist is meant to help you compare them on the same terms. We make one of these tools, so read it with that in mind. The questions are the ones we would want a buyer to ask us.

## What should ICH M11 support actually mean?

ICH M11 has two working parts. The template sets the format and structure of the protocol. The technical specification sets the data elements and their technical attributes, so protocol content can be exchanged between systems. A tool can follow the first without the second, so ask each vendor which one it means.

Ask how the tool holds M11 content. Some tools hold fields. Others hold headings over free text. Both can produce a document that follows the template. They differ in what the system can check and re-use later.

Ask about versions. The M11 guideline says the template and technical specification are versioned documents that "may be revised, subject to a change control process." Ask which version the tool follows today, how a new version is rolled out, and what happens to protocols that are in progress when it arrives.

Ask to see the flexibility the standard allows. The template keeps its higher-level heading structure, while many lower-level sections can be added, removed, or modified. Have the vendor add a lower-level section in front of you.

## What questions should you ask every vendor?

Consistency. The same fact often appears in several protocol sections. Ask how the tool keeps those in agreement. The honest answers range from careful reading by a person to a system check that flags related sections when one changes.

Process. Ask where writer and reviewer assignment, due dates, approvals, and signatures live. If they live in email and calendars beside the tool, you are buying an editor, and that may be all you need.

Export. Reviewers outside the system will read the protocol in Word or PDF. Ask whether you can export a formatted document at any time, and whether old approved versions stay downloadable.

Derived documents. Consent forms, visit worksheets, and screening forms all depend on the protocol. Ask which of them the tool generates from the protocol and which you will still maintain by hand.

Data exchange. Ask whether the tool can produce a study definition in a standard format such as CDISC USDM, and whether that output is versioned with the protocol it came from.

AI. Ask exactly where the tool uses a language model, whether you can work without it, and who reviews what it writes. For our part, protocol authoring, review, and approval in Trelice are deterministic and do not run on a language model. AI is optional. It is used to import an existing document, to learn a house format, and to draft consent form sections and their translations, which are labeled as drafts and reviewed by a person.

Records and signatures. Ask each vendor what is validated today and what is planned, and ask to see the evidence. Ours is this: Trelice is architected to support 21 CFR Part 11 requirements. Validation is in progress.

## What should you watch in a demo?

Bring the same synopsis to each vendor, and ask to watch an amendment travel through the system. A first draft looks good in most tools. An amendment is where the differences between structured platforms and retrofitted templates show.

Pick a small, real change, such as moving one visit in the schedule of assessments. Then watch what happens. Is the reason for the change recorded? Does the amendment get its own approval chain? Is a summary of changes generated, or does someone write it afterward? Which derived documents rebuild, which show a warning, and which stay silent until a person notices?

Watch a reviewer as well as an author. Ask the vendor to request changes on a section, show that editing is locked during review, and open the audit trail entry for that decision.

## When is a suite the better choice?

In a suite, protocol authoring is one module of a wider eClinical platform. That is a reasonable choice if your organization wants one vendor for data capture, trial management, trial master file, and authoring, and values a single contract over depth in any one module.

We say this plainly on our own comparison page. Trelice is a focused authoring tool. It has no EDC, no CTMS, and no eTMF, and there is no plan to add them. Teams that want one vendor for everything will be happier elsewhere.

## When is a Word-based tool the better choice?

Word-based tools keep writers in the tool they already know. Some add structured content and templates inside Word. That can suit a writing group whose work covers many document types, where protocols are a small share of the total.

Plain Word can also be enough. If you write a few protocols a year with a stable team, a well-kept template mapped to the M11 table of contents may serve you.

Know the trade you are making. In Word the structure is headings, the content is free text, and the knowledge of what belongs where lives with the writer. When the protocol is amended, each derived document is brought back in line by hand, file by file.

## How should you make the final decision?

Demo more than one tool. Score the amendment, not the first draft. After each demo, write down what the vendor said is true today and what is planned, and ask them to confirm it in writing.

Our comparison page describes the wider landscape, including other structured authoring vendors as they describe themselves. If your bottleneck is the protocol and the documents that depend on it, we would be glad to be one of your demos. If it is somewhere else, the checklist above should still help you choose.

## Related on this site

-   [How Trelice compares](/compare)
-   [Protocol authoring on ICH M11](/protocol-authoring)
-   [Downstream documents](/downstream-documents)
-   [CDISC USDM support](/usdm)

## Sources

-   [EMA: ICH M11 Guideline on clinical electronic structured harmonised protocol (CeSHarP), Step 5 (PDF)](https://www.ema.europa.eu/en/documents/regulatory-procedural-guideline/ich-m11-guideline-clinical-electronic-structured-harmonised-protocol-cesharp-step-5_en.pdf)
-   [EMA: ICH M11 guideline, clinical study protocol template and technical specifications](https://www.ema.europa.eu/en/ich-m11-guideline-clinical-study-protocol-template-technical-specifications-scientific-guideline)
-   [TransCelerate BioPharma: Digital Data Flow initiative](https://www.transceleratebiopharmainc.com/initiatives/digital-data-flow/)

* * *

By Ilan Slonim

[← All resources](/resources)
