Protocol development has long produced a document that is reviewed, approved and then interpreted again by every delivery function. ICH M11 introduces a harmonised structure, template and technical specification intended to support electronic exchange of protocol information.
The guidance does not turn every protocol into software. It does establish a clearer basis for treating protocol content as information that can be structured, transferred and reused across systems and organisations.
Meaning is carried through defined content and data fields, not layout alone.
Teams need to agree how approved protocol information is checked before it is reused in study requirements and systems.
A common structure improves exchange. It does not replace clinical judgement or quality oversight.
01
M11 is more than a new protocol template.
The final FDA guidance describes persistent variability in protocol structure and content as a source of inefficiency in search, review and assessment. M11 addresses that problem through a common protocol structure supported by a technical specification.
Its design principles include a common set of core content, electronic exchange, content reuse and an open data model. Together, those principles shift attention from how a protocol page looks to how protocol information is represented and understood.
Structured information can keep its meaning as it moves between teams and systems.
02
The benefits matter when teams prepare the study.
A structured protocol is valuable when its meaning can reach the people and systems preparing the study. Eligibility criteria affect recruitment assumptions. Visit schedules affect site capacity and participant burden. Endpoint choices affect data capture, technology and oversight.
If teams have to recreate these links by hand after approval, a structured protocol will still leave work disconnected.
03
What sponsors and CROs should prepare now.
Agree who develops and reviews each study element, and how its meaning will carry into downstream use.
Keep the evidence, assumptions and authority behind a decision connected to the content it shaped.
Make the consequences for sites, participants, vendors and systems visible before delivery begins.
Structure should make review easier while showing who made or approved each decision.
04
What M11 does not claim.
The FDA guidance is nonbinding and allows alternative approaches when they satisfy applicable requirements. It does not prescribe how organisations must develop or maintain every protocol, and using the template or technical specification does not by itself establish trial quality.
Those boundaries matter. A structured protocol is an information foundation, not proof that the right decisions were made or carried out well.
05
The Tenvia view.
For an assessment, structure can describe what is collected and when. The study team also needs to understand why that frequency was chosen, what supports it and which assumptions still need review. Tenvia’s approach keeps those questions beside the design.
ICH M11 is a reference for organising Tenvia’s study information. CDISC USDM is a complementary structured study-definition exchange. The same governed design may have both a protocol document view and a data representation, with exact versions, terminology, unsupported elements and mappings examined separately. Neither standard establishes a ready-made EDC configuration.
This does not mean that an M11 or USDM export has been tested or compliance verified. Keeping the reasons behind decisions is part of Tenvia’s approach. It is not a regulatory requirement or endorsement.
Explore structured protocol developmentChecked 24 September 2026
M11 Clinical Electronic Structured Harmonised Protocol, May 2026
FDA guidance for industry, May 2026, adopting the ICH M11 guideline
FDA publication, May 2026; ICH template adopted 19 November 2025
FDA publication, May 2026; ICH specification adopted 19 November 2025
Structured study-definition exchange; pin exact versions and conformance for an implementation