A measurement finishes, a result appears on the touchscreen, and within seconds someone presses print. The page goes into a folder, the Excel file lands on a shared drive, and the job is considered archived. Nobody scheduled a meeting to design this workflow. It assembled itself out of convenience, and it now functions as the de facto record-keeping system in a great many laboratories. The question worth asking is not whether printing and exporting are useful — they clearly are — but whether the habit preserves the *evidence* behind a number or only the appearance of it.
How Paper, PDFs and Spreadsheets Became the Default Lab Archive
The habit persists because each format solves a different, local problem. A PDF is the closest thing to a universal renderer: it looks the same on a reviewer’s laptop, in a submission portal and on a tablet in the cold room. A printed page requires no software at all and survives a dead hard drive. An Excel file is editable, chartable and familiar, which is exactly why analysts keep it as the working copy. Individually, each choice is sensible. Stacked together, they become institutional memory by accident rather than design.
Instrument firmware has encouraged the pattern. Modern platforms are built to deliver finished documents rather than raw data streams: full-page reports, label formats, and cryo labels printed over USB or a lab network, with exports to PDF and Excel available at the touch of an icon. That convenience is genuinely valuable in a busy core facility, where a queue of users is waiting and no one has time to design a data model. The path of least resistance leads straight to a printer.
The scale of what accumulates is easy to underestimate. Consider a full scan completed in seconds — the NanoPhotometer NP80, for instance, describes measure times of “as little as 2.5 seconds” in its body text and 2.5 – 4 seconds in its technical table. A single afternoon can generate dozens of files; a year across several instruments generates thousands. Multiply that by the number of groups sharing a core, and the archive becomes a large, unindexed pile of similarly named documents.
What gets lost first is context. A PDF generated from a microvolume measurement may or may not display the path length used (0.67 mm or 0.07 mm), the corresponding dilution factor (15 or 140), the blank reference, the method version or the instrument serial number. A printout certainly will not. Yet these are precisely the details a reviewer, a collaborator or a future version of yourself will need in order to interpret an absorbance value or a concentration. The trio of printer, PDF and spreadsheet captures the outcome while quietly discarding the provenance.
What the Habit Preserves — and What It Silently Loses
The strengths are real and should not be dismissed. PDFs and paper are software-independent: they remain readable when a vendor discontinues a file format, when a licence lapses, or when an instrument is decommissioned. A printed report is immune to ransomware and to the shared drive that someone reorganised without telling anyone. Excel, meanwhile, keeps analysis alive — standard curves can be refitted, kinetics re-plotted, and concentration calculations checked against the original values. For teaching and troubleshooting, an editable file is invaluable.
The weaknesses are structural. A spreadsheet cell has no memory: overwrite a value and the previous one is gone unless the system providing it kept a trail. A PDF is a *picture of a table*, not a dataset — units are not enforced, decimal separators travel badly, and text extraction from a poorly tagged report can silently corrupt numbers during a migration. Printouts are single copies, vulnerable to fading, coffee and theft, and thermal labels on tubes stored at −80 °C have a limited readable life. Add version sprawl — report_final_v3_corrected.pdf — and the archive becomes difficult to audit even when nothing has actually gone wrong.
Regulatory expectations sharpen the point. A PDF dropped onto a network share is not automatically an electronic record in the sense that 21 CFR Part 11 requires; audit trails, access control and electronic signatures have to be generated and protected by the system that created the data. The Implen NanoPhotometer NP80 illustrates the distinction well: the base instrument exports to Excel and PDF and prints reports, labels and cryo labels, while an optional CFR21 software package is described as supporting FDA 21 CFR Part 11 compliance through user management, access control, electronic signatures, data integrity, security and audit trail functions, with IQ/OQ options for GMP/GLP/GxP environments. In other words, the archiving habit and the compliant record are two different things, and only one of them is produced by pressing print.
The instrument layer is not the obstacle. Many of the systems now in service — microvolume and cuvette UV-Vis Spectrophotometers such as the NanoPhotometer NP80, for example — already offer network file-server access to their internal storage, 1D and 2D barcode reader compatibility, and direct output to PDF and Excel, alongside printing to AirPrint/IPP-compatible devices, HP universal driver printers and DYMO label printers. The missing piece is usually policy, not hardware.
Building an Archiving Habit That Still Makes Sense in Five Years
The first decision is to name a system of record. Everything else follows from it. If the instrument’s own storage or its regulated data package is the primary record, then PDFs, printouts and spreadsheets are derivatives — useful copies that must never be edited in place and never allowed to drift from the original. If a LIMS or electronic lab notebook is the system of record, then the export is a transport format. What fails is the undefined middle ground, where three copies exist and no one can say which one is authoritative.
A practical habit rests on three rules. First, keep one untouched, machine-readable file per measurement or per batch, written once and stored read-only. Second, generate the human-readable report from that file rather than retyping values by hand, so the PDF and the data cannot disagree. Third, maintain a lightweight index that maps a sample identifier to its files — a manifest spreadsheet is enough, provided it lives somewhere stable and is backed up with the data it describes.
Metadata deserves explicit attention because it is the part that decays invisibly. A workable minimum set includes the instrument serial number and model, the method name and version, path length and any dilution applied, the blank or reference used, operator identity, date and time, sample ID, and physical storage location. On the NanoPhotometer NP80, several of these are captured automatically by the NPOS environment, which runs on a built-in computer with 64 GB of internal storage and can be reached from a computer on the lab network. Implen also describes NPOS as a proprietary system “immune to known malicious software” and notes that the instrument does not permit internet browsing while still allowing control from PCs, tablets and smartphones — useful properties, though they do not substitute for network permissions and retention rules on the destination server.
Labels are the other half of the archive. A tube in a freezer is only as traceable as the barcode on it, so printing cryo labels at the moment of measurement, with an identifier that matches the exported file name, closes the loop between physical sample and digital record. Barcode readers then turn a manual search into a lookup.
Finally, test the habit rather than assuming it works. Pull a random file from three years ago, open it on a machine that does not have the instrument software installed, and check whether the numbers and their context are still intelligible without expert help. Run that exercise annually, write the naming convention and the retention rule into an SOP that survives staff turnover, and state plainly in that SOP which copy is the record and which are convenience copies. An archiving habit becomes trustworthy only when it is documented well enough that the next person can follow it without asking.
A Sofia-born astrophysicist residing in Buenos Aires, Valentina blogs under the motto “Science is salsa—mix it well.” Expect lucid breakdowns of quantum entanglement, reviews of indie RPGs, and tango etiquette guides. She juggles fire at weekend festivals (safely), proving gravity is optional for good storytelling.
