An electronic investigator site file (eISF) is the validated system a research site uses to hold its essential trial records under version control, role-based access and a full audit trail. It holds the copy of the trial record that belongs to the investigator and stays under site control. AQ eISF is the site file module of AQ Platform.
AQ’s guide to eISF covers every critical aspect of eISF to support clear understanding and informed implementation:
- Clear definition of eISF and its role in clinical trials
- Evolution from paper-based ISF to connected digital systems
- Scope of documentation managed within an eISF
- Step-by-step workflow of how eISF operates across the study lifecycle
- Core features and system-level controls that govern documentation
- Roles and responsibilities of users interacting with the eISF
- Operational benefits and impact on study execution
- Relationship between the eISF, the eTMF and the pharmacy site file
- Regulatory requirements and how eISF supports compliance
- Key challenges in implementing an eISF system
- Criteria and capabilities required when selecting an eISF solution
- Overview of AQ eISF and its approach to controlled, connected documentation
What is an Electronic Investigator Site File (eISF)?
An Electronic Investigator Site File (eISF) is a study-scoped, software-based system designed to collect, organise, manage, and maintain site-level essential documents generated during a clinical trial. It operates within a structured, template-driven architecture where document classification, access control, version management, and audit traceability are enforced through system rules.
The eISF ensures that each document is attributable to authorised personnel, aligned with defined study roles, and maintained with complete lifecycle history in compliance with ICH-GCP, 21 CFR Part 11, and ALCOA+ data integrity principles. It also supports controlled workflows such as document review, approval, and electronic signatures, while enabling secure access for investigators, site staff, monitors, and auditors.
Also Read: What is ePSF in Clinical Trial Data Management?
What Does an eISF Manage in Clinical Trials?
An electronic Investigator Site File (eISF) manages all essential site-level documentation required to demonstrate that a clinical trial is conducted in compliance with protocol, regulatory requirements, and Good Clinical Practice. It acts as a structured, system-controlled environment where documents are not only stored but also organised, tracked, reviewed, and validated throughout their lifecycle. Each document remains linked to authorised personnel, defined responsibilities, and a complete audit history, ensuring continuous visibility, traceability, and inspection readiness across the study.
Core Areas Managed by an eISF
- Essential site-level clinical trial documents
- Structured document organisation and filing architecture
- Document versioning, updates, and approval status
- Role-based access control and user permissions
- Audit trail and complete document activity history
- Review workflows, approvals, and electronic signatures
- Remote monitoring access and document review processes
- Regulatory compliance and documentation alignment
- Inspection readiness and document completeness tracking
Scope Boundary Within Clinical Trials
An eISF manages investigator and site documentation, while central trial records are maintained in the eTMF and pharmacy-controlled records are managed within the pharmacy site file, ensuring clear separation of responsibilities across clinical trial systems.
Evolution of Investigator Site Files: Paper to Connected eISF Systems
The transition from paper-based Investigator Site Files (ISF) to electronic Investigator Site Files (eISF) has developed over time, with a noticeable acceleration between 2018 and 2025. This shift has been driven by increasing trial complexity, the need for remote oversight, and regulatory encouragement toward digital, traceable systems.
Paper-Based ISF (Pre-Digital Phase)
Investigator Site Files were originally maintained as physical binders at each clinical trial site. These binders contained essential documents required to demonstrate compliance with ICH-GCP and to allow evaluation of trial conduct and data quality.
The Principal Investigator and site staff were responsible for maintaining these records, ensuring documents were complete, current, and available for monitoring and inspections throughout the study.
However, this approach introduced operational limitations:
- Manual document handling and filing
- Limited access outside the site
- Delays in updates and version tracking
- High dependency on site staff for accuracy
- Increased risk of missing or outdated records
Documentation remained static and was often reviewed only during scheduled visits.
Early Digital Adoption (Pre-2018)
As trials expanded across multiple sites and regions, some organisations began using shared drives and basic electronic systems to manage site documents. This improved accessibility and reduced reliance on paper.
Even then, key challenges remained:
- No standardised document structure across studies
- Inconsistent version control and approval tracking
- Limited enforcement of user roles and permissions
- Absence of reliable audit trails
Digital storage existed, but documentation control was still largely manual.
Regulatory Push and Initial eISF Adoption (2016–2018)
The introduction of the ICH E6(R2) Addendum in 2016 emphasised risk-based monitoring and encouraged remote oversight. This created the need for systems that could provide real-time access to site documentation.
As a result, early eISF platforms began to emerge, allowing sites and sponsors to pilot structured, system-based document management approaches.
Rapid Acceleration During COVID-19 (2020–2022)
The COVID-19 pandemic acted as a major catalyst for eISF adoption. Restrictions on site visits forced sponsors and CROs to rely on remote monitoring, which required immediate digital access to site documentation.
During this period:
- eISF platforms enabled remote document review
- Sites reduced dependency on physical binders
- Digital workflows became essential for study continuity
This phase marked a transition from optional adoption to operational necessity.
Expansion and Standardisation (2023–2025)
Following the pandemic, eISF adoption expanded across global research sites. Structured documentation and remote oversight became the normal expectation rather than a pilot project.
At the same time, regulatory developments such as ICH E6(R3) reinforced the role of digital systems, encouraging flexibility, traceability, and quality-by-design in clinical trial documentation.
eISF systems during this phase introduced:
- Template-driven document structures
- Role-based permissions and access control
- Integrated audit trails and electronic signatures
- Real-time visibility into document completeness
2026 and Beyond: Intelligent, Connected, and Site-Centric eISF Systems
The next phase of eISF evolution moves beyond structured digital documentation toward intelligent, connected, and site-driven systems. Clinical research operations continue to expand in complexity, scale, and data volume, which drives the need for systems that not only manage documents but actively support decision-making, compliance, and workflow execution in real time.
This phase introduces deeper automation, stronger interoperability, and increased control at the site level, shaping eISF into a central operational layer within modern clinical trials.
Intelligent Automation and AI Integration
- AI-driven document classification and auto-filing based on document type and metadata
- Automated routing of documents across studies and workflows
- Data extraction from uploaded files to reduce manual entry
- Proactive alerts for expiring documents such as CVs, licenses, and training records
- Predictive identification of missing or incomplete documentation
Connected Ecosystems and Interoperability
- Direct eISF to eTMF connectivity for real-time document exchange
- Integration with CTMS for study execution alignment
- Direct data capture from EHR systems to reduce duplicate documentation
- Built-in electronic signature workflows for faster approvals
- Unified workflows across the eISF, the pharmacy site file and the QMS
Remote and Hybrid Monitoring Models
- Secure, permission-based remote access for CRAs and sponsors
- Continuous document review without dependency on site visits
- Standardised digital structures enabling instant audit readiness
- Real-time tracking of document completeness and site status
Site-Owned and Standardised Platforms
- Shift toward site-owned eISF systems used across multiple sponsors
- Reduction in sponsor-specific documentation fragmentation
- Increased standardisation across site networks and research organisations
- Scalable systems supporting multi-study and multi-site environments
eISF systems are evolving into intelligent platforms that combine document control, workflow automation, and system-wide connectivity. The focus shifts from managing files to managing documentation as an active, controlled process within clinical trial execution.
Core Features and Functions of an eISF System
| Feature and Function | What It Controls | Outcome |
| Study-Scoped Architecture | Ensures all eISF activity exists within a defined study and cannot exist independently | Maintains clear separation of data across studies and prevents cross-contamination |
| Template-Driven Structure | Defines folder hierarchy at creation stage using predefined templates | Standardised document organisation across all sites and studies |
| Document Lifecycle Control | Manages upload, versioning, locking, signing, moving, and controlled removal of documents | Ensures only valid, current documents are used throughout the study |
| Role-Based Permissions | Controls granular actions such as view, create, edit, move, delete, restrict, and sign | Enforces responsibility-based access aligned with study roles |
| Audit Trail and Activity Logging | Records every user and document action with timestamps and attribution | Provides full traceability for inspections and compliance review |
| Workspace and Metadata Control | Displays document context including study, category, version, and signature status | Improves document visibility and reduces ambiguity during review |
| Review, Approval, and Signature Control | Enables controlled workflows with electronic signatures and document state tracking | Ensures documents are reviewed, approved, and compliant before use |
| Removed Document Management | Tracks removed documents with reason, timestamp, and recovery options | Prevents data loss and ensures no undocumented deletion occurs |
| Dashboard and Oversight Metrics | Displays document counts, locked/signed status, unresolved issues, and activity logs | Enables real-time monitoring of document completeness and compliance |
| Notification and Activity Tracking | Alerts users to assignments, document changes, and pending actions | Keeps stakeholders aligned and reduces missed actions |
| Integration Across Modules | Connects eISF with the pharmacy site file, the QMS and study management modules within the system | Aligns documentation with execution, quality, and pharmacy workflows |
| System-Level Compliance Controls | Enforces template immutability, permission checks, and auditability across all actions | Maintains regulatory integrity and consistency across ongoing trials |
How eISF Works in Clinical Trial Operations?
An eISF is used daily by different roles, each performing controlled actions based on permissions. The system enforces structure, validates actions, and records every step.
The eISF works within a study that is already created in the clinical trial system. Once the study is available, a template is applied to generate the folder structure. After that, site users begin working inside this structure, and every document follows a controlled path from upload to approval.
Let us walk through a real-world multi-site study (ONC-247) to show how each role interacts with the eISF across the study lifecycle.
1. Study Setup and eISF Configuration
The study ONC-247 is already created in the system. The study manager enables eISF and selects an Oncology Phase III template.
The system generates folders such as:
- Protocol
- Regulatory
- Investigator & Staff
- Informed Consent
- Monitoring
- Safety
Users are assigned:
- Sara (Coordinator)
- Dr. Ahmed (Principal Investigator)
- John (CRA)
At this stage, the structure is fixed and ready for use.
2. Document Upload and Organisation
Sara opens the eISF and starts uploading required documents.
Examples:
- Dr. Ahmed CV → Investigator & Staff folder
- Ethics Approval Letter → Regulatory folder
- Consent Form v1.0 → Informed Consent folder
The system:
- Tags each document with study name and category
- Sets version as v1.0
- Marks status as Draft
- Records upload in audit log
The dashboard shows:
- Required documents: 25
- Uploaded: 18
- Missing: 7
3. Review and Feedback
John (CRA) logs in remotely and filters documents marked “Pending Review.”
He opens Protocol v1.0 and adds a comment:
“Signature page missing”
The eISF system:
- Saves the comment
- Notifies Sara
- Keeps document in Draft status
4. Document Update and Version Control
Sara uploads a corrected file: Protocol v1.1
The eISF system:
- Keeps v1.0 in history
- Marks v1.1 as current version
- Logs update with timestamp
Now:
- v1.1 → Active
- v1.0 → Superseded
5. Review and Approval
Dr. Ahmed opens Protocol v1.1 and reviews it. He clicks Sign.
The eISF system:
- Applies electronic signature
- Records name, date, and time
- Changes status to Approved
- Locks the document
6. Monitoring and Site Readiness
John opens the dashboard and sees:
- Required documents: 25
- Approved: 25
- Missing: 0
He confirms site readiness for activation. No manual checklist or email follow-up is needed.
7. Ongoing Study Execution
During the study, documents continue to be added. Examples:
- Monitoring Visit Report → Monitoring folder
- Updated Consent Form v2.0 → replaces v1.0
- SAE Report → Safety folder
The eISF system:
- Maintains version history
- Logs every upload, edit, and approval
- Prevents overwriting existing records
8. Audit and Inspection
A QA auditor accesses the eISF in read-only mode. As required, the auditor can open a document and see the readily-available insights:
- Uploaded by: Sara
- Reviewed by: John
- Signed by: Dr. Ahmed
- Full timeline of actions
9. Study Close-Out
At study completion:
- All documents are reviewed and approved
- Missing items are resolved
- Final versions are locked
The eISF now contains a complete document set, full audit trail, and inspection-ready records.
So, this example shows how eISF works as a controlled workflow system:
See the full site file workflow on the AQ eISF module page, or book a 30-minute demo on a live study.
Who Uses eISF in Clinical Trials?
| Role | What They Do in eISF | System Interaction |
| Principal Investigator (PI) | Reviews and approves site documents, ensures compliance with protocol and regulations | Reviews documents, applies electronic signatures, validates final versions |
| Site Coordinator / Study Coordinator | Manages day-to-day documentation at the site | Uploads documents, updates versions, organises files, responds to review comments |
| Clinical Research Associate (CRA) / Monitor | Monitors site documentation and verifies compliance | Reviews documents remotely, adds comments, tracks completeness, verifies readiness |
| Sponsor / Study Manager | Oversees study-level documentation and site readiness | Creates studies, assigns users, monitors document status and site progress |
| Contract Research Organisation (CRO) | Manages trial operations on behalf of sponsor | Oversees multiple sites, reviews documentation, ensures consistency across studies |
| Quality Assurance (QA) / Auditor | Conducts audits and ensures regulatory compliance | Accesses audit trails, reviews document history, verifies compliance during inspections |
| Regulatory Affairs Team | Ensures documentation meets regulatory submission requirements | Reviews regulatory documents, validates approvals and compliance records |
| Pharmacist / Pharmacy Team (via the pharmacy site file) | Manages pharmacy-related documentation separate from site records | Maintains drug accountability and pharmacy records in the pharmacy site file, aligned with eISF |
Benefits of Using eISF in Clinical Trials
- Faster site activation timelines
- Reduced document preparation time for monitoring and audits
- Real-time visibility of document status across the study
- Elimination of duplicate and outdated document usage
- Reduced manual workload for site staff
- Faster issue identification and resolution
- Reduced monitoring delays and site visits
- Improved accuracy and consistency of documentation
- Stronger control over user actions and responsibilities
- Complete traceability of all document activity
- Lower risk of missing or non-compliant documents
- Continuous inspection readiness throughout the study
Is eISF a Part of eTMF?
An eISF is not a subset or module of the eTMF. It is a connected but independent system that supports the eTMF by providing accurate, site-level documentation throughout the study.
The eISF operates at the site level, where investigators and site staff manage and maintain essential documents during the study. The eTMF operates at the sponsor level, where all trial documentation from every site is collected, reviewed, and archived as the official record of the trial.
The eISF and the eTMF relate as follows:
- The eISF contains site-specific documents for a single study site
- The eTMF contains documents from all sites participating in the trial
- Documents created and maintained in the eISF are transferred or synced to the eTMF
- The eTMF becomes the central repository for regulatory review and inspection
An eISF can be considered a source of documents that feed into the eTMF, but it remains a separate system with its own structure, users, and controls.
eISF vs eTMF vs Pharmacy Site File: Key Differences
The eISF manages general site-level documentation, including investigator records, approvals, and consent forms. The pharmacy site file manages pharmacy-specific documentation, including drug accountability, storage, and dispensing records. Both systems follow the same controls such as structured folders, permissions, versioning, and audit trails, but operate in separate domains. The eISF contributes site documentation to the eTMF, while the pharmacy site file contributes pharmacy documentation, forming the complete trial record at the sponsor level.
| Aspect | eISF (Electronic Investigator Site File) | eTMF (Electronic Trial Master File) | Pharmacy Site File (Electronic) |
| Primary Scope | Site-level documentation | Sponsor-level, trial-wide documentation | Pharmacy-level documentation |
| Ownership | Investigator site | Sponsor / CRO | Site pharmacy / pharmacist |
| Document Coverage | Documents specific to one site | Documents from all sites in the study | Documents related to investigational product (IP) handling |
| Purpose | Demonstrate site compliance and conduct | Demonstrate overall trial compliance and oversight | Demonstrate proper handling and accountability of study drug |
| Users | PI, coordinators, CRAs | Sponsors, CROs, regulatory teams | Pharmacists, pharmacy staff, monitors |
| Document Types | CVs, consent forms, approvals, training, monitoring records | Protocols, contracts, safety reports, site docs from all locations | Drug accountability logs, storage records, temperature logs, dispensing records |
| Level of Control | Site-controlled | Sponsor-controlled | Pharmacy-controlled |
| Lifecycle Role | Active during site execution | Active across entire trial lifecycle | Active during drug management and dispensing |
| Regulatory Role | Supports site inspection readiness | Holds the sponsor record an inspector uses to reconstruct the trial | Supports pharmacy compliance and audits |
| Data Flow | Feeds site documents into eTMF | Aggregates documents from all systems | Operates separately but aligned with site and trial activities |
| Relationship | Works alongside the eTMF and the pharmacy site file | Central system integrating all documentation | Separate but connected to site and study workflows |
Also Read: Difference Between eTMF and CTMS
What Should an Electronic Investigator Site File Include Under ICH E6(R3)?
An electronic investigator site file should include every essential record that ICH E6(R3) places with the investigator and the institution, held under the controls the guideline expects of a computerised system. Appendix C of E6(R3) is the starting point for the list. The protocol and the sponsor agreement settle the rest for each trial.
ICH E6(R3) was adopted at Step 4 on 6 January 2025 and took effect in the UK on 28 April 2026. Appendix C is titled Essential Records for the Conduct of a Clinical Trial and takes the place of the essential documents list in Chapter 8 of E6(R2). It covers how essential records are managed and how a trial team decides whether a record is essential, rather than handing over a fixed inventory. Source: ICH E6(R3), Step 4, adopted 6 January 2025, checked on 14 October 2026.
The table below groups the site-level essential records and names what an eISF has to be able to show for each group. It is a grouped view rather than a line-by-line reproduction of Appendix C.
| Record group | What sits in the site file | What the eISF must be able to show |
| Authorisations and approvals | Regulatory authorisation, research ethics committee opinion, HRA approval and the list of approved documents | Which approved version was in force on any given date |
| Protocol and amendments | Current protocol, every amendment and the signature pages | The protocol version in force when each participant was seen |
| Product information | Current and superseded investigator brochures or summaries of product characteristics | The version supplied to the site and the date it was received |
| Staff authorisation and training | Delegation log, curricula vitae, GCP and protocol training records, professional registrations | Who was authorised to perform which task, and from which date |
| Informed consent materials | Every version of the participant information sheet and the consent form | The version in use at each consent event |
| Participant and source records | Screening and enrolment logs, randomisation records, source worksheets or their electronic equivalent | That each entry is attributable, contemporaneous and not altered without a trail |
| Safety records | Serious adverse event reports, safety letters and sponsor notifications | Receipt, investigator review and onward reporting |
| Investigational product records | Receipt, storage, dispensing, return and destruction records, held in the pharmacy site file | Reconciliation from receipt to final disposition |
| Monitoring and oversight | Monitoring visit reports, follow-up letters, audit records and trial correspondence | What was reviewed, what was raised and what was closed |
| Close-out and archive | End of trial notification, the final report sent to the site and the archiving record | When the file was closed, by whom, and where it is now held |
Which System Controls Does E6(R3) Expect?
E6(R3) sets out data governance in Annex 1, section 4, and applies it to any computerised system that holds trial records. Six controls decide whether an electronic site file meets it.
- Validation for intended use. The site holds evidence that the system does what the trial relies on it to do, for the release in use.
- Version control. Superseded records stay readable and the current record is unambiguous.
- Attributable actions. Every action carries a named user and a time stamp, so the state of the file can be reconstructed for any date.
- Role-based access. Permissions follow the delegation log, and access is withdrawn when a role ends.
- Electronic signatures. Each approval is linked to an identified signatory and to the record version that was signed.
- Direct access for review. Monitors, auditors and inspectors can read the live file, including its audit trail, without an export.
AQ eISF files site records to the DIA TMF Reference Model structure and audit-trails every filing, so the site file and the sponsor trial master file reconcile zone by zone.
What Do UK Trials Add to the E6(R3) List?
UK trials carry four further duties on top of E6(R3). Each one changes what the site file has to hold, or how long it has to last.
| UK duty | What it means for the site file |
| Retention for at least 25 years | Regulation 31A of the amended UK Clinical Trials Regulations applies to trials whose application was submitted on or after 28 April 2026. The records have to stay readable and retrievable for the whole period. |
| The transitional rule | Trials applied for before 28 April 2026 keep the trial master file for five years after the trial concludes. Participant medical files still need 25 years. |
| Certified copies | A scan replaces an original only as a certified copy, and the scanning process itself is validated. MHRA guidance asks for original records or certified true copies. |
| Direct access at inspection | MHRA inspectors expect access to the file and its audit trail. A read-only inspector view removes the need to build an export under pressure. |
Sources: MHRA guidance on archiving and retention of clinical trial records and MHRA good clinical practice guidance and inspections, both checked on 14 October 2026. NHS organisations add their own information governance checks before go-live, which are set out in eISF for NHS Trusts: Electronic Investigator Site File Requirements.
How Do Hybrid Paper and Electronic Site Files Work?
Many sites run a hybrid file for part of a study. Wet-ink consent forms, delegation logs signed on paper and courier paperwork often stay physical while the rest of the file is electronic. A hybrid file is acceptable. An undeclared hybrid file is the problem, because nobody can say where a given record lives.
- Declare the index. One file index states, section by section, whether the record is held on paper, electronically, or in both places.
- One record, one authoritative place. Each record has a single master location, and any second copy is labelled as a copy.
- Certify the scans. A scan that stands in for an original is verified and certified, and the certification is itself recorded.
- Keep both halves current. A paper section with no named owner drifts exactly as a whole paper file does.
Also Read: The Investigator Site File Essential Documents Checklist (ICH-GCP Chapter 8)
Regulatory Compliance and eISF Systems
An eISF supports regulatory compliance by embedding control directly into how site documents are created, reviewed, approved, and maintained. Instead of relying on manual processes, the system enforces structure, permissions, and traceability so that every document meets regulatory expectations throughout the study lifecycle.
Regulatory Foundations
- ICH-GCP (E6). Defines the essential documents required to demonstrate trial conduct and data quality at the site level.
- 21 CFR Part 11. Requires secure electronic records, validated systems, and compliant electronic signatures.
- ALCOA+ Principles. Ensures data integrity through attributes such as attributable, contemporaneous, accurate, and complete records.
How eISF Maintains Compliance?
- Predefined Document Structure. Templates ensure documents are filed in correct categories, aligned with regulatory requirements from the start.
- Permission-Based Control. User actions such as upload, edit, review, and sign are restricted based on assigned roles and responsibilities.
- End-to-End Audit Trail. Every document action is automatically recorded with user identity, timestamp, and activity history.
- Electronic Signatures. Approvals are completed using compliant eSignatures linked to authorised users.
- Version Integrity. Each document update creates a new version, while previous versions remain preserved and traceable.
- Controlled Document Removal. No document is permanently deleted; removal is tracked with reason, timestamp, and recovery options.
- Real-Time Compliance Oversight. Dashboards highlight missing, pending, or incomplete documents, allowing immediate action.
An eISF ensures that site documentation remains complete, accurate, and continuously inspection-ready. Compliance is enforced through system controls rather than manual effort, reducing errors, improving traceability, and enabling confident audit and regulatory review at any stage of the trial.
Challenges in Implementing an eISF System
- Defining a standard folder structure that works across all studies and sites
- Translating regulatory requirements into a usable, system-driven template
- Mapping real-world site workflows into controlled digital processes
- Assigning correct roles and permissions without over-restricting or overexposing access
- Aligning responsibilities between site staff, monitors, and sponsors within the system
- Migrating legacy documents without losing structure, context, or traceability
- Maintaining version integrity during transition from uncontrolled documents
- Driving consistent document quality across different sites and users
- Eliminating parallel trackers (Excel, email) that compete with the system
- Ensuring users follow system workflows instead of bypassing them
- Managing document completeness in real time without manual follow-ups
- Handling audit expectations during early adoption phases
- Integrating eISF with CTMS, eTMF, QMS, and pharmacy site file without duplication or gaps
- Training users to understand not just how to use the system, but why controls exist
- Maintaining compliance while allowing operational flexibility
- Preventing unauthorised actions while keeping workflows efficient
- Scaling the system across multiple studies without breaking consistency
- Ensuring continuous oversight without increasing administrative burden
Also Read: What is DOA: Delegation of Authority in Clinical Research
How to Choose the Right eISF System?
It is important for CROs, sponsors, and clinical sites to assess eISF capabilities carefully, in order to support consistent workflows, role-based control, and real-time document visibility.
Key Criteria and Required Capabilities
| Criteria | What to Look For |
| Study-Scoped Architecture | Ability to create and manage eISF within individual studies with clear separation of data |
| Template-Driven Structure | Predefined folder hierarchy applied at study creation to ensure consistency |
| Document Lifecycle Control | Versioning, locking, signing, and full history tracking of documents |
| Role-Based Permissions | Granular control over user actions such as view, upload, edit, sign, and restrict |
| Audit Trail and Traceability | Automatic logging of every action with user, timestamp, and activity |
| Electronic Signatures | Compliance with 21 CFR Part 11 for approvals and certifications |
| Real-Time Document Visibility | Dashboards showing completeness, missing documents, and status tracking |
| Remote Monitoring Capability | Secure access for CRAs and sponsors to review documents without site visits |
| Data Integrity Controls | Enforcement of ALCOA+ principles across document handling |
| Controlled Document Removal | No permanent deletion, with recovery and full audit history |
| Integration Capability | Ability to connect with CTMS, eTMF, QMS and pharmacy site file records |
| Usability and Adoption | Clear interface that supports site workflows without requiring workarounds |
| Scalability Across Studies | Consistent performance and structure across multiple studies and sites |
| Compliance Readiness | System validation and alignment with regulatory requirements |
Also Read: What Is Clinical Research Software and How to Choose the Right One?
Frequently Asked Questions
What is an electronic investigator site file?
An electronic investigator site file is the validated system a research site uses to hold its essential trial records. It applies version control, role-based access, electronic signatures and a full audit trail to every record. The file stays under site control and remains the investigator part of the trial record.
What should an electronic investigator site file include under ICH E6(R3)?
It should include the essential records E6(R3) places with the investigator and the institution. Appendix C of E6(R3), Essential Records for the Conduct of a Clinical Trial, is the starting point. In practice that means approvals, the protocol and its amendments, product information, staff authorisation and training records, consent materials, participant and source records, safety records, investigational product records and monitoring records. The protocol and the sponsor agreement settle the rest for each trial.
Is the eISF part of the eTMF?
No. The eISF is a connected but separate system with its own structure, users and controls. It holds site-level records and stays under the investigator. The eTMF holds the sponsor record for the whole trial and receives site documents from the eISF.
How long must an investigator site file be kept in the UK?
Trials whose application was submitted on or after 28 April 2026 keep essential records for at least 25 years after the trial concludes, under regulation 31A of the amended UK Clinical Trials Regulations. Trials applied for before that date keep the trial master file for five years after the trial concludes. Participant medical files need 25 years either way.
Can a scanned document replace the original in an eISF?
Only as a certified copy. The scan has to be verified as holding the same information as the original, the certification has to be recorded, and the scanning process itself has to be validated. MHRA guidance asks sites to retain original records or certified true copies.
Who owns the investigator site file?
The investigator and the institution hold it. A sponsor or contract research organisation may supply the system and may be granted access to review it. Ownership of the records does not move with the software.
Does an eISF need to be validated?
Yes. E6(R3) treats a system holding trial records as a computerised system that needs validation for its intended use. The site should hold validation evidence for the release in use, and the supplier should say how each new release is covered.
Can a site run a paper and an electronic site file at the same time?
Yes, and most sites do for part of a study. The hybrid has to be declared in a single file index that states where each section is held. Each record needs one authoritative location, and any scan standing in for an original needs certifying.
AQ eISF: Controlled, Connected Investigator Site Documentation For Inspection-Ready Trials
AQ eISF is a study-scoped, template-driven system designed to manage investigator site documentation with structured control, role-based permissions, and full audit traceability. It ensures that documents are organised, reviewed, approved, and maintained within a controlled environment throughout the study lifecycle. The system provides real-time visibility into document status and completeness, supports remote monitoring, and keeps site documentation continuously aligned with regulatory requirements and inspection readiness.
What AQ eISF Offers:
- Predefined, template-driven folder structure for consistent document organisation
- Study-scoped environment with clear separation of data across studies
- Role-based permissions controlling who can view, edit, approve, or sign documents
- Complete document lifecycle management with version control and status tracking
- Built-in audit trail capturing every document action with timestamp and user
- Electronic signatures for controlled approvals, designed to support 21 CFR Part 11 requirements
- Real-time dashboards for document completeness and activity tracking
- Secure remote access for site teams, monitors, and sponsors
- Controlled document removal with full recovery and audit history
- Integration with AQ CTMS, AQ eTMF, AQ QMS and AQ Pharmacy for aligned trial operations
Book a live demo to see how AQ eISF manages site documentation with control, visibility, and continuous inspection readiness.
