Blog
Experiment Procedure Example: Guide to Reproducible Science
A scientist often realizes the procedure is weak at the worst possible moment. Gloves are on, the timer is running, the sample is already thawed, and the record says something useless like “mix well,” “incubate,” or “measure as usual.” That kind of note doesn't just slow the bench down. It creates doubt about what occurred.
A strong experiment procedure example does more than tell someone what should happen. It records what must be controlled, what must be observed, and what to do when reality stops matching the plan. That distinction matters in every lab, from qPCR setup to HPLC sample prep, because reproducibility depends on procedures that another scientist can repeat without chasing unwritten assumptions.
Table of Contents
- The Foundation of a Reproducible Experiment Procedure
- Annotated Example a Molecular Biology Workflow
- Annotated Example an Analytical Chemistry Method
- Your Reusable Procedure Template and Pre-Run Checklist
- From Text to Truth Capturing Procedures in Real-Time
- Troubleshooting Common Procedure Documentation Gaps
The Foundation of a Reproducible Experiment Procedure
A procedure is not a checklist pasted into an ELN. It is the operational version of the experiment design. If another competent scientist cannot reproduce the work from the document alone, the procedure is incomplete.
According to Scribbr's overview of experimental design essentials, a rigorous procedure should specify the independent and dependent variables, define the hypothesis, include a control group, and state exactly how subjects or samples are assigned to treatment conditions. Controlled experiments also require systematic manipulation of the independent variable, precise measurement of the dependent variable, and active control of confounders. That same guidance also stresses that the procedure should be written precisely enough that another person can repeat the work, including exact materials or equipment, sample selection, number of trials, and documentation methods.
What a procedure must contain
The fastest way to improve an experiment procedure example is to stop treating the procedure section as a prose summary. It needs named components.
- Objective and hypothesis. State what the experiment is testing and what result would support or reject that hypothesis.
- Independent and dependent variables. Name what is being changed and what is being measured.
- Controls. Identify negative, positive, vehicle, blank, or untreated controls as applicable.
- Assignment logic. State how samples, subjects, wells, tubes, or injections are assigned.
- Materials and equipment. Record exact reagents, instruments, and any identifiers the lab relies on.
- Measurement plan. State what will be measured, when, and by what method.
- Confounder control. Note anything that must be kept stable to protect interpretation.
A good companion habit is to separate instructional language from record language. “Add reagent B” is instruction. “Add reagent B, record lot, time of addition, and visible color change within the next observation window” is procedure-grade documentation.
For teams refining SOPs or internal methods, Verbex's guide on protocols in science is useful because it reinforces the distinction between what the operator does and what the record must preserve.
What makes a procedure repeatable
The bench usually fails on missing detail, not missing intelligence. Scientists already know how to pipette, vortex, and incubate. What they don't know from a weak record is which tube was equilibrated first, whether the reagent was cloudy before mixing, whether the plate edge was avoided, or whether a timer drifted because another task interrupted the run.
Practical rule: If a future reviewer would ask “exactly how?”, the answer belongs in the procedure.
A repeatable procedure usually includes the following bench-level details:
| Element | What to write |
|---|---|
| Sample handling | How samples were selected, labeled, stored, thawed, mixed, or discarded |
| Equipment setup | Instrument used, settings selected, calibration status if relevant |
| Sequence | Exact order of steps, especially where order affects the outcome |
| Observation timing | When visual, physical, or analytical observations are made |
| Documentation method | Notes, measurements, sketches, photos, or other record forms |
| Replication details | Number of runs, repeats, or technical and biological replicates |
That level of precision feels slow when someone writes it after the fact. It is much easier when captured as the work happens.
Annotated Example a Molecular Biology Workflow
Molecular biology procedures fail without overt warning. The assay may still run, the amplification curves may still appear, and the plate may still look tidy. But if the master mix identity, control placement, or thermal program was recorded loosely, the result becomes harder to trust later.
Example procedure for a qPCR run
Below is a practical experiment procedure example for a qPCR gene expression assay. The values are intentionally qualitative where lab-specific settings normally vary.
Objective
Assess relative target amplification in prepared cDNA samples using a qPCR assay with standards and controls.
Materials
qPCR master mix, forward primer, reverse primer, nuclease-free water, cDNA samples, no-template control material, plate seals, optical qPCR plate, calibrated pipettes, filtered tips, qPCR instrument.
Procedure
- Thaw cDNA samples, primers, and qPCR master mix according to lab handling requirements. Mix each gently and briefly collect contents before use.
- Prepare a reaction map before pipetting. Assign standards, controls, and unknown samples to specific wells.
- Prepare a master mix for all planned reactions plus excess volume appropriate to the lab's setup practice.
- Dispense master mix into each designated well.
- Add cDNA samples to assigned wells. Add no-template control material to control wells.
- Seal the plate, centrifuge briefly if that is part of the lab's standard handling, and inspect for bubbles or sealing defects.
- Load the plate into the thermocycler and run the predefined qPCR program for the assay.
- Save raw output files under the sample naming convention used by the lab.
- Review amplification curves, melt data if applicable, and control performance before interpretation.
- Record any repeat wells, exclusions, or plate issues in the experiment record.
The reaction map is part of the procedure, not an attachment added later. If the map is missing, the run is harder to audit and harder to repeat.
The point of this example isn't to provide one universal qPCR method. It's to show how the record should read. A scientist reading it later should know what was loaded, where it was loaded, what controlled the run, and what output was reviewed.
What the record must capture during the run
Many molecular biology records often go thin in this respect. The planned steps are written. The executed details are not.
A stronger qPCR entry captures items like these in real time:
- Reagent identity. Master mix name, primer set identity, and any kit or internal labeling details the lab uses.
- Plate logic. Where standards, controls, and unknowns were placed, and whether anything changed during setup.
- Handling deviations. Late-thawed sample, replaced seal, reloaded well, suspected bubble, or repeat dispense.
- Run context. Instrument name, method file used, and whether the operator accepted or questioned any control result.
A future scientist should be able to tell the difference between “the assay was performed” and “this exact plate was assembled in this exact way.”
A short visual explainer helps here because qPCR procedures are easier to understand when plate setup and decision points are visible.
What usually does not work is generic shorthand. “Loaded plate.” “Ran program.” “Looks good.” Those phrases save a few seconds and cost clarity later.
Annotated Example an Analytical Chemistry Method
Analytical chemistry records break for different reasons. The scientist may document manual steps carefully but omit the instrument conditions that made the separation meaningful. In chromatography, that gap is serious. A sample prep note without mobile phase, injection sequence, or system suitability context is not a complete method record.
Example procedure for HPLC sample preparation
This experiment procedure example uses a common HPLC sample preparation and run setup pattern.
Objective
Prepare samples for HPLC analysis and document instrument conditions needed for interpretable chromatographic data.
Materials
Sample matrix, diluent, volumetric glassware or validated equivalent, syringe filters if used by the method, vials and caps, mobile phase components, HPLC system, column specified by the method, standards, blanks.
Procedure
- Confirm the sample identity and required analytical method before preparation.
- Prepare fresh mobile phase according to the method and label each component or reservoir clearly.
- Condition the HPLC system using the column and method-defined setup.
- Prepare calibration standards and blank solutions according to the method record.
- Prepare the analytical sample by dilution, extraction, or transfer as specified for the matrix.
- Filter or clarify the sample if the method requires it, and transfer to a labeled vial.
- Program the instrument method, including run conditions and sequence structure.
- Run blank, standards, system suitability injections, and analytical samples in the defined order.
- Review chromatograms for peak shape, retention behavior, baseline quality, and integration issues.
- Record any reinjections, sample re-preparation, instrument interruptions, or method edits.
The critical point is that sample preparation and run setup belong in the same procedural story. Splitting them across disconnected records often hides the reason a chromatogram looks unusual.
What analysts often forget to document
Analytical teams usually remember the sample weight or dilution. They often forget the details that explain whether the run itself was sound.
A better HPLC record captures:
| Area | What should appear in the record |
|---|---|
| Mobile phase prep | Composition, preparation date, and anything unusual during mixing or degassing |
| Instrument method | Method file name or identifier, detector mode, column identity, and key run settings |
| Sequence logic | Blank placement, standard placement, system suitability order, sample order |
| Sample prep | Dilution path, filtration step, transfer details, and any re-preparation |
| Review notes | Baseline behavior, integration edits, reinjections, carryover concerns, unusual peaks |
Bench reality: A chromatogram can look wrong for reasons that began at sample prep, at instrument setup, or during review. The procedure should preserve all three.
What doesn't work is treating the chromatographic run as a black box. “Analyzed by HPLC per method” is fine for a meeting slide. It is poor documentation for a record that must stand on its own months later.
Your Reusable Procedure Template and Pre-Run Checklist
Most scientists don't need another ornate SOP template. They need a simple structure that catches the details people forget under time pressure. A reusable template does that by making key fields impossible to skip.
Reusable experiment procedure template
The template below works well as a starting point for biology, chemistry, QC, and general wet-lab use. It can be copied into an ELN, adapted into an internal form, or standardized with tools such as a protocol builder. Teams looking for a ready-made format can adapt the structure from this laboratory protocol template.
| Section | Content / Key Questions to Answer |
|---|---|
| Title | What experiment is being performed |
| Objective | What question is being tested |
| Hypothesis | What outcome is expected and why |
| Independent variable | What is being changed |
| Dependent variable | What is being measured |
| Controls | Which controls are included and why |
| Sample assignment | How samples or subjects are assigned to groups, wells, tubes, or runs |
| Materials | Which reagents, consumables, and reference materials are used |
| Equipment | Which instruments or devices are used |
| Setup conditions | What must be configured before starting |
| Procedure steps | What happens, in exact order |
| Observation points | When to check, inspect, measure, or document |
| Data capture | What values, images, notes, or files must be recorded |
| Decision points | When to stop, repeat, annotate, or escalate |
| Deviations | What changed from plan during execution |
| Results summary | What happened in the run |
| Review notes | What needs follow-up, repeat work, or interpretation |
Pre-run checklist
A short pre-run check catches more procedural failures than most post-run cleanup.
- Method is readable. No vague phrases remain. If a step says “mix,” the method also says how.
- Controls are ready. Positive, negative, blank, untreated, or vehicle controls are prepared and labeled.
- Assignments are fixed. Plate map, vial order, sample grouping, or sequence order is written before starting.
- Capture method is ready. Notebook, ELN entry, worksheet, or voice capture workflow is open before hands are busy.
- Observation timing is defined. The record states when to inspect, not just what to inspect.
- Failure rules exist. The method says when to repeat, when to annotate, and when to stop.
A template is useful only if the lab uses it under pressure. That usually means keeping it short enough to complete and specific enough to trust.
From Text to Truth Capturing Procedures in Real-Time
A procedure on paper is a prediction. The experiment at the bench is the event. Those two versions drift apart quickly once a tube cracks, a run pauses, a baseline becomes unstable, or a scientist notices something odd that doesn't fit the original plan.
The missing piece in many records is not scientific competence. It is contemporaneous capture. The scientist notices the deviation, plans to write it down later, then loses the exact order, timing, or wording.
Why procedures fail during execution
A useful warning comes from a contact-angle teaching note that highlights a common weakness in procedural writing. As described in the Johns Hopkins contact angle experiment guide, procedural content often shows the happy path but gives little guidance on what to do when the procedure becomes ambiguous or a measurement is unstable. The same source supports including decision points for error handling, because procedural quality depends on documenting deviations, corrections, and repeatability conditions.
That principle applies well beyond contact angle work. A procedure is incomplete if it records only the nominal path and ignores the branch points.
For example:
- Measurement instability. The result fluctuates and the scientist must decide whether to repeat or annotate.
- Visual ambiguity. The baseline, band, peak, or droplet edge cannot be interpreted cleanly.
- Execution drift. Incubation runs long, the plate is resealed, the sample order changes, or one injection is repeated.
A procedure becomes trustworthy when it records not only what the scientist planned to do, but also how the scientist handled uncertainty.
Teams that want stronger bench records often benefit from organizing notes around experiment sections rather than a single running paragraph. A practical reference is this guide on how to organize research notes, especially for labs trying to keep procedures, observations, and deviations connected.
A Voice-to-ELN workflow for deviations and timing
A Voice-to-ELN workflow fits naturally. Instead of stopping to type with gloved hands or trying to reconstruct events later, the scientist captures spoken bench notes as work happens, with timestamps tied to the moment of observation.
That approach works well for details such as:
- Unexpected observations. Color shift, precipitation, foam, turbidity, delayed dissolution.
- Timing changes. Incubation started late, wash extended, reaction paused, reinjection requested.
- Decision points. Automatic fit rejected, repeat measurement taken, control flagged for review.
- Sequence details. Which sample was handled first, what was reloaded, what was skipped.
One option in this category is Verbex, a private, on-device Voice-to-ELN app for scientists that helps capture spoken experiment notes into structured sections such as Objective, Materials, Procedure, Observations, and Results, with review before finalization. In practice, that kind of workflow helps scientists preserve the scientific moment while staying focused on the bench.
What doesn't work is assuming memory will preserve order, timing, and uncertainty. It usually preserves the conclusion, not the path.
Troubleshooting Common Procedure Documentation Gaps
Even careful scientists leave holes in the record when the procedure language is weak. Most of those gaps are fixable with small habits and sharper wording.
Gap one vague action words
Words like “prepare,” “mix,” “wash,” and “analyze” look harmless. They also hide the exact action.
Fix: replace abstract verbs with operational instructions.
Write “invert tube until solution appears uniform” or “rinse vessel, then inspect for visible residue before proceeding.” The record becomes clearer immediately.
Gap two missing deviations
Many records describe the intended method and omit the actual interruptions. That creates a false sense of smooth execution.
Fix: add a deviation line wherever the run branches.
If a well was repeated, a sample was re-filtered, or an automatic fit was manually corrected, write that event at the time it happened.
Good records don't pretend the bench was tidy. They explain how the scientist handled the untidy parts.
Gap three broken timing records
A note that says “incubated” without start time, end time, or observation point is weak documentation. Timing is often part of the method, not background context.
Fix: record timing as part of the procedure itself.
Use timer-linked notes, timestamped entries, or structured observation fields so the record preserves sequence instead of summarizing it later.
Gap four missing context
A result without context is hard to interpret. Scientists often capture the readout but skip the conditions that made the readout possible.
Fix: attach context to the action.
That means sample identity, relevant instrument or setup condition, and any unusual visual or environmental note that influenced interpretation.
A practical cleanup routine before final review is useful:
- Read for ambiguity. If another scientist could ask “what exactly happened here,” rewrite the line.
- Read for omissions. Check whether controls, assignments, and deviations are visible.
- Read for sequence. Make sure the order of work is preserved.
- Read for audit value. Confirm that the record shows what was done, what changed, and what was observed.
Better procedure writing rarely comes from making records prettier. It comes from making them more faithful.
A practical next step is to use a documentation workflow built for real bench conditions. Verbex is a private, on-device Voice-to-ELN app for scientists. It helps researchers capture experiment notes by voice as work happens, organize them into scientific sections, review the structured draft, and export ELN-ready records. Built around truth-first documentation, privacy by default, and human control, it fits labs that want to capture procedures, deviations, timing, and observations closer to the moment of work.