Trial Operations — Glossary¶

← Back to glossary index

The day-to-day mechanics of running a clinical trial — site readiness, enrolment, data quality, deviations, and the cycle metrics that determine whether a trial finishes on time and on budget.

Terms covered:

Site activation
Enrolment velocity
First Patient In (FPI), Last Patient In (LPI), Last Patient Out (LPO)
Site Initiation Visit (SIV)
Database lock
Source Data Verification (SDV)
Query / query resolution
Protocol amendment
Protocol deviation
Risk-based monitoring (RBM)
Cycle time

Site activation¶

Definition. The process of getting a clinical trial site ready to enrol patients — covering regulatory approvals (ethics committee, regulatory authority), site contracts, site staff training, drug shipment, and operational readiness. A site is "activated" when it can legally and operationally begin screening and enrolling patients.

In practice. Site activation is a multi-step pipeline:

Site selection and feasibility — sponsor confirms site has the right patient population and operational capacity
Site contract negotiation — typically the slowest step, can take 60-180 days
Ethics committee submission and approval — varies wildly by jurisdiction (4-12 weeks typical)
Regulatory authority submission (where required separately from ethics)
Site Initiation Visit (SIV) — sponsor / CRO trains site staff
Drug shipment to site
First patient screened / first patient enrolled

Total cycle time from selection to first-patient-in is commonly 4-9 months.

Why it matters. Site activation is the dominant rate-limiting step in trial start-up. Slow site activation directly delays first patient in, which delays everything downstream. The variation across sites is wide — fast sites activate in months, slow sites can take a year+.

Where Flusso fits. A real-time site activation status board (per site, per trial, with red-amber-green flags on each pipeline step) is one of the highest-value operational views Flusso provides. Sponsors typically have this data fragmented across CTMS, regulatory affairs trackers, contract management systems, and CRO project trackers — Flusso unifies it.

Enrolment velocity¶

Definition. The rate at which a clinical trial enrols patients, typically measured per site per month or per trial per month. The fundamental operational metric in trial execution.

In practice. Enrolment velocity is tracked at multiple levels:

Per-site velocity — patients enrolled per site per month; identifies fast vs. slow sites
Per-region velocity — aggregated; identifies regional bottlenecks (regulatory, demographic, competitive)
Per-trial velocity — aggregated; tracked against the enrolment plan
Cohort-level velocity — for trials with multiple cohorts, how each cohort is filling

Common patterns:

Front-loaded enrolment (sites are highly motivated at start, slow as competing trials emerge)
Long-tail enrolment (last 20% of patients takes 50% of the time — the hardest patients to find)
Site dropout (some sites that activate never produce a patient)

Why it matters. Enrolment velocity is the single largest driver of trial duration, and trial duration is one of the largest drivers of trial cost. A 6-month enrolment delay on a Phase 3 trial can cost $10M+ in incremental burn and delay launch revenue by similar or longer.

Where Flusso fits. Real-time, cross-trial enrolment velocity dashboards with anomaly detection (sites that have stopped enrolling, regions that are slipping, cohorts that are filling faster or slower than expected) means slow-site detection moves from "we noticed in last month's review" to "we knew within a week."

Related: Site activation · Cycle time

First Patient In (FPI), Last Patient In (LPI), Last Patient Out (LPO)¶

Definition. The three canonical milestones of clinical trial enrolment and follow-up:

First Patient In (FPI) — the first patient enrolled and dosed in a trial
Last Patient In (LPI) — the last patient enrolled (enrolment complete)
Last Patient Out (LPO) — the last patient completes the protocol-defined follow-up

In practice. These milestones structure trial execution and frequently appear as contractual triggers in development milestones. The interval from FPI to LPI is the enrolment phase; LPI to LPO is the follow-up phase; LPO to database lock is the close-out phase.

For Adagene's muzastotug Phase 2 (Q1 2026 reported "completed enrolment"), LPI is the recent milestone; LPO will follow at the end of the protocol-defined follow-up period; database lock will follow shortly after LPO.

Why it matters. These are the most-commonly-tracked operational milestones in any trial and the events that trigger most development milestone payments. Their predictability (or lack of it) shapes finance forecasts.

Where Flusso fits. Predictable milestone forecasting based on real-time enrolment velocity rather than retrospective spreadsheet projections. Finance can update cash-flow forecasts on real data, not stale assumptions.

