Laboratory protocol versus an experiment record is the difference between a reusable recipe and dated proof that this run happened. The protocol tells you how the method is supposed to go. The record tells you what this operator did on this date, with which lots, and which files. Filing the recipe is not that proof. ELN versus LIMS splits narrative from aliquot state. Sign-off readiness assumes the object is already a run. SOP-versus-protocol naming is a later page. This page only splits recipe from run.
The Protocol Is Not Proof That This Run Happened
The search is difference between protocol and experiment record. Keep the words stable. A protocol is a versioned method: abstract steps that can be reused. An experiment record is contemporaneous documentation of one execution. Schröder and colleagues draw the same line with different nouns. Protocol templates, they write, encode instructions and do not necessarily carry lot numbers, timestamps, instrument parameters, or the research data. Documentation of the actual wet-lab experiment does. This page calls that second object an experiment record, even when some papers call the run an “ELN protocol.” The object split matters more than the synonym.
A signed protocol PDF still does not prove today's incubation happened. It proves which method was intended.
Recipe Versus Dated Run Evidence
| Dimension | Laboratory protocol | Experiment record |
| Time posture | Prospective: how the method should run | Retrospective: what this run did |
| Typical contents | Versioned steps, reagents as classes, expected parameters | Lots, passage numbers, actual times, deviations, raw files |
| Identity | A reusable method ID | A dated entry ID plus operator |
| What it can prove later | Which method was intended | That the run, the deviation, and the data exist |
| What it cannot prove | That this operator followed it today | That the method is the controlled SOP for the organization — a later naming page |
Template-structure guides often separate a linked SOP from a procedure log. That is the same split in form language. Do not treat those guides as a Zetta feature list. Do not treat them as the SOP-versus-protocol page.
What Each Object Can Prove
When a result is challenged, the protocol answers “which recipe was supposed to run.” Only the record answers “what was pipetted, when, and from which lot.” A PCR protocol can list a 58 °C anneal. The record must say whether this run used 58 °C, which polymerase lot, and which gel file. A deviation that exists only in memory cannot be recovered from a clean PDF. A record that never links the protocol version cannot tell a reviewer which recipe was intended. You need both objects. You sign the run. Filing the protocol first is allowed when the method is still being written and no wet run has started. The moment a tube is opened, the dated record must exist, even if the protocol version is still a draft pointer. Leaving only a signed recipe after the run is the failure this page names. Paper versus digital cost is a different decision. Traceability is not a cheaper page.
File Both; Sign Only the Run
Create or link the protocol, then create the dated record that points at that version and stores lots, times, deviations, and files. ZettaNote can hold both objects after they are distinct. It is the notebook, not the subject of a naming contest. Product language about audit trails and 21 CFR Part 11 support describes software features. Software does not, by itself, make a laboratory Part 11 complete. If the only artifact in the folder is a protocol PDF with a signature block, you have filed a recipe. You have not recorded the run.
Frequently Asked Questions
Is filing a protocol PDF the same as writing an experiment record?
No. The PDF is the recipe. The record is the dated run with lots, times, and files.
Is this the same distinction as SOP versus protocol?
No. SOP versus protocol is a later naming page about controlled versus working methods. This page is recipe versus run evidence.