Sponsors and CROs that own and maintain the trial master file (TMF) and need an electronic TMF system.
Scope Sponsors and CROs that own and maintain the trial master file. Site-side eISF and eRegulatory binders are out of scope, except where the vendor also sells a sponsor or CRO eTMF (Florence). The collaboration feature notes describe how each eTMF exchanges documents with sites.
These notes describe the products in the eTMF guide.
Florence eTMF
Best for
Sponsors and CROs whose sites already use Florence eBinders and who want site documents to flow into the TMF
What to consider
Florence's strength is the site side: its eTMF connects to each site's Florence eISF through SiteLink, and Florence reports 88,000+ research sites on its network. It has an open API, Part 11 electronic signatures and a SOC 2 Type II report. Its public eTMF pages do not describe a TMF Reference Model structure or inspector access.
Sponsors overseeing CRO-run TMFs who want TMF quality review and expert services alongside the software
What to consider
PhlexTMF, from Phlexglobal (part of Cencora), is a TMF-only product with pre-trained AI indexing, built-in quality review and Exchange Mechanism export. We found no current public compliance statement or certification and no documented integrations or site exchange. Ask for its SOC 2 or ISO report and validation package.
Single and double checks describe documented support for an individual feature. Double checks use the extended definition for that feature. Unknown means the available evidence does not establish support.
Expand a feature definition or support note for context and its original source.
Florence eTMF vs PhlexTMF (eTMF): category feature evidence and sources. Products are not ranked.
Category feature
Florence eTMF
PhlexTMF
TMF Reference Model and inspection readinessFeature definitions
Supported
A TMF Reference Model structure or document completeness tracking is documented.
Extended support
A TMF Reference Model structure, completeness tracking and dedicated inspector access are all documented.
Florence eTMF
Supported
Florence shows missing and expired documents and milestone dashboards, but its public eTMF pages do not describe a TMF Reference Model structure or inspector access.
Missing/expired-document and milestone dashboards establish tracking; model alignment and inspector access are not described.
PhlexTMF
Supported
PhlexTMF tracks expected versus received documents by trial, country and site, exports in the Exchange Mechanism format, and PhlexTMF for Viewing gives inspectors access to closed-study TMFs.
Expected-document tracking and closed-study inspector access are stated; Reference Model alignment is not stated.
Document capture and AI automationFeature definitions
Supported
Automated document capture, filing or processing is documented.
Extended support
AI classifies or indexes documents and extracts metadata or attribute values.
Florence eTMF
Supported
Florence syncs documents into the eTMF by email and in October 2026 announced AI classification that recommends document type and filing location for user approval; metadata extraction is not described.
Exchange Mechanism export establishes data exchange; named integrations and a public API were not found.
Compliance and validation evidenceFeature definitions
Supported
Relevant trial compliance or security controls are stated, with their scope identified.
Extended support
Relevant trial controls and a publicly accessible ISO certificate or SOC audit report covering the product or vendor are documented.
Florence eTMF
Supported
Florence has an annual third-party SOC 2 Type II attestation (report under NDA), and its eTMF FAQ states Part 11-compliant electronic records and signatures.