On May 22, 2026, FDA published its final guidance adopting ICH M11 — the Clinical Electronic Structured Harmonised Protocol, or CeSHarP — five months after the ICH Assembly adopted the guideline, template, and technical specification at Step 4 on November 19, 2025. Most sponsors reading the announcement will see a new protocol template and file it under formatting. That undersells what M11 actually asks for: a protocol whose sections, data fields, and terminology are structured well enough to move between systems without being retyped.
What ICH M11 actually finalized
M11 is not a single document. The ICH Assembly's November 19, 2025 Step 4 package bundled a guideline explaining the rationale, the CeSHarP template itself, and a technical specification most sponsors will not read before deciding to adopt it. FDA's final guidance folds together two rounds of prior draft guidance — the original CeSHarP draft from December 2022 (87 FR 78696) and the technical specification and template draft from June 2025 (90 FR 24146) — into one package, exactly five months after the international text reached Step 4. Every ICH member authority then implements the harmonized text on its own timeline (Step 5); EMA has published the same three documents as a scientific guideline, and neither agency has attached a mandatory-use date. Reconciling that timeline with your own eCTD publishing calendar is the first practical question, not the last.
The template's structure is fixed, and that is the point
CeSHarP is not a suggested outline. Trial design sits in Section 4 every time; the start and end of the trial is always Section 4.4; inclusion and exclusion criteria live in Sections 5.4 and 5.5; stopping rules are Section 7.4. That rigidity is deliberate — it is what lets a reviewer, an IRB, or a partner's system find the same information in the same place across every CeSHarP-formatted protocol, and it is what the technical specification's machine-readable layer depends on. A protocol that keeps its legacy numbering and simply borrows CeSHarP's cover page has not adopted M11; it has renamed a document.
- Section 4 is trial design, full stop. Objectives, endpoints, and estimands belong in the synopsis ahead of it — the template puts the synopsis, schema, and schedule of activities near the front precisely because that is what a site or reviewer opens first.
- Eligibility criteria split across 5.4 and 5.5. Each criterion has to resolve to a yes/no answer with a defined data source — a specific lab value, a named diagnostic code — not a paragraph of clinical judgment.
- Stopping rules are Section 7.4, not buried in a safety appendix. Reviewers and DSMBs know where to look without a document map.
- Every data element carries conformance and cardinality. The technical specification defines whether a field is required or optional and how many times it can repeat — the part legacy word-processor templates have no equivalent for.
A CeSHarP-formatted cover page on a legacy protocol is not what ICH M11 asked for. The technical specification's conformance and cardinality rules are the actual deliverable — the section numbers are just where they live. Why the mapping work comes first
Why voluntary doesn't mean optional for long
Nothing forces a sponsor to use CeSHarP on its next protocol. FDA's guidance carries the standard nonbinding language, and EMA has published the guideline without a compliance date attached. But a harmonized template that regulators, IRBs, and increasingly CROs are building tooling around rarely stays optional for a decade — ICH's own common technical document went from voluntary to the default within a few submission cycles after adoption. The sponsors best positioned when a region eventually tightens expectations will be the ones who piloted CeSHarP on a low-stakes protocol first, not the ones reverse-engineering a decade of legacy templates against a deadline. That is a regulatory submissions planning question as much as a medical-writing one, and it belongs on the same roadmap as your IND application strategy, not bolted on afterward.
- Confirm your authoring and eTMF tooling can emit the technical specification's structured data — conformance, cardinality, coded terminology — not just a document that looks like the template.
- Remap one legacy protocol section by section against the fixed numbering (4, 4.4, 5.4/5.5, 7.4) before amending a live study, to find where your content doesn't fit cleanly.
- Pilot on a new protocol or a major amendment, not mid-stream on an active trial where a structural rewrite adds risk for no regulatory benefit.
- Track FDA and EMA implementation separately. Step 5 adoption timing, and any future compliance date, is set by each authority on its own schedule.
None of this requires an enterprise system overhaul on day one. It requires treating M11 as a data-structure decision that happens to ship with a template attached, and testing that decision on a protocol where getting the mapping wrong costs a redline, not a filing delay. Sponsors who wait for a mandatory-use date to start that mapping will be doing it under a clock instead of on their own schedule; our clinical quality assurance team runs exactly this kind of process pilot before a regulation forces the pace.
Frequently asked questions
Is ICH M11 (CeSHarP) mandatory?
No. FDA's final guidance (91 FR 30310, May 22, 2026) uses the standard nonbinding-recommendations language, and EMA has not attached a compliance date to its version of the guideline. Both authorities have finalized the text; neither has made it a requirement.
What is the difference between the CeSHarP template and a normal protocol template?
CeSHarP fixes section numbering across every protocol — trial design in Section 4, eligibility criteria in 5.4/5.5, stopping rules in 7.4 — and pairs that structure with a technical specification defining conformance and cardinality for each data element, so protocol content can be exchanged electronically rather than re-keyed. Copying the headings without the underlying structured data is not the same as implementing the technical specification.
Do we need new software to adopt ICH M11?
You need protocol-authoring or eTMF tooling that can produce the technical specification's structured, coded data elements — not merely a template with the right headings. Confirm your current platform's roadmap before committing a study to CeSHarP.
Sources & further reading
- FDA. M11 Clinical Electronic Structured Harmonised Protocol (CeSHarP) — Guidance for Industry; Availability (91 FR 30310, May 22, 2026). federalregister.gov
- ICH. M11 — Clinical Electronic Structured Harmonised Protocol, Step 4 guideline, template, and technical specification (adopted Nov. 19, 2025). ich.org
- EMA. ICH M11 guideline, clinical study protocol template and technical specifications — Scientific guideline. ema.europa.eu
This article is provided for general informational purposes and reflects the regulatory landscape as of September 2026. It is not legal or regulatory advice. Confirm current ICH M11 implementation status with FDA, EMA, or qualified counsel before acting.
