Instrument files in lab records are the raw outputs, images, spectra, chromatograms, and data files that instruments produce during an experiment, and deciding which ones belong in the record is a reproducibility and audit question, not just a file management question. A record that describes an experiment without its instrument outputs is an incomplete record, because the conclusions cannot be verified against the raw data that produced them.
Most labs keep instrument files somewhere but do not have a clear rule about which files belong in the record, which are linked versus embedded, and how long they must be retained. This guide covers which instrument files belong in lab records, how to manage them, and what a complete record needs.
Which Files Belong in the Record
The rule is simple: any instrument output that supports a conclusion in the record belongs with the record. This includes the raw data files, not just the processed or summarized versions. A gel image that was quantified should have the original image file; a sequencing run that confirmed a clone should have the trace files or FASTQ; a spectrometer reading that produced a concentration should have the raw output. The raw data is what lets a reviewer or a future team member re-analyze, check, or reproduce the result.

Processed data alone is not sufficient. A graph derived from raw instrument output cannot be checked against the raw data if the raw data is absent. For GLP and similar quality frameworks, the expectation is that raw data is retained and retrievable, not just the processed result.
Linking Versus Embedding
| Approach | Best for | Risk |
| Direct linking | Large files, NGS data, instrument databases | Link breaks if storage moves |
| Embedding | Small files, images, key traces | Record size grows; format may age |
| Hybrid | Embed key outputs, link full raw data | Requires discipline to maintain both |
For most labs, a hybrid approach works best: embed the key instrument outputs that directly support each conclusion, and link the full raw dataset so it remains available for re-analysis. The link must be stable over the retention period; a link that breaks when storage is reorganized is worse than no link.
Retention and Readability
Instrument files must be retained for the same period as the record and must remain readable throughout that period. Proprietary instrument formats that become unreadable when the instrument software is upgraded create a silent compliance risk. Labs with long retention obligations should consider exporting instrument data to open, stable formats alongside the native files, so the data remains accessible even if the instrument vendor's software is no longer available.
How Zettalab Supports Instrument File Management
For labs that need instrument files linked to experiment records with retention and readability planning, Zettalab connects molecular biology tools with ELN-style documentation and team file storage. ZettaNote supports file attachments and cross-references, and ZettaFile supports permission-managed storage, so a team can attach instrument outputs to records directly. To manage instrument files inside a connected lab workspace, explore Zettalab's cloud-based R&D lab platform.
FAQ
Which instrument files belong in a lab record?
Any instrument output that supports a conclusion in the record belongs with the record, including the raw data files, not just processed versions. A gel image, a sequencing trace, a spectrometer reading, the raw output is what lets a reviewer verify the result. Processed data alone is not sufficient for reproducibility or audit.
Should I link or embed instrument files?
Embed small, key files that directly support conclusions; link large datasets for full re-analysis. The link must remain stable over the retention period. A hybrid approach preserves both accessibility and record size.
How long must instrument files be retained?
For the same retention period as the record they support, and they must remain readable throughout. Proprietary formats that become unreadable over time create compliance risk. Exporting to open formats alongside native files protects against format obsolescence.
Conclusion
Which instrument files belong in lab records is a reproducibility question: the raw outputs that support conclusions must travel with the record, linked or embedded, and remain readable for the full retention period. A connected R&D workspace that supports file attachments and retention planning, such as Zettalab, fits labs whose records must hold up under review. To manage instrument files inside a structured lab workspace, explore Zettalab's cloud-based R&D lab platform.