Design history file: assembled during the project, not after it
A DHF is a compilation, not a document. Teams that treat it as something to write at the end discover the records they needed were never created.
A TMF assembled at the end is a TMF assembled from memory. Inspectors ask when documents were filed, not only whether they exist.
The trial master file is the collection of essential documents that allows the conduct of a clinical trial and the quality of the data produced to be evaluated. It exists so that somebody who was not there can reconstruct what was done, by whom, under what approvals, and whether the protocol was followed.
Its defining requirement is not completeness at the end but contemporaneity throughout. Documents are supposed to be filed as they arise, so that at any moment the file reflects the state of the trial. A file assembled in the weeks before an inspection may contain everything and still fail, because the timeliness of filing is itself part of what is assessed.
The most useful thing a TMF can do is distinguish between a document that has not arisen yet, one that will never arise for this trial, and one that should exist and does not. Files that record only what is present cannot answer the question an inspector actually asks, and the team ends up reconstructing the expected list under pressure. Define it at study start and maintain it as the trial changes.
Electronic trial master file systems used to hold the file are regulated software: they require validation, audit trails and controlled access. That is a genuine constraint, not a vendor talking point, and it is why the file cannot simply live in a shared drive.
Completeness alone is a lagging and flattering measure. The pair worth tracking is completeness against the expected document list and timeliness — the interval between a document being dated and being filed. A trial with ninety-five per cent completeness and a median filing lag of two months has a problem that the completeness figure conceals, and it is the lag that inspection findings usually name.
Ettex Records keeps the study-level records that sit outside a validated system — the expected-document plan, the filing standard, quality review results and the archiving plan — with dates visible, and Ettex Docs holds the working drafts of documents before they are approved and filed. The instrument the study collects data on is covered in case report form, and the participant-facing document in informed consent form.
To be explicit: this is not an eTMF and must not be used as one. The essential documents of a trial belong in a validated system with audit trails; what this covers is the planning and oversight around it, and none of it is regulatory advice.
The collection of essential documents allowing the conduct of a trial and the quality of its data to be evaluated independently.
Documents are expected to be filed as they arise. A file assembled before an inspection may be complete and still fail on filing lag.
A defined structure agreed before filing starts, commonly based on the widely used reference model, with a clear sponsor and site split.
Electronic systems holding essential documents are regulated software requiring validation, audit trails and controlled access.
A DHF is a compilation, not a document. Teams that treat it as something to write at the end discover the records they needed were never created.
The certificate that only says “passed” is the one that will not help you. As-found readings and stated uncertainty are what make it evidence.
Most CMDB projects fail the same way — an ambitious model, a good first load, and eighteen months later a database nobody trusts enough to act on.