What to Include in a Lab Protocol for Reproducible Experiments

A lab protocol is a written, step-by-step procedure that records an experiment's purpose, materials, conditions, and acceptance criteria, so that another researcher can execute the experiment and judge its results without asking the author. The protocol is the experiment's contract: it states what was intended, what was used, and what counts as success, before the data exists.

Protocols fail in two familiar ways: they are too thin to reproduce, or so overloaded with prose that nobody reads them. The sections below are the minimum content that separates a protocol a stranger can follow from a set of personal notes, organized so each section answers one question a reader will ask at the bench.

Purpose and Scope: The Question the Protocol Answers

The protocol opens with the question it exists to answer and the boundary of what it covers. This is not background literature; it is a two or three sentence statement of the experiment's goal, the sample or system it applies to, and what decision the result will support. A protocol whose purpose is unclear gets adapted in unplanned ways, because readers fill the gap with their own assumptions.

The scope statement also names what the protocol does not cover, such as upstream preparation or downstream analysis steps that live in other protocols. Referencing those sibling protocols by identifier, rather than summarizing them, keeps each document focused and the set of documents navigable.

Materials With Identifiers, Not Just Names

The materials section lists reagents, consumables, and instruments with enough identity to reorder or locate them: catalog numbers, lot numbers where the lot matters, and instrument identifiers. "Taq polymerase" is a family; the catalog number and lot is what ties the protocol to the actual chemistry used. Lot numbers earn their place for reagents where lot-to-lot variation changes results, which the protocol should flag explicitly.

Consumables and equipment get the same treatment in condensed form, with model or identifier rather than prose. The test of the materials section is whether someone could place the orders and find the instruments without asking a single question of the author.

Step-by-Step Procedure With Decision Points

The procedure is numbered, specific, and written for execution at the bench: quantities, temperatures, times, and the order of operations. Each step says what to do, not what the step means, because interpretation belongs in the surrounding sections. Steps that branch, "if the pellet is small, then...", state their condition and both paths explicitly rather than leaving the reader to improvise.

Decision points deserve visible treatment, because they are where protocols silently diverge: two people can follow the same written steps and take different branches because the branch condition was vague. The protocol should make every branch a written one, with the criterion that selects it, so the executed path can be reconstructed from the record afterward.

Controls and Acceptance Criteria: Deciding Success in Advance

The protocol names its controls and what each one proves: the positive control that the assay can detect the signal, the negative control that the signal is not an artifact, and any internal standards the measurement depends on. Each control gets its expected result stated in advance, so a failed control is recognizable as a failed control rather than a mystery to be investigated after the fact.

Acceptance criteria extend the same discipline to the experiment itself: the measurable conditions the results must meet to be trusted, such as amplification efficiency ranges, signal thresholds, or purity cutoffs, written before the data is collected. Criteria set in advance are what allow a clean pass or fail call; criteria invented after seeing the data are not criteria but post hoc justification, and the protocol's job is to prevent exactly that. For teams that want protocols and experiment records connected, Zettalab keeps protocol documentation linked to the records executed against them.

Safety, Disposal, and Reference Notes

Hazards and disposal requirements belong in the protocol where the material or step appears, not in a generic preamble, because the reader encounters them at the moment of use. The level of detail follows the hazard: a sentence for standard precautions, more for procedures with specific risk. References to supplier documentation or safety sheets are pointed to, not duplicated.

The protocol closes with its own maintenance trail: the version, the author, the reviewers, and the date, with a short change log for revisions. A protocol is a living document, and its change history is part of its scientific record, because results are always tied to the protocol version they were produced under.

FAQ

What is the difference between a lab protocol and an SOP?

A lab protocol records how a specific experiment is performed and what its results must satisfy, while a standard operating procedure describes a recurring process the lab must perform consistently, often for compliance. The boundary is flexible in practice, but the distinction matters for management: protocols carry the experiment's scientific judgment, and SOPs carry the lab's process requirements, with different review and change control.

How detailed should a lab protocol be?

Detailed enough that a competent colleague can execute the experiment and judge the results without asking the author, and no more. Every quantity, time, temperature, and branch condition must be present, while background theory and generic context should stay out or move to references. The test is a stranger test: hand the protocol to someone who has never run it, and see where their questions appear.

Who should review a lab protocol before it is used?

At least one reviewer who will use it and one who will judge its results, typically an experienced colleague plus the person responsible for the downstream decision. The reviewer checks executability, not just correctness: whether the steps can actually be performed with the listed materials and whether the acceptance criteria are measurable. A signed review turns the protocol from a draft into the version results are tied to.

How should deviations from a protocol be handled?

Deviations are recorded at the moment they happen, in the experiment record, with what was changed and why, and they do not silently edit the protocol. If the deviation proves better, it becomes a proposed protocol revision through the normal change process. The rule is one-directional: records reference protocol versions, and protocols change only through deliberate revision.

Why do acceptance criteria have to be set before the experiment?

Because criteria set after seeing the data are not criteria but rationalizations, and the difference determines whether a result can be trusted. Pre-registered criteria force the team to decide in advance what evidence would be convincing, which is exactly the protection against cherry-picking that reproducibility depends on. The criteria go in the protocol, and the experiment record documents the verdict against them.

Should a protocol include the data analysis steps?

The protocol should state the acceptance criteria and reference the analysis procedure, but detailed analysis belongs in a linked analysis protocol or the experiment record. Keeping execution and analysis as separate, cross-referenced documents keeps each readable. What must not happen is leaving the analysis undefined, because results without a defined analysis path invite post hoc choices. For teams that want protocols and experiment records connected, ZettaNote within the Zettalab workspace supports structured documentation with templates and cross-references.

Conclusion

A protocol earns its name when it contains the six elements that make an experiment reproducible: a stated purpose, identified materials, an executable procedure with explicit branches, controls and acceptance criteria set in advance, safety notes where they apply, and its own version history. Written this way, the protocol becomes the lab's stable reference point, the document every result is judged against. To keep protocols and experiment records connected, explore Zettalab's ZettaNote ELN.