Type to search every page, guide, role page, event and post.

Trelice

The protocol authoring platform
for clinical trials.

Write the protocol once. Every document follows.

Trelice is an ICH M11-native platform for writing the clinical trial protocol. It generates ICFs, visit worksheets, eligibility screeners and redacted protocols from the approved protocol, and flags each one for regeneration when the protocol is amended.

A short walkthrough of authoring a protocol and generating its downstream documents.

How the data moves

Everything that should be linked, is linked

Trelice maps how your documents really depend on each other, down to the parental consent form for Japan. Because every one of those links is real, data flows on its own across the whole program, and Trelice sees the moment anything falls out of sync. Nobody has to keep that map in a tracker or work it out in a meeting. Click a stage to jump to it, or let it play.

1 of 5One study, its documents, and the brochure above it

Study A is the first protocol for the product, in atopic dermatitis. The Investigator’s Brochure sits above it and prefills the product facts: names and codes, formulation, mechanism of action, dose rationale, adverse events of special interest. Below it sit the documents generated from the approved protocol: the visit worksheets, the eligibility screener and the consent form, which splits into adult, child and parental masters, each with its own version for the USA, Germany, Japan and Canada. Every arrow is a live link, not a copy. Whenever a study changes, what changed goes back up to the brochure, and the updated brochure goes out to every study.

  • Live link
  • Data flowing
  • Change proposed, waiting for review
  • Out of sync, drift detected
  • In sync

What Trelice is

Trelice is the protocol authoring platform for clinical trials, built natively on the ICH M11 structured protocol standard. Clinical operations teams and medical writers at pharma sponsors of any size use it to author study protocols in a structured, regulatory-led format instead of Word templates.

From the approved protocol, Trelice generates the downstream documents that depend on it: informed consent forms (ICFs), site visit worksheets, IRB/EC question-and-answer documents, and redacted protocols for public registry disclosure. It also generates a version of each document for each site, the way source documents should be. When the protocol is amended, every generated document flags for regeneration. That prevents the inconsistency that comes from re-syncing files by hand.

Trelice also manages the protocol development process itself. Sections are assigned to writers and reviewers with due dates, approvals move through a queue, progress is visible on a dashboard, and electronic signatures and a permanent audit trail record every step.

Trelice is architected for 21 CFR Part 11, with audit trails built in from the ground up. It was shaped in close collaboration with clinical trial practitioners.

One protocol, every document

ICFs, redactions, screening forms and more, instantly ready and always up to date.

The protocol is only the start. Every document a trial derives from it is generated straight from your approved protocol, and the moment the protocol changes, each one flags for regeneration. No more rebuilding the same content by hand across five files and hoping they still agree.

Informed consent forms

Master, country, site, and population-specific ICFs generated directly from the protocol, in plain language and ready for IRB submission.

Redacted protocols

Public-disclosure and transparency redactions applied automatically and consistently, ready for submission without a manual markup pass.

Screening & eligibility forms

Inclusion and exclusion criteria flow from the protocol into screening forms that stay in lockstep every time the criteria move.

Investigator’s Brochure

One brochure per investigational product, upstream of every protocol that uses it: new protocols start prefilled from the current edition, and approved protocols propose their study facts back for the next one.

How the brochure connects

Another document type

If your trial needs a document Trelice does not generate yet, reach us and we will add it to the pipeline.

Request a document type
Trelice document generation hub for one protocol: consent forms, visit instructions, study schematic, eligibility screener and screening form, IRB Q&A, site budget, redacted protocol, and site distribution
Every document here is generated from the approved protocol and flags for regeneration when the protocol changes.
Clinical trials deserve better protocols

Built for the way protocols get written.

Clinical trials teams stitch together Word templates, chase down regulatory citations, and re-sync every downstream document by hand. Every edit is an opportunity to drift out of compliance, incur additional cost, and delay study timelines.

6mo
Median authoring time for a Phase II protocol across industry, much of it spent on consistency and compliance review.
73%
Of protocols require ≥1 substantial amendment post-approval, each one triggering a cascade of document rewrites.
$141k
Average cost per protocol amendment, counting rework, IRB re-submission, and study delay.
Authoring, the flagship

Keeping up with regulations, so you don’t have to.

