What to Include in an Electronic Experiment Record: Essential Fields for Research Documentation

An electronic experiment record should include the structured information that makes the experiment reproducible, searchable, and reviewable: identification metadata, objective, materials and reagents, protocol with any deviations, results with attached data files, analysis and conclusions, and review sign-off. A record that omits any of these sections creates a documentation gap — sometimes minor (a missing date), sometimes critical (a missing primer sequence that prevents anyone from repeating the experiment).

For molecular biology and biotech research teams, defining what each experiment record must contain — and configuring the ELN to enforce those requirements — is the foundation of standardized, trustworthy documentation. This guide walks through each essential section and the fields it should include.

Experiment Identification Metadata

The identification section makes the record findable. Required fields:

• Experiment title: A descriptive title that distinguishes this experiment from others — not "PCR" but "PCR amplification of EGFP insert for pCMV-EGFP cloning (colony screen)."
• Unique experiment ID: Auto-generated by the ELN; should be sequential and immutable.
• Date: The date the experiment was performed. Auto-filled from the system clock but editable if documenting a past experiment.
• Researcher: Auto-filled from login identity. If multiple researchers performed the experiment, list all contributors.
• Project: Selected from a controlled vocabulary — links this experiment to its project context for search and filtering.
• Experiment type: Selected from a controlled vocabulary (cloning, PCR, transformation, sequencing, cell culture, etc.). This field enables filtering all experiments of a given type across projects.

Objective

A 1-3 sentence statement of what the experiment aims to determine or achieve. This field is the most commonly under-written section in experiment records, but it is essential for future readers: a record that describes what was done without explaining why leaves the reader guessing about the experimental context. Good objective: "Determine whether the pCMV-EGFP construct (v3, colony #7) contains the correct EGFP insert without mutations, by Sanger sequencing of the insert and flanking vector regions." Poor objective: "Sequence pCMV-EGFP."

Materials and Reagents

List everything used in the experiment that could affect the result:

• Plasmids and constructs with unique identifiers and source (lab stock, Addgene ID, commercial vendor)
• Primers with full sequences (5' to 3'), names, and purpose
• Enzymes with vendor, catalog number, and units used
• Competent cells with strain name, source, and preparation date if made in-house
• Kits with vendor and catalog number
• Key reagents with lot numbers where lot-to-lot variability could affect results
• Antibiotics with working concentration

Protocol

Reference the standard protocol if one exists ("Cloning Protocol v3.1, step 4-7"), and document every deviation from the standard. If no standard protocol exists, record the full step-by-step. Deviations are the most important part of this section — they are what distinguish this experiment from all others using the same protocol and they are often the explanation for unexpected results. Record: incubation times that differed from the protocol, enzyme amounts that were adjusted, cycling parameters that were modified, and any steps that were repeated or omitted.

Results and Data Attachments

Summarize the results in text, and attach the raw and processed data files that support the summary. For molecular biology experiments, typical attachments include: gel images (labeled with lane contents), sequence chromatograms, alignment results comparing observed vs. expected sequence, colony counts, instrument output files, and plasmid maps. Each attached file should have a one-line description of what it represents in the experiment context. Attach files at documentation time — not later — to prevent the "missing attachment" gap.

Analysis and Conclusions

Interpret the results: Did the experiment succeed, fail, or produce ambiguous results? If it succeeded, what is the next step? If it failed, what is the likely cause and what will be tried next? This section closes the loop — without it, the record is a collection of data without interpretation, and future readers must reconstruct the analysis themselves. For constructs that pass verification: state explicitly that the construct is verified and ready for use, and record the construct's unique identifier and storage location.

Review and Sign-Off

The review section records that someone other than the experimenter has checked the record for completeness and scientific soundness. Fields: reviewer name, review date, review outcome (approved, revisions requested, rejected), and reviewer comments. For GLP-ready labs, the review should include an electronic signature meeting 21 CFR Part 11 requirements.

FAQ

How detailed should the materials section be?

Detailed enough that a colleague could order the same materials and repeat the experiment without asking you questions. For commercial reagents, record the vendor and catalog number. For plasmids and constructs, record the unique lab identifier (not "the EGFP plasmid" but "pCMV-EGFP_v3, lab stock #P0421"). For primers, record the full sequence — a primer name like "F1" is meaningless without the sequence or a link to a shared primer database. For enzymes, record the vendor and units used. Lot numbers should be recorded for reagents where lot variability matters (antibodies, competent cells, enzymes for critical steps).

Should negative and inconclusive results be documented?

Yes — with the same level of detail as positive results. A negative result ("the cloning failed — no colonies on the experimental plate") documented with the conditions that produced it prevents colleagues from repeating the same failed approach. An inconclusive result ("colony PCR showed bands of unexpected sizes") documented with the gel image and analysis provides the starting point for troubleshooting. Labs that only document successful experiments accumulate survivorship bias in their records — they know what worked but not what did not, which is often equally valuable information.

How do ELN templates enforce experiment record completeness?

ELN templates can enforce completeness by marking certain fields as required — the researcher cannot save or submit the record until those fields contain valid data. Required fields should include: experiment title, date, researcher, project, experiment type, objective, and at least one result file attachment or text result. Optional fields capture additional detail for experiments that need it without burdening every record. The review workflow provides a second completeness check — a reviewer should return incomplete records to the researcher before approving. Zettalab's ZettaNote ELN supports configurable required fields within experiment record templates, helping labs enforce documentation standards without manual policing.

Conclusion

Every electronic experiment record should answer five questions for a future reader: What was done? Why was it done? How was it done? What was the result? What does it mean and what comes next? The sections described in this guide — identification, objective, materials, protocol, results, analysis, and review — are structured to answer those questions systematically.

Configure the ELN to enforce the minimum required fields through templates, use the review workflow as a completeness check, and iterate on the template based on which fields researchers consistently fill — and which they consistently skip. Explore ZettaNote's experiment record templates and review workflows for research teams building complete, searchable, and audit-ready experiment documentation.