Florence eISF Alternatives: Connecting the Site File to the Study Record

Florence alternatives concept: an evidence thread running solid through a complete site file then breaking before the study record holding delegation, visit window and milestone data

Florence alternatives compared and named: Veeva SiteVault, Complion from RealTime, Advarra eReg, TransPerfect Trial Interactive, SharePoint and AQ. Each is described in its vendor’s own published wording, with what a site file does not hold, what an inspection costs when one study sits in two systems, and how a move is planned.

ALCOA+ and the Trial Master File: Applying Data Integrity Principles

ALCOA+ and the Trial Master File: a filed document threaded on a continuous record of who, when and why

ALCOA+ applies to the whole Trial Master File, including the system that holds it. This guide maps each of the nine attributes to the TMF control that evidences it, shows where attributes are lost between the activity and the filing, and explains why four of the nine sit with the system rather than the page.

TMF Reference Model and the Investigator Site File: Where eISF Fits

TMF Reference Model and the Investigator Site File: one model, the site holds part of it

The investigator site file structure is the site-held part of the Trial Master File. This guide maps the ISF to the DIA TMF Reference Model, shows which of the 11 zones live at the site, who holds each copy, and how a shared structure lets a monitor reconcile the two files zone by zone.

NHS R&D: Governing Site Files Across a Trust’s Studies

NHS R&D site file governance: one trust-wide standard governing every study's site file

NHS R&D site file governance is the trust-level control that keeps every study’s site file complete, current, and consistent across the whole portfolio. This guide explains what an R&D office must govern, how consistency breaks when each study files on its own, and the controls that hold a trust-wide standard.

Placeholder Documents in a TMF: Why Gaps Need Owners, Not Just Flags

Conceptual illustration of a TMF placeholder document flagged as a gap and then assigned an owner with a due date, showing every TMF gap needs an owner not just a flag

A placeholder document in a Trial Master File marks an expected record before the real one arrives. It makes an absence visible, but a flag alone does not close it. This guide explains what placeholder documents are, why every gap needs a named owner and a due date, and when a persistent gap should escalate to CAPA.

eISF vs Paper Site Files: Closing the Monitoring Visit Gap

Conceptual illustration of a live eISF screen reviewed remotely by a CRA between monitoring visits, beside a faded unseen paper binder, closing the monitoring visit gap

An electronic Investigator Site File and a paper site file hold the same essential documents, but only one can be reviewed between monitoring visits. This guide explains the monitoring visit gap, compares eISF and paper across the controls inspectors test, and shows what actually closes it.

TMF Completeness Tracking: How RAG Scoring Prevents Inspection Findings

Conceptual RAG completeness gauge for a Trial Master File, mostly green with amber due-soon and red missing segments, showing gaps surface before an inspection

TMF completeness tracking measures a Trial Master File against the documents it should hold, and RAG scoring grades each as red, amber or green. This guide explains how real-time scoring surfaces gaps early, which metrics show completeness, and how it prevents MHRA inspection findings.

The DIA TMF Reference Model: A Practical Guide to the 11 Zones

Conceptual illustration of the DIA TMF Reference Model as eleven numbered zones in one shared structure, so every document has one agreed home

The DIA TMF Reference Model organises every Trial Master File document into 11 standardised zones. This guide walks each zone, explains how zones, sections and artefacts fit together, and shows why a shared structure removes the reconciliation cost when sponsors, CROs and sites share a TMF.

ePSF vs eISF: Why Pharmacy Documentation Needs Its Own File

Conceptual hero: eISF and ePSF as two separately held folders on their own plinths, each with its own inspection lens and owner, divided by a dashed boundary

The pharmacy site file is not a folder inside the investigator site file. It is a separately owned, separately held, separately inspected record, and merging the two is what costs sites at inspection. This guide explains why ePSF and eISF stay distinct, what belongs in each, and why the separation still matters once both go digital.

Free guides · PDF
Find the right guide for you

Pick a module, your organisation type, or both — we'll match the guides and email them to you.

Most popular guides
Explore
15+ guides

Free guides · PDF

Guides matched to you.

✓ Written for first-in-human & Phase 1 sites

✓ Inspection-ready checklists & templates

✓ Aligned to MHRA, FDA & EU Annex 11