Tell Trelice where your trial will run, and the protocol reshapes itself to every country or region you select, adding the fields each jurisdiction requires and citing the exact regulation behind every one, so you can feel confident your protocol won’t be rejected over a compliance gap.

Trelice regulatory references for the IND Number field: 21 CFR 312 marked required for the FDA, EU CTR Annex I for the EMA, and the PMD Act for the PMDA
Compliance by design

Built for regulators, not retrofitted for them.

ICH GCP
E6 (R3)
The updated international standard for clinical trials
FDA
21 CFR
US clinical-trial regulations, including Part 11
EU
536/2014
The harmonized EU Clinical Trials Regulation
CDISC
USDM
The protocol as a machine-readable study definition
+
Local
Country-specific regulators as applicable: MHLW (JP), MHRA (UK), and more
01 / Update once, update everywhere

Change an endpoint. Watch every relevant section update itself.

Trelice's protocol modules are intelligently linked together. When you revise a field that appears in multiple protocol sections (a primary endpoint, say), the platform propagates the change to every other relevant section: synopsis, eligibility, objectives, statistical analysis.

What used to take a medical writer three weeks takes three minutes. The platform prevents the inconsistency that hand-synced sections accumulate.

  • Repeating data tagged by the system
  • Bidirectional links between all related fields
  • Change impact preview before you commit
Trelice: a field linked across multiple protocol sections so editing any one updates all
02 / Review and approve in one place

Assign reviewers, and watch the approvals roll in.

No more frantically chasing down team members via email to make sure they reviewed the protocol. Simply assign reviewers in Trelice and watch the approvals roll in. Export the review and approval audit trail with the click of a button to demonstrate regulatory compliance.

Nothing reaches a regulator without the right eyes on it. Every decision is captured with an electronic signature and a full audit trail, architected for 21 CFR Part 11.

  • Assign named reviewers and approvers per section
  • One-click export of the full review & approval audit trail
  • Electronic signatures on every sign-off, architected for 21 CFR Part 11
Trelice review process for a protocol section: three review levels, each reviewer's approval status, authoring and review due dates, and the assigned writer
03 / Automated QC and formatting

Submission-ready formatting, checked automatically.

Once you've finished writing, Trelice automatically QCs your protocol for consistency, adds bookmarks and in-document linking, and puts all formatting in submission shape.

What used to take medical writers weeks is now done automatically in minutes.

  • Automated consistency and terminology checks
  • Bookmarks and in-document cross-links added for you
  • Submission-ready formatting applied in minutes, not weeks
04 / Live Document Preview

See your protocol in Word or PDF, live as you type.

Prefer to see your protocol in Word or PDF as you go? The live document preview updates as you type. Export at any time to get the fully formatted, submission-ready Word or PDF document.

  • Faithful Word and PDF rendering with your organization's template
  • Track changes, comments, and redlines preserved on export
  • One-click submission-ready PDF with bookmarked sections
Trelice protocol editor beside the live PDF preview, with page thumbnails and the rendered synopsis
And there’s more

You write the protocol, we generate the ICF.

The informed consent form has always been the hardest downstream document: plain language, legally binding, jurisdictionally varied, rewritten every time the protocol shifts. Trelice automates it.

Product / 01

Authoring

Protocols, written with regulatory intelligence.

The structured protocol authoring system. Regulatory rationale per field, intelligent linking, native approval flow, live document preview.

Explore Authoring
Product / 02

ICF

Informed consent, automatically generated.

Create master, country, site, and population-specific consent forms with the click of a button directly from the approved protocol. IRB-ready and auto-regenerating, with plain language held to a patient reading level.

Explore ICF
Product / 03

Investigator's Brochure

One brochure per product, every protocol in step.

Author the Investigator's Brochure once per investigational product and every protocol that uses it starts prefilled from the current edition. Approved protocols propose their study facts back, and the next edition's summary of changes is generated rather than written.

Explore the Investigator's Brochure
Who it’s for

One protocol, working for every actor in the trial.

A trial is run by sponsors, CROs, and sites, and each of them spends weeks producing documents the others depend on. Trelice generates each actor’s documents from the same approved protocol, so every team starts sooner and nothing drifts out of sync between them.

Sponsors

