Back
Feature

Protocols

Version-controlled SOPs for your team

Standardize procedures across every member of your lab. Protocols are searchable, version-controlled, and directly linked to the experiments that use them — no more emailing PDFs.

app.nextlabs.io/protocols/7

Overview

Dashboard
Experiments
Protocols
Experiment Runs
Inventory
Samples
Calendar
Inbox2
Storage
Integrations

PCR Standard v2

Standard PCR protocol for bacterial colony screening

Reagent Setup

Prepare buffers & primers

PCR Mix Prep

Master mix + template DNA

Thermocycler Run

35 cycles · 94/58/72°C

Gel Electrophoresis

1 % agarose · 90 V · 35 min

Imaging & Analysis

UV transilluminator · ImageJ

Thermocycler Run

Description

Run 35 cycles94°C / 30s denaturation → 58°C / 30s annealing → 72°C / 60s extension. Final extension 72°C / 5 min. Hold at 4°C.

Parameters

Cycles35
Denaturation94°C / 30s
Annealing58°C / 30s
Extension72°C / 60s

Reagents

Taq Polymerase 5U/µL0.25 µL
dNTP Mix 10mM1 µL

Version control

Every change is tracked. Roll back to any previous version, compare diffs, and always know what version was used.

Rich step editor

Build protocols with a structured flow editor — steps, substeps, inputs, and validation checkpoints.

Searchable library

Find any SOP instantly by title, tag, or linked experiment. Your full procedure library at a keystroke.

Experiment linking

When an experiment runs a protocol, the exact version is recorded. Reproducibility is automatic.

Import your existing SOPs

Bring in Word, PDF, or plain text protocols and structure them in NextLabs. No need to start from scratch.

Collaborative editing

Team members can propose edits. Owners review and approve before the new version goes live.

Compliance ready

Version history and audit trails satisfy GLP and ISO documentation requirements out of the box.

Built for real lab workflows

Standard wet-lab procedures

PCR setup, Western blot, ELISA, transfection. Each protocol is a versioned recipe — change the buffer recipe once, every future experiment uses the new version, and old runs stay linked to the version they actually used.

Regulated bioprocess SOPs

Cell line maintenance, media prep, sterility checks. Lock the approved version, require electronic sign-off on changes, keep a complete history for audits without rebuilding it after the fact.

Onboarding new lab members

Point new hires to the searchable protocol library instead of emailing a folder of PDFs. Nested step structure means they read the right thing first time and stop interrupting senior researchers with version questions.

Multi-site collaborations

Two labs running the same screen on different continents. Both sides reference the same protocol version. When one site optimizes a step, the other sees the proposed change before it goes live.

Works with your existing tools

Protocols import from anywhere your SOPs currently live and export to anywhere your team needs them. Nothing locked behind a proprietary format.

  • Word (.docx) and Google Docs import with structure detection
  • PDF import for archived protocols and legacy documentation
  • Plain text and Markdown for protocols already under git
  • PDF export with version, signoff, and timestamp watermark
  • Direct linking from experiments — version pinned automatically
  • REST API for syncing protocols with internal documentation systems

Frequently asked questions

What happens to old experiments when a protocol changes?

Nothing. Each experiment is permanently linked to the exact protocol version that ran. New experiments use the latest version unless you explicitly pick an older one. Reproducibility is preserved without manual bookkeeping.

Can multiple people edit the same protocol at once?

Edits are proposed as drafts. Owners review the diff and approve, similar to a pull request workflow. The published version is always coherent — no live merge conflicts on a critical SOP.

Do you support nested or branching protocols?

Yes. The step editor handles arbitrary nesting and conditional branches. A 30-step purification with 4-step subroutines for each fraction is structured exactly that way, not flattened into prose.

Can we sign off protocols electronically?

Approval requires an authenticated user action, recorded with timestamp and identity in the immutable audit log. Combined with versioning and access control, this satisfies the technical requirements for 21 CFR Part 11 and GLP electronic signatures.

How are protocols searched across a 200-member organization?

Search indexes title, body, tags, and linked experiments. Filter by author, last edited, or whether the protocol is referenced in active experiments. Results return in under a second on libraries of several thousand SOPs.

Ready to modernize your lab?

No commitment. Cancel anytime during the trial.