Site Initiation Visit (SIV)¶

Definition. The formal sponsor / CRO visit to a clinical trial site that authorises the site to begin enrolling patients. Conducted after all regulatory and contractual prerequisites are met, the SIV trains site staff on the protocol, study procedures, EDC system, and trial-specific safety reporting.

In practice. Common SIV components:

Protocol training for the PI, sub-investigators, study coordinators, pharmacy, lab
EDC system training and account provisioning
Investigational product handling, storage, and dispensing training
Safety reporting workflow review
Source documentation requirements walkthrough
Question-and-answer session

The SIV must be completed before the site can enrol — it's the operational equivalent of "go live."

Why it matters. SIVs are often delayed because of last-minute protocol amendments, document version mismatches, or scheduling conflicts. Each delay pushes site activation and enrolment downstream.

Where Flusso fits. SIV status is a tracked attribute in site activation. Flusso surfaces SIV scheduling, completion, and post-SIV first-patient timing across the portfolio.

Related: Site activation · Protocol amendment

Database lock¶

Definition. The formal closing of a clinical trial database for analysis. After database lock, no further data can be entered or modified; the dataset is frozen for statistical analysis. A prerequisite for top-line data readout and for the Clinical Study Report.

In practice. Database lock is preceded by a structured close-out process:

Last patient out — final protocol visit completed
Final monitoring visits — site monitors verify all data captured
Query resolution — open queries cleared
Data review — sponsor data management reviews dataset for completeness
Database lock — the lock event itself
Statistical analysis — pre-specified analyses run on locked data
Top-line data readout

The interval from LPO to database lock is typically 2-4 months for a well-run trial; longer if data quality is poor.

Why it matters. Database lock is a critical milestone — it gates the data readout that triggers most major partnership and regulatory milestones. Slow database lock = delayed cash inflow + delayed regulatory progression.

Where Flusso fits. Continuous data quality visibility throughout the trial means database-lock readiness is known in real time, not discovered at LPO. Surprises at lock-time become rare.

Related: LPO · Query / query resolution · SDV

Source Data Verification (SDV)¶

Definition. The process of verifying that data entered into the EDC matches the original source documentation at the site (paper records, hospital systems, lab reports). Performed by clinical research associates (CRAs) — the field-based monitors who visit sites periodically.

In practice. Historically, SDV was 100% — every data point in the EDC was verified against source. The industry has moved toward risk-based monitoring (RBM), where SDV is targeted at high-risk data points (primary endpoints, safety endpoints) rather than performed exhaustively.

A typical CRA monitoring visit covers:

SDV of selected data points (per the monitoring plan)
Source document review for completeness and quality
Drug accountability check
Query generation for discrepancies found

Why it matters. SDV is one of the largest cost lines in clinical trial monitoring. Reducing SDV burden through risk-based approaches has been a major industry efficiency push over the past decade. SDV findings drive query rates.

Where Flusso fits. Out of scope for the SDV process itself (which is field-based), but the visibility into SDV completion rates, query generation patterns, and monitoring-visit cadence across sites is part of Flusso's operational dashboard.

Query / query resolution¶

Definition. A formal request from the sponsor / CRO to the site to clarify, correct, or supplement a data entry in the EDC. Generated automatically by the EDC (range checks, logic checks) or manually by data managers / CRAs reviewing the data.

In practice. Common query types:

Range queries — value outside expected range (lab value, vital sign)
Consistency queries — value inconsistent with another captured value (e.g., end date before start date)
Missing data queries — required field left blank
Source mismatch queries — EDC value doesn't match source document
Safety queries — clarification needed on adverse event reporting

Sites are expected to respond within a defined turnaround (often 5-10 business days). Open queries blocking database lock are a primary source of close-out delay.

Why it matters. Query rates and resolution times are operational signals — high query rates indicate site quality issues; slow resolution times indicate site engagement issues. Both directly impact database lock timing.

Where Flusso fits. Cross-site query rate dashboards surface site quality problems early. Cross-trial query patterns can highlight protocol design issues that should drive amendments before they affect more sites.

Related: SDV · Database lock · EDC

Protocol amendment¶