Write the protocol in weeks, not months.

Author the protocol in a structured, ICH M11-native editor instead of a Word template. Every field carries its regulatory rationale, linked sections stay consistent as the design evolves, and reviews, signatures, and the audit trail live in one place, so lean teams move from synopsis to a submission-ready protocol without hiring an army.

ICH M11-nativeFewer amendmentsFaster to IND

CROs

Generate the deliverables, onboard sites faster.

Import the sponsor’s protocol, or pick up one authored in Trelice, and generate the documents your engagement depends on: master, country, and site-specific ICFs, plus eligibility screening forms driven directly by the inclusion and exclusion criteria. With each site’s document set generated instead of built by hand, site onboarding shrinks from weeks of document preparation to days.

ICF generationEligibility screenersFaster site onboarding

Sites

Enroll sooner, audit-ready from day one.

Source documents arrive generated per site from the approved protocol: visit worksheets, subject booklets, and screening forms, ready before the first patient walks in. Coordinators start enrollment quickly instead of building paperwork first, and because every document traces back to the protocol version it came from, sites are fully audit-ready for source document review from the get-go.

Per-site source docsQuicker enrollmentAudit-ready from day one
FAQ

Frequently asked questions

What is Trelice?

Trelice is the protocol authoring platform for clinical trials. Protocols are written in a structured format aligned with ICH M11, and downstream trial documents are generated directly from the approved protocol.

Is Trelice ICH M11 native?

Yes. Trelice is built natively on the ICH M11 structured protocol standard rather than retrofitting M11 headings onto Word templates. The authoring structure itself follows the standard.

Does Trelice support CDISC USDM?

Yes. Because protocols in Trelice are structured data, Trelice produces a CDISC Unified Study Definitions Model (USDM) study definition from the approved protocol for downstream systems to consume, and it is defining USDM-based structured definitions for the documents generated from the protocol (see USDM support).

Does Trelice generate informed consent forms (ICFs) from the protocol?

Yes. Master, country-, site-, and population-specific ICFs are generated directly from the approved protocol in plain language, and they flag for regeneration whenever the protocol changes.

What other documents does Trelice generate?

Site visit worksheets and a printable subject booklet, an eligibility screener driven by the protocol’s inclusion and exclusion criteria, IRB/EC questionnaires, study schematics, a summary of changes for each amendment, and redacted protocol versions for public disclosure. Documents are generated per site where that matters, the way source documents should be. Additional document types can be added on request.

What happens when a protocol is amended?

The change is made once, in the protocol. Trelice keeps interdependent protocol sections consistent and flags every generated downstream document for regeneration, so amendments do not require manually reconciling separate files.

Does Trelice support 21 CFR Part 11?

Trelice is architected to support 21 CFR Part 11 requirements, including audit trails and electronic signatures. Validation is in progress.

Who is Trelice for?

Clinical operations teams at pharma sponsors of any size are the primary users, alongside the medical writers who author protocols. CROs and agencies use Trelice’s document generation downstream.

Does Trelice manage writer and reviewer assignments?

Yes. Protocol sections are assigned to writers and reviewers with due dates (see sending a section for review). Reviewers approve or request changes from an approval queue, pending tasks are tracked per person (see pending tasks), and a dashboard shows where each protocol stands. Electronic signatures and a permanent audit trail record every step.

How do distributed teams collaborate in Trelice?

Everyone works on the same protocol in the browser. Comments are anchored to individual fields and resolved in place (see comments and working together), a banner shows who else is editing a section, and any field can be shared as a link that lands a colleague exactly there. Notifications arrive in the app and by email, with per-type preferences (see notifications and reminders).

Can Trelice manage several studies at once?

Yes. Studies are the top-level container, with statuses from concept through completed and a searchable studies list (see working with studies). A dashboard summarizes active studies, protocols in development, and pending reviews across the organization (see your dashboard), and one pending-tasks page tracks outstanding work across every protocol (see pending tasks).

Does Trelice handle abbreviations automatically?

Inserted abbreviations are expanded at their first mention in the exported document, and the Abbreviations and Definitions section builds itself from what the protocol actually uses. Definitions come from your organization’s shared library or the standard ICH/GCP set, and entries that are defined but unused are flagged (see writing and formatting text).

Does Trelice number Schedule of Assessments footnotes automatically?

Yes. Footnotes attach to a visit, an assessment, or a single cell. Trelice numbers and places them, renumbers them when visits or rows move, and lets one footnote be reused across the table (see filling in structured sections).

Trelice Schedule of Assessments as a visit by assessment matrix, with visit timing and windows and assessments grouped by category

What is the summary of changes for an amendment?

A generated list of every field an amendment changed, old and new values side by side, with the written reason for each change. It downloads as PDF or Word, and the full amendment history exports to CSV (see amendment history and versions).

Can Trelice import an existing protocol?

Yes. Upload a PDF or Word protocol and Trelice extracts it into structured sections, reporting what was populated where; unmapped content is preserved under the appendices (see working with studies). The ICF Generator also drafts a consent form directly from an uploaded protocol PDF.

Can Trelice create a new protocol from an existing one?

Yes. Any protocol offers Create from this: pick the reason (sub-study, new indication, next phase), the source version, the destination study, and exactly which sections, fields and list items to copy. Every copied field stays linked to its source, so the two protocols watch each other for drift from then on (see derived protocols).

How does Trelice detect drift between related protocols?

When a protocol is derived from another, each copied field keeps a link in both directions. If either protocol later changes a linked field, the other side gets a drift alert showing both values side by side, and a person resolves it: keep mine, take theirs, or unlink the field on purpose. A section with unresolved drift cannot be approved, and every resolution is recorded in the audit trail (see drift alerts).

What is a derivation template?

A saved answer to "what does our sub-study copy from the parent protocol?". It stores the list of sections, fields and list items to copy, never any content, so it works on any source protocol. Applying one preselects the whole picking step; the derivation records which template was used (see derivation templates).

Does Trelice author the Investigator's Brochure?

Yes, as its own product. Trelice keeps one brochure per investigational product, shared by every study of that product, with immutable released editions, a generated Summary of Changes, a structured Reference Safety Information table and an audited annual review. New protocols are prefilled from the current edition, and approved protocols propose their study facts back for the next one (see the Investigator's Brochure).

What happens across my studies when a new brochure edition is released?

Releasing an edition compares every brochure-linked field of every protocol that uses the product. Changed fields raise drift alerts on those protocols, and consent forms whose risk language the edition touched are flagged for an update. An Impact view lists every affected study, protocol and consent form, so the follow-through is a worklist rather than a memory exercise (see kept in step both ways).

Can Trelice match our company's document format and template?

Yes, on both axes. Upload one sample document and Trelice learns your house style, fonts, margins, headers, cover page and logo, as a versioned format template applied to exports and previews. Your protocol template, the heading tree, numbering and your own fields, can be captured as a protocol layout, learned from a document too (see document formats).

How does Trelice help a program scale to many protocols?

By replacing copies with links. New protocols are derived from existing ones with every copied field watched for drift, product facts live once in the Investigator’s Brochure and flow into every protocol, downstream documents flag for regeneration when their protocol changes, and house formats make the twentieth study’s documents come out as right as the first (see scaling clinical programs).

Will Trelice make it harder to collaborate with external reviewers?

No. Trelice does not charge per user, so you can invite principal investigators, medical experts, consultants, and other external contributors without purchasing additional seats.

Access can be limited to exactly what each person needs to review or edit. This allows external contributors to participate directly while protecting the rest of the study and your organization’s information.

Instead of reconciling multiple Word documents, conflicting tracked changes, and disconnected comments, your team can manage feedback in one controlled environment. When a document is ready for distribution, Trelice can export it to Word or PDF.

Is Trelice overkill for a small company or a single protocol?

No. Small teams often have the least capacity to absorb preventable mistakes, rework, and delays.

Trelice’s consistency checks, reusable content, automated document generation, and structured authoring capabilities do not require a lengthy implementation project. They support the team from the first protocol.

For a small sponsor, identifying an inconsistency before submission, or avoiding weeks of manual document reconciliation, can make the difference between keeping a study on schedule and experiencing a costly delay.

Why doesn’t Trelice use generative AI to write the protocol?

Trelice does not position generative AI as a substitute for scientific and medical judgment.

Clinical protocols contain consequential decisions that must be accurate, explainable, and approved by qualified people. Generative AI can produce convincing but incorrect information, omit important context, or introduce unsupported assumptions. In a regulated document, polished prose is not the same as reliable content.

Trelice focuses on helping authors create consistent, complete, traceable protocols while keeping people accountable for the scientific content. AI is used for bounded, reviewable tasks, such as converting an existing protocol into Trelice, not for inventing medical rationale or study design decisions.

How does Trelice use AI?

The core of Trelice is deterministic: protocol authoring, review, approval, amendments, consistency checks, and the documents computed from the structured data of the protocol run on the structure of the protocol, not on a language model. AI is optional and bounded. Trelice uses it to import an existing document, to learn a house format, and to draft consent form sections and their translations. Those drafts are labeled, and a person reviews each one before it counts. Every AI feature can be turned off. A team can also connect its own AI agents, whose work lands in Trelice as drafts and comments. A person approves every change, and an AI agent never approves.

Do we have to use AI to use Trelice?

No. Trelice works without AI. Protocol authoring, review, approvals, amendments, consistency checks, and the documents computed from the structured data of the protocol are deterministic: they run on the structure of the protocol, not on a language model.

AI is used in three bounded places: importing an existing Word or PDF document into structured sections, learning your house format from a sample, and drafting consent form sections and their translations, which are labeled as drafts and reviewed by a person. Each has a manual path. A protocol can be started from a template instead of an import, a format can be configured by hand, and a consent section or a translation can be written by hand.

Every AI feature can be turned off for your organization, and on request we set up your account with AI disabled entirely. Nothing in the platform depends on it.

What is an AI agent?

An AI agent is an AI language model that has been given tools and a goal, so it can work through a task on its own: read documents and email, use software the way a person uses it, and take the next step based on what it found. A chatbot answers a question and stops; an AI agent can, for example, read an IRB letter and draft a response to each question. The AI agents page explains the terms in plain words for clinical teams.

Can AI agents work in Trelice?

Yes. An AI agent can draft protocol updates from research documents and emails, turn meeting notes into field-level comments, draft IRB responses, and start amendments, including from a safety query in your EDC. Its work lands in Trelice as drafts inside the normal workflows, held to the same structure, mandatory fields, and validation as a person’s work (see AI agents in Trelice). These are agents your team connects. Trelice itself does not draft protocol content with a language model, and a person approves every change.

How does Trelice prevent AI from hallucinating?

It doesn’t, because nobody can: producing confident text that is sometimes wrong is a property of the technology itself. That is exactly why humans are always in the loop in Trelice. AI output arrives as drafts and comments inside structured sections with mandatory fields, where validation and consistency checks catch what they can, and a qualified person reviews and approves every change before it becomes part of the study record. The honest design is not AI that never errs, it is a system where an error cannot become an approved document without a human missing it first.

Can an AI agent approve changes in Trelice?

No. An AI agent can run a first review that flags inconsistencies, but every approval in Trelice is a human approval: review workflows name a person as the approver, electronic signatures belong to people, and the audit trail records who or what made every change. Trelice allows you to scale and bring AI to the table without losing governance, on both human and machine.

Why doesn’t Trelice publish simple per-user pricing?

Because Trelice does not charge based on the number of users.

Per-seat pricing discourages organizations from including the reviewers and contributors needed to create a strong protocol. Trelice instead considers the scale and needs of your clinical development program, allowing you to invite internal and external collaborators without worrying about the cost of every additional seat.

This makes pricing predictable around the work being performed, rather than the number of people contributing to it.

Is migrating from Word and existing protocol processes difficult?

No. You do not need to rebuild every protocol manually or abandon your existing work.

Add your users, import your current protocols, and Trelice’s AI-assisted migration process converts them into structured protocols within the platform. Your team can review the imported content and continue working from there.

This provides a practical path from document-based authoring to structured protocol management without starting over, while preserving human review and control throughout the transition. Import is optional: teams that prefer not to use AI can start each protocol from a template and bring content across themselves.

See a protocol draft itself in thirty minutes.

Bring a synopsis. We’ll walk through Authoring together on your actual study: regulatory rationale, intelligent linking, approval flow, live document preview, and the downstream ICF.

Request a Tour