Experiment Setup Runbook — reproducible execution steps

Purpose and scope

This runbook standardizes experiment setup and execution to reduce avoidable variability, prevent manual errors, and improve reproducibility. Use it for routine laboratory runs, pilot experiments, or whenever consistent execution matters. Tailor the templates below to your protocol, instrument, and local safety rules before first use.

Who should use this

Operators, lab technicians, experiment leads, QA/quality personnel, and anyone responsible for executing or checking experimental runs.

Roles and responsibilities

• Operator: Execute the steps, record data, flag anomalies.
• Run Lead / PI: Confirm protocol version, acceptance criteria, and authorize deviations.
• Quality / Lab Manager: Review run logs, ensure calibration and reagent records are current.

Prerequisites & preparations

• Approved protocol and current protocol version displayed.
• Equipment warmed up and calibrated within acceptable window.
• Reagents and consumables verified (lot numbers, expiry dates).
• Samples labeled with unique IDs and logged in sample register.
• Data storage path and backup procedure verified.
• Required safety PPE available and used.

Pre-run checklist (verify before starting)

• Protocol version: record
• Run ID created: record
• Operator name and contact: record
• Equipment IDs and calibration timestamps checked
• Environmental conditions within allowed range (temperature, humidity)
• Reagent lot numbers and expiry dates verified
• Consumables (tips, tubes, filters) stock confirmed
• Waste containers and LOTO status verified (if applicable)
• Data destination and backup available
• Emergency shutoff and contact list known

Standardized setup & execution procedure (ordered steps)

1. Initialize run record (5–10 min)

   Create Run ID, note protocol version, operator, date/time, and sample count in the run log. Record initial environmental and equipment status.

2. Prepare equipment (10–30 min depending on instrument)

   Power on instruments, wait required warm-up time, verify calibration status, load method files. If instrument passes self-checks, proceed; otherwise follow instrument troubleshooting checklist.

3. Prepare reagents and samples (10–20 min)

   Bring reagents to required temperature, mix if required, aliquot as specified. Verify reagent lot numbers and expirations against the log.

4. Perform control checks (5–15 min)

   Run positive and negative controls or blanks as defined. Confirm control results are within acceptance criteria before running samples.

5. Execute primary run (variable)

   Follow stepwise protocol actions exactly. At each sub-step, record timestamps, operator initials, instrument readings, and any deviations. Use the data logging fields below for consistency.

6. Immediate validation and anomaly flagging (5–15 min)

   Check that raw output is complete and that key metrics meet acceptance rules. If anomalies occur, pause the run and consult the troubleshooting section.

Data logging fields (standard entries — adapt as needed)

Record these fields in the run log or electronic lab notebook for every run. Use consistent formats and units.

• Run ID
• Protocol and version
• Date and start/end times
• Operator name and initials
• Instrument ID(s) and firmware version
• Calibration check timestamp
• Sample IDs / sample manifest
• Reagent lot numbers & expiry
• Environmental conditions (T, RH) with measurement time
• Control results (values and pass/fail)
• File names / storage paths for raw data and exports
• Deviations & anomalies (description, time, immediate action)
• Operator comments

Example logging row (CSV-friendly)

RunID,Protocol_v,Date,StartTime,EndTime,Operator,InstrumentID,CalDate,SampleIDs,ReagentLots,TempC,Control1,Control2,RawDataPath,Anomalies,Comments

Post-run cleanup and data export

• Stop instruments according to manufacturer guidance and allow cool-downs if required.
• Export raw data to the agreed storage location and create a checksum or manifest to verify integrity.
• Back up data to secondary storage or cloud per local policy.
• Clean and return consumables and reagents; document used lots and remaining volumes.
• Dispose of waste following safety and regulatory rules; log waste disposition if required.
• Complete run log with end time, summary result (pass/fail), and sign-off (operator and run lead).

Troubleshooting quick guide

• Instrument won’t start: Check power, fuses, and emergency stop. Confirm firmware and connection. If unresolved, tag instrument as out-of-service and notify maintenance.
• Controls fail: Do not proceed with samples. Re-run controls with fresh reagents; if failure persists, stop and escalate.
• Unexpected signal/noise: Check consumables, filters, and sample prep. Re-run a portion of the run if feasible to isolate cause.
• Data missing/incomplete: Verify data path and instrument memory. Attempt export again; if unrecoverable, document loss and notify data steward.
• Reagent contamination suspected: Stop, quarantine reagents, and run negative controls. Replace suspect reagents before resuming.

Acceptance criteria and stop conditions

• Control values within protocol-specified ranges.
• No critical instrument errors during run.
• All required raw data files present and verified.
• If any critical criterion fails, stop the run, record the failure, and notify the run lead.

Versioning, change control, and continuous improvement

Record the runbook version used for each run. Any protocol deviations or suggestions for improvement should be captured in the run log. Periodically review run logs to identify recurring sources of variability and update this runbook accordingly.

How to adapt this template

Keep a local copy of this runbook and tailor checklists, expected durations, control criteria, and data fields to your assay and instruments. When adapting, preserve the core logging fields so runs remain comparable across time and teams.

Quick links and attachments

• Protocol document (link or filename)
• Instrument SOPs and maintenance records
• Calibration certificates
• Data storage and backup policy