Definition. A formal change to an approved clinical trial protocol. Requires re-approval by ethics committees and regulatory authorities at every active site before the new protocol can be implemented. Protocol amendments are common — a typical Phase 2 trial sees 2-5 amendments over its life; Phase 3 trials often see 5-10+.

In practice. Common protocol amendment drivers:

Safety findings requiring inclusion/exclusion criteria changes or dose modifications
Operational difficulties requiring procedure changes
Emerging external data that changes the scientific question
Regulatory feedback requiring design changes
Sample size adjustments based on interim analysis findings

Amendment cycle time:

Sponsor-side drafting: 2-6 weeks
Ethics committee review: 4-12 weeks per site
Regulatory authority review (where applicable): 4-8 weeks
Site implementation: 2-4 weeks per site after approval

Why it matters. Protocol amendments are operationally disruptive — they pause enrolment at affected sites until re-approved, they require re-consent of enrolled patients in many cases, and they typically delay overall trial timelines by months. The cost of an amendment is real and often understated.

Where Flusso fits. Amendment-status visibility per site (drafted / submitted to ethics / approved / implemented) means the operational impact of an amendment is visible portfolio-wide rather than per-site. Cross-trial amendment patterns can also be detected — useful for protocol-design improvement over time.

Related: HREC / IRB · Site activation · Protocol deviation

Protocol deviation¶

Definition. Any departure from the approved trial protocol — could be an inclusion/exclusion criterion violation, a missed visit, a dosing error, a procedure performed out of window, etc. Protocol deviations are categorised by severity (minor vs. major) and tracked in the trial database.

In practice. Common protocol deviation categories:

Eligibility deviations — patient enrolled who didn't fully meet inclusion/exclusion criteria
Visit window deviations — visit performed outside the protocol-defined window
Dosing deviations — dose changed, missed, or administered incorrectly
Procedure deviations — required assessment not performed
Consent deviations — re-consent issues following protocol amendments

Major deviations affecting safety or primary endpoints can compromise the trial's ability to support regulatory approval — they're tracked closely and reviewed by the SRC.

Why it matters. High deviation rates are an indicator of site quality problems. Cross-site deviation patterns can indicate protocol design problems. Major deviations can affect data integrity and regulatory submission.

Where Flusso fits. Cross-site and cross-trial deviation pattern detection is exactly the kind of multi-source-system view that's hard to build manually. Flusso surfaces deviation patterns to the SRC and operations team continuously.

Related: Protocol amendment · SRC

Risk-based monitoring (RBM)¶

Definition. A monitoring approach that targets monitoring effort based on identified risks rather than applying uniform monitoring across all data and sites. Replaces the historical "100% SDV" model with a targeted approach that focuses on high-risk data, sites, and time points.

In practice. RBM components typically include:

A risk assessment at trial start identifying high-risk areas (primary endpoints, safety endpoints, complex procedures)
A monitoring plan that defines what gets full monitoring vs. targeted vs. remote-only
Centralised statistical monitoring (looking for anomalous patterns in EDC data centrally)
Triggered on-site monitoring when risk indicators emerge
Continuous risk reassessment through the trial

Why it matters. Done well, RBM reduces monitoring cost (a major trial cost line) without compromising data quality. Done poorly, it can leave critical risks unmonitored.

Where Flusso fits. Centralised statistical monitoring needs cross-site data visibility — exactly the kind of operational view Flusso provides. Risk indicators surfaced from operational data (high query rates, slow enrolment, deviation patterns) feed back into monitoring decisions.

Related: SDV · Query / query resolution

Cycle time¶

Definition. The duration of any defined operational interval in trial execution. Common cycle times tracked include site-activation cycle time (selection to FPI), enrolment cycle time (FPI to LPI), close-out cycle time (LPO to database lock), and trial cycle time (FPI to top-line data).

In practice. Cycle time is the universal metric for trial operational efficiency. Sponsors track it per trial, per site, per region, per therapeutic area, and benchmark against industry references (Tufts CSDD, KMR Group, Citeline benchmarks).

Why it matters. Cycle time compression is the most direct lever for trial cost reduction and competitive timing — getting to data faster means lower burn, faster milestone realisation, and earlier potential market entry.

Where Flusso fits. Real-time cycle time tracking with anomaly detection means cycle-time slip is detected as it happens, not in retrospective benchmark reviews. Operations can intervene early.

Related: Site activation · Enrolment velocity · Database lock

← Back to glossary index