WHY ENGLISH?
Turn an experiment into a traceable research record
Use the routes to prepare the entry, capture work as it happens, preserve evidence, explain interpretation and hand the experiment to the future.
Open the full contents · See the How English Works hub
Full contents
Set the context
Record the method
Capture evidence
Interpret carefully
Close the loop
Practice and next steps
Practice and next steps
Practice and next steps
Practice and next steps
Practice and next steps
A laboratory notebook entry is the contemporaneous record of what a researcher planned, did, observed, changed and concluded on a particular piece of work. English matters because memory compresses detail. A precise entry preserves the small decisions, settings, failures and file relationships that make an experiment understandable later.
Students searching for how to write a lab notebook, electronic laboratory notebook best practices, experimental records, reproducibility, research notes or scientific record keeping often expect a neat retrospective summary. A useful notebook is different from a polished laboratory report: it records the evolving work, including deviations and unsuccessful attempts, while the evidence is still close.
The current NIH intramural electronic laboratory notebook policy defines an ELN as a system for creating, storing, retrieving and sharing electronic research records while meeting records-management and security requirements. The NIH Electronic Lab Notebooks resource page provides best-practice materials for trainees and principal investigators. These are NIH intramural resources; students and researchers must follow their own institution, laboratory, funder, ethics and intellectual-property rules.
Use the notebook map project, owner, date, time, page, objective, hypothesis, protocol, version, sample, material, lot, instrument, setting, calibration, environment, procedure, observation, measurement, unit, file, code, calculation, deviation, error, correction, decision, interpretation, uncertainty, witness, signature, review and next step. The purpose is a reliable research trail, not a performance of certainty.
Use the approved notebook
Prepare the entry around the paper or electronic system authorised for the project before memory begins to compress the work.
Traceability weakens when personal notes become the only research record.
Use the approved system and confirm ownership, access and retention rules.
Record example. A trainee records work in the institutional ELN rather than a private note app The entry now has a stable home.
Did You Know? NIH describes an electronic laboratory notebook as a system for creating, storing, retrieving and sharing electronic research records while meeting records-management and security requirements. This is why the paper or electronic system authorised for the project needs a precise, dated record.
Identify the project
Record the study, protocol, work package and responsible team as the experiment unfolds. Precise nouns and verbs keep action attached to evidence.
Reproduction becomes guesswork when an entry begins with experiment today.
Write the actual sequence and use stable project names and identifiers.
Method example. The entry links to the approved protocol and dataset plan Another trained reader can follow the work.
Do not clean away deviations simply because the result looks usable.
Date and time the work
Preserve evidence for the temporal sequence needed to reconstruct actions and conditions without replacing raw data with a convenient summary.
Auditability disappears when entries are backfilled without marking when they were written.
Link files, settings and record contemporaneously and identify later additions.
Evidence example. A late clarification carries its own date and points to the original entry The claim can now be checked.
Keep sample codes, file identifiers and versions consistent across systems.
Write a useful title
Interpret the experiment, variable and stage described in one searchable line with bounded certainty and a visible next step.
Learning stops when titles repeat sample test for months.
Separate observation, inference and include the distinguishing purpose or condition.
Decision example. Enzyme stability after third freeze-thaw cycle identifies the question The notebook supports the next experiment.
Close the entry through the approved signature, review and cross-link process.
State the objective
Prepare the entry around the immediate question this entry is designed to answer before memory begins to compress the work.
Traceability weakens when a broad project aim replaces today's decision.
Use the approved system and write a bounded and observable objective.
Record example. The run tests whether calibration remains within the stated range The entry now has a stable home.
Finish the setup with author, date, project and protocol references.
Record the hypothesis appropriately
Record the expected relationship or prediction when the method uses one as the experiment unfolds. Precise nouns and verbs keep action attached to evidence.
Reproduction becomes guesswork when a hypothesis is invented after results are known.
Write the actual sequence and date the prediction and distinguish exploratory work.
Method example. An exploratory screen is labelled exploratory rather than forced into confirmatory language Another trained reader can follow the work.
Did You Know? NIH describes an electronic laboratory notebook as a system for creating, storing, retrieving and sharing electronic research records while meeting records-management and security requirements. This is why the expected relationship or prediction when the method uses one needs a precise, dated record.
Reference the protocol version
Preserve evidence for the exact approved procedure or method used without replacing raw data with a convenient summary.
Auditability disappears when the entry says standard protocol without an identifier.
Link files, settings and link version, date and accessible location.
Evidence example. Protocol P-17 version 4 governs the extraction steps The claim can now be checked.
Keep sample codes, file identifiers and versions consistent across systems.
Describe deviations
Interpret the difference between planned and actual procedure with bounded certainty and a visible next step.
Learning stops when small changes disappear because the experiment seemed successful.
Separate observation, inference and record what changed, why and who authorised it.
Decision example. Incubation lasted three extra minutes after an equipment restart The notebook supports the next experiment.
Close the entry through the approved signature, review and cross-link process.
Identify samples
Prepare the entry around the stable codes, source and relevant preparation state before memory begins to compress the work.
Traceability weakens when names or tube positions become the identifier.
Use the approved system and use approved codes and preserve the mapping securely.
Record example. Sample S042-A is distinguished from its diluted aliquot The entry now has a stable home.
Finish the setup with author, date, project and protocol references.
Record materials and lots
Record the reagents, consumables and batches that can affect results as the experiment unfolds. Precise nouns and verbs keep action attached to evidence.
Reproduction becomes guesswork when only the product family is recorded.
Write the actual sequence and capture supplier, catalogue and lot where relevant.
Method example. A new antibody lot is traceable when signal intensity changes Another trained reader can follow the work.
Do not clean away deviations simply because the result looks usable.
Record preparation
Preserve evidence for the concentrations, calculations, dates and conditions used to make materials without replacing raw data with a convenient summary.
Auditability disappears when a solution is described as usual mix.
Link files, settings and show quantities, units and final volume.
Evidence example. The buffer calculation and pH adjustment are recorded beside preparation time The claim can now be checked.
Did You Know? NIH describes an electronic laboratory notebook as a system for creating, storing, retrieving and sharing electronic research records while meeting records-management and security requirements. This is why the concentrations, calculations, dates and conditions used to make materials needs a precise, dated record.
Identify instruments
Interpret the equipment, configuration and asset identifier used with bounded certainty and a visible next step.
Learning stops when the model name is treated as sufficient.
Separate observation, inference and record instrument ID and relevant module.
Decision example. Microscope M-03 with camera C-11 links the image to the actual system The notebook supports the next experiment.
Close the entry through the approved signature, review and cross-link process.
Check calibration status
Prepare the entry around the evidence that measurement equipment was fit for use before memory begins to compress the work.
Traceability weakens when calibrated is asserted without a date or result.
Use the approved system and cite the calibration record and pre-run check.
Record example. The balance verification passed with the recorded standard before weighing The entry now has a stable home.
Finish the setup with author, date, project and protocol references.
Capture software and settings
Record the version, parameters and configuration shaping collection or analysis as the experiment unfolds. Precise nouns and verbs keep action attached to evidence.
Reproduction becomes guesswork when default settings are assumed stable.
Write the actual sequence and record version and export the configuration.
Method example. Acquisition software version and exposure settings accompany the image series Another trained reader can follow the work.
Do not clean away deviations simply because the result looks usable.
Describe environmental conditions
Preserve evidence for temperature, humidity, light or other conditions relevant to the method without replacing raw data with a convenient summary.
Auditability disappears when room conditions are ignored until a result changes.
Link files, settings and record only variables with plausible influence.
Evidence example. A temperature excursion is noted during incubation The claim can now be checked.
Keep sample codes, file identifiers and versions consistent across systems.
Write steps in sequence
Interpret the actual order, timing and branching of work with bounded certainty and a visible next step.
Learning stops when the method is rewritten from memory at the end.
Separate observation, inference and record actions as they occur with timestamps where useful.
Decision example. A wash was repeated before the imaging step and appears in order The notebook supports the next experiment.
Did You Know? NIH describes an electronic laboratory notebook as a system for creating, storing, retrieving and sharing electronic research records while meeting records-management and security requirements. This is why the actual order, timing and branching of work needs a precise, dated record.
Use precise verbs
Prepare the entry around the physical action performed on the material or system before memory begins to compress the work.
Traceability weakens when handled or processed hides the operation.
Use the approved system and name measured, mixed, centrifuged, filtered or imaged.
Record example. The sample was centrifuged at a stated force rather than spun down The entry now has a stable home.
Finish the setup with author, date, project and protocol references.
Use complete units
Record the magnitude and unit attached to every quantitative value as the experiment unfolds. Precise nouns and verbs keep action attached to evidence.
Reproduction becomes guesswork when bare numbers rely on local habit.
Write the actual sequence and write units and distinguish mass, force and speed.
Method example. Centrifugal force is recorded in g with duration Another trained reader can follow the work.
Do not clean away deviations simply because the result looks usable.
Record observations directly
Preserve evidence for the sensory or instrument-visible event noticed during work without replacing raw data with a convenient summary.
Auditability disappears when interpretation replaces what was seen.
Link files, settings and describe appearance before assigning a cause.
Evidence example. A cloudy layer formed after mixing; contamination remains a hypothesis The claim can now be checked.
Keep sample codes, file identifiers and versions consistent across systems.
Capture unexpected results
Interpret the anomalies, failures and surprises that may reveal the mechanism with bounded certainty and a visible next step.
Learning stops when only successful runs enter the notebook.
Separate observation, inference and record the event and immediate response.
Decision example. A blank well shows signal and triggers a contamination check The notebook supports the next experiment.
Close the entry through the approved signature, review and cross-link process.
Link raw data
Prepare the entry around the immutable source files supporting the entry before memory begins to compress the work.
Traceability weakens when screenshots become the only retained evidence.
Use the approved system and use stable paths, identifiers and checks.
Record example. The entry cites the original image folder and run identifier The entry now has a stable home.
Did You Know? NIH describes an electronic laboratory notebook as a system for creating, storing, retrieving and sharing electronic research records while meeting records-management and security requirements. This is why the immutable source files supporting the entry needs a precise, dated record.
Name files consistently
Record the convention connecting samples, runs and versions as the experiment unfolds. Precise nouns and verbs keep action attached to evidence.
Reproduction becomes guesswork when final-new2 cannot be traced.
Write the actual sequence and apply the project naming rule.
Method example. Run date and sample code appear in every exported filename Another trained reader can follow the work.
Do not clean away deviations simply because the result looks usable.
Record data transfers
Preserve evidence for the movement from instrument to approved storage without replacing raw data with a convenient summary.
Auditability disappears when files are copied without checking completeness.
Link files, settings and note destination and verification.
Evidence example. A checksum confirms the transfer before local deletion The claim can now be checked.
Keep sample codes, file identifiers and versions consistent across systems.
Reference code and scripts
Interpret the analysis logic applied to raw or derived data with bounded certainty and a visible next step.
Learning stops when manual transformations are invisible.
Separate observation, inference and identify repository commit or version.
Decision example. The notebook links to the exact script commit used for the figure The notebook supports the next experiment.
Close the entry through the approved signature, review and cross-link process.
Show calculations
Prepare the entry around the formula, inputs, units and rounding used for derived values before memory begins to compress the work.
Traceability weakens when a final concentration appears without working.
Use the approved system and write the calculation or link a controlled sheet.
Record example. Dilution factors are checked against final volume The entry now has a stable home.
Finish the setup with author, date, project and protocol references.
Preserve intermediate states
Record the meaningful outputs between raw data and final result as the experiment unfolds. Precise nouns and verbs keep action attached to evidence.
Reproduction becomes guesswork when only the final graph remains.
Write the actual sequence and retain steps needed to audit transformation.
Method example. A cleaned table is linked to the exclusion log and raw export Another trained reader can follow the work.
Did You Know? NIH describes an electronic laboratory notebook as a system for creating, storing, retrieving and sharing electronic research records while meeting records-management and security requirements. This is why the meaningful outputs between raw data and final result needs a precise, dated record.
Record exclusions
Preserve evidence for the data points or samples removed and the stated reason without replacing raw data with a convenient summary.
Auditability disappears when outliers vanish from the final analysis.
Link files, settings and apply the planned rule and keep the record.
Evidence example. A damaged sample is excluded under a pre-stated criterion The claim can now be checked.
Keep sample codes, file identifiers and versions consistent across systems.
Separate result and interpretation
Interpret the measured outcome versus the explanation offered for it with bounded certainty and a visible next step.
Learning stops when a plausible mechanism is written as fact.
Separate observation, inference and use evidence and confidence language.
Decision example. Signal decreased; photobleaching is one supported possibility The notebook supports the next experiment.
Close the entry through the approved signature, review and cross-link process.
Compare with controls
Prepare the entry around the positive, negative, blank or reference conditions that bound meaning before memory begins to compress the work.
Traceability weakens when a treatment value is read in isolation.
Use the approved system and record whether controls behaved as expected.
Record example. The positive control passed while the blank failed The entry now has a stable home.
Finish the setup with author, date, project and protocol references.
Record uncertainty
Record the measurement limits, variability and unresolved ambiguity as the experiment unfolds. Precise nouns and verbs keep action attached to evidence.
Reproduction becomes guesswork when precision in display is mistaken for certainty.
Write the actual sequence and note repeatability, detection limits and assumptions.
Method example. A value near the detection threshold is not treated as exact Another trained reader can follow the work.
Do not clean away deviations simply because the result looks usable.
Avoid rewriting history
Preserve evidence for the preservation of original entries and visible corrections without replacing raw data with a convenient summary.
Auditability disappears when an error is silently overwritten.
Link files, settings and use the system's correction method with reason.
Evidence example. The incorrect sample code remains readable beside the dated correction The claim can now be checked.
Did You Know? NIH describes an electronic laboratory notebook as a system for creating, storing, retrieving and sharing electronic research records while meeting records-management and security requirements. This is why the preservation of original entries and visible corrections needs a precise, dated record.
Explain missing information
Interpret the reason a field, file or measurement is absent with bounded certainty and a visible next step.
Learning stops when blank space is left for later guessing.
Separate observation, inference and state not measured, not applicable or unavailable.
Decision example. Humidity was not recorded because the method did not require it The notebook supports the next experiment.
Close the entry through the approved signature, review and cross-link process.
Record decisions
Prepare the entry around the choice made from evidence during the work before memory begins to compress the work.
Traceability weakens when the next step appears without rationale.
Use the approved system and write decision, basis and owner.
Record example. The team repeats the run because the blank control failed The entry now has a stable home.
Finish the setup with author, date, project and protocol references.
Record communication
Record the material instruction or interpretation received from a collaborator as the experiment unfolds. Precise nouns and verbs keep action attached to evidence.
Reproduction becomes guesswork when verbal changes leave no trace.
Write the actual sequence and summarise and link the authorised source.
Method example. A supervisor approves the protocol deviation in the ELN Another trained reader can follow the work.
Do not clean away deviations simply because the result looks usable.
Use attachments carefully
Preserve evidence for the files, photos and instrument reports embedded or linked to the entry without replacing raw data with a convenient summary.
Auditability disappears when attachments have no label or context.
Link files, settings and caption each artefact and preserve its original.
Evidence example. A chromatogram states sample, run and instrument The claim can now be checked.
Keep sample codes, file identifiers and versions consistent across systems.
Protect confidential information
Interpret the personal, proprietary or security-sensitive content within the record with bounded certainty and a visible next step.
Learning stops when the notebook becomes a convenient copy of every identifier.
Separate observation, inference and minimise and use controlled references.
Decision example. Participant names stay outside the analytical notebook The notebook supports the next experiment.
Did You Know? NIH describes an electronic laboratory notebook as a system for creating, storing, retrieving and sharing electronic research records while meeting records-management and security requirements. This is why the personal, proprietary or security-sensitive content within the record needs a precise, dated record.
Respect intellectual property
Prepare the entry around the ownership, disclosure and witness rules relevant to inventions before memory begins to compress the work.
Traceability weakens when public sharing occurs before review.
Use the approved system and follow institutional and sponsor procedures.
Record example. A potentially patentable method is recorded and reviewed before conference disclosure The entry now has a stable home.
Finish the setup with author, date, project and protocol references.
Sign or attest entries
Record the mechanism that marks authorship and completion as the experiment unfolds. Precise nouns and verbs keep action attached to evidence.
Reproduction becomes guesswork when a typed name is assumed equivalent in every system.
Write the actual sequence and use the approved signature workflow.
Method example. The ELN audit trail records author and completion time Another trained reader can follow the work.
Do not clean away deviations simply because the result looks usable.
Use witness review where required
Preserve evidence for the independent confirmation that the record is understandable and complete without replacing raw data with a convenient summary.
Auditability disappears when a colleague signs without reading.
Link files, settings and follow the actual witness role and timing.
Evidence example. A witness can locate raw data and follow the method The claim can now be checked.
Keep sample codes, file identifiers and versions consistent across systems.
End with next steps
Interpret the immediate action, pending check or decision needed after the entry with bounded certainty and a visible next step.
Learning stops when the record stops at a confusing result.
Separate observation, inference and name owner, trigger and planned date.
Decision example. A repeat run waits for replacement reagent arrival The notebook supports the next experiment.
Close the entry through the approved signature, review and cross-link process.
Cross-link related entries
Prepare the entry around the chain between preparation, experiment, analysis and repeat before memory begins to compress the work.
Traceability weakens when each day becomes an isolated page.
Use the approved system and use stable references in both directions.
Record example. The failed run links to its corrective repeat and reagent preparation The entry now has a stable home.
Did You Know? NIH describes an electronic laboratory notebook as a system for creating, storing, retrieving and sharing electronic research records while meeting records-management and security requirements. This is why the chain between preparation, experiment, analysis and repeat needs a precise, dated record.
Review for completeness
Record the final check that another trained person can reconstruct the work as the experiment unfolds. Precise nouns and verbs keep action attached to evidence.
Reproduction becomes guesswork when neat formatting is mistaken for completeness.
Write the actual sequence and test identifiers, units, files and deviations.
Method example. A colleague can locate every sample and raw file Another trained reader can follow the work.
Do not clean away deviations simply because the result looks usable.
Export and preserve correctly
Preserve evidence for the authorised retention and disposition path for the record without replacing raw data with a convenient summary.
Auditability disappears when a PDF export is assumed to preserve all audit history.
Link files, settings and follow the ELN and records policy.
Evidence example. The institution retains the controlled ELN record after a trainee leaves The claim can now be checked.
Keep sample codes, file identifiers and versions consistent across systems.
Use the notebook to learn
Interpret the patterns across successful, failed and ambiguous experiments with bounded certainty and a visible next step.
Learning stops when records are consulted only during disputes.
Separate observation, inference and review deviations and recurring conditions.
Decision example. Repeated drift after warm-up leads to a better calibration schedule The notebook supports the next experiment.
Close the entry through the approved signature, review and cross-link process.
Hand over the work
Prepare the entry around the context a new researcher needs to continue safely and accurately before memory begins to compress the work.
Traceability weakens when knowledge leaves with the original author.
Use the approved system and create a linked orientation entry.
Record example. The handover identifies active protocols, open questions and authoritative files The entry now has a stable home.
Finish the setup with author, date, project and protocol references.
Capture instrument state, calibration and software context
Record instrument state as the experiment unfolds. Precise nouns and verbs keep action attached to evidence.
Reproduction becomes guesswork when the result names a machine but omits calibration status, configuration or software version.
Write the actual sequence and link the current calibration record, settings export and control result.
Method example. Microscope M-14, objective 40x, firmware 3.8 and calibration record CAL-221 are identified beside the image set Another trained reader can follow the work.
Did You Know? NIH describes an electronic laboratory notebook as a system for creating, storing, retrieving and sharing electronic research records while meeting records-management and security requirements. This is why instrument state needs a precise, dated record.
Distinguish planned repeats from selective reruns
Preserve evidence for repeat rationale without replacing raw data with a convenient summary.
Auditability disappears when an inconvenient result is silently rerun until a preferred pattern appears.
Link files, settings and record the decision rule, every run and the reason for repetition.
Evidence example. Run 2 was repeated because the pre-registered positive-control threshold failed; both files remain linked The claim can now be checked.
Keep sample codes, file identifiers and versions consistent across systems.
Document sample custody and storage transitions
Interpret sample custody with bounded certainty and a visible next step.
Learning stops when location and handling change without a traceable handover.
Separate observation, inference and record container code, quantity, condition, person, time and destination.
Decision example. Aliquot S17 moved from freezer F2 rack C4 to F5 rack A1 at 16:20 with seal intact The notebook supports the next experiment.
Close the entry through the approved signature, review and cross-link process.
Connect calculations to raw observations
Prepare the entry around calculation provenance before memory begins to compress the work.
Traceability weakens when a spreadsheet value appears without formula, unit conversion or source cells.
Use the approved system and preserve the formula, units, source range and checked output.
Record example. Concentration uses the linked calibration curve v3, dilution factor 10 and absorbance file R44.csv The entry now has a stable home.
Finish the setup with author, date, project and protocol references.
Record negative and inconclusive results usefully
Record negative evidence as the experiment unfolds. Precise nouns and verbs keep action attached to evidence.
Reproduction becomes guesswork when a null result is reduced to 'did not work' and loses its conditions.
Write the actual sequence and state the tested range, controls, detection limit and next decision.
Method example. No signal above the validated detection limit appeared from 1–50 ng while both controls passed Another trained reader can follow the work.
Do not clean away deviations simply because the result looks usable.
Prepare an entry for independent review
Preserve evidence for review readiness without replacing raw data with a convenient summary.
Auditability disappears when the author can explain the experiment orally but the record cannot stand alone.
Link files, settings and run a completeness check and invite a reviewer to trace one claim.
Evidence example. A colleague follows Figure 3 back to sample S17, raw file R44.csv, protocol P9 and the signed deviation note The claim can now be checked.
Did You Know? NIH describes an electronic laboratory notebook as a system for creating, storing, retrieving and sharing electronic research records while meeting records-management and security requirements. This is why review readiness needs a precise, dated record.
A worked example
A student runs a protein assay and later writes: Test worked mostly, one weird result, see spreadsheet. The note omits sample codes, reagent lot, plate layout, instrument settings, raw-file location, control behaviour and the reason one value disappeared.
The reconstructed entry identifies the project and objective, links protocol version, lists sample and reagent codes, records the actual timing and reader settings, points to raw data, shows the dilution calculation, describes the failed blank, records the exclusion decision and schedules a repeat with fresh reagent.
English preserves the experiment's state. Observed is not inferred, corrected is not erased, raw is not final and not measured is not zero. Those distinctions make the notebook useful for the next decision, the next researcher and the later paper.
A practical checklist
- Approved notebook used
- Project, author and date clear
- Objective and protocol version stated
- Samples, materials and instruments traceable
- Settings and units complete
- Actual sequence and deviations recorded
- Raw data and code linked
- Calculations and exclusions visible
- Observation separated from interpretation
- Corrections preserve history
- Signature or review completed
- Next step and related entries linked
Advice for students, parents and young adults
Students can practise with one school experiment: write enough that a classmate could reproduce the setup without asking what you meant. Include the unsuccessful step; it often teaches more than the polished result.
Parents can encourage a simple habit—date, purpose, action, observation, file, next step—without reading confidential research material. The goal is reliable thinking, not surveillance.
A notebook entry does not replace an approved protocol, ethics record, safety procedure, data management plan, laboratory report or intellectual-property review. Use the current institutional system and specialist requirements.
Frequently asked questions
Is a lab notebook the same as a lab report?
No. The notebook is the contemporaneous working record. A report later presents selected methods, results and interpretation for a defined audience.
Should failed experiments be recorded?
Yes. Record what happened, relevant conditions and evidence. Failure can prevent repetition and reveal the mechanism.
Can I correct an entry?
Yes, using the approved method that preserves the original, identifies the correction and records who made it and when.
How much detail is enough?
Enough for a trained reader to understand what was done, locate the evidence, reproduce the work where appropriate and see deviations and decisions.
May I use a personal notebook app?
Only if your institution or project authorises it. Research records can have ownership, security, retention and audit requirements.
When should an entry be completed?
As close to the work as practical. Later additions should be clearly dated and linked rather than presented as contemporaneous.
The deeper English lesson
Laboratory-notebook English is temporal-and-procedural language. Stable nouns identify research objects, precise verbs preserve action, units constrain numbers, evidential labels protect uncertainty and cross-links turn separate entries into a research history.
Useful next reading
Continue with explaining scientific evidence, writing a research data management plan, reading a laboratory test report, reading an academic integrity policy, and the How English Works.