Skip to main content

Structured protocols you run step by step

From a written method to a recorded run.

Author a protocol as ordered steps and publish a version so everyone runs the same method. When it is time to do the work, start a run and the protocol becomes a live checklist you tick off step by step, in cook mode, so nothing is skipped.

Each run is recorded, so a result later points back to exactly which version was executed and by whom. Steps can consume inventory and link to the samples they touch, keeping the method and the materials in sync.

Fit a multi-day run into the days you have

A four-day protocol is four days of somebody's calendar, each of them needing the bench time and the instrument free. Schedule run puts the protocol's days down one side, each carrying its step count, its rough duration, and the instrument it needs, beside a live calendar. Click an hour to place a block at the length the recipe estimates, or drag to set your own. If a day uses an instrument, that instrument's bookings and downtime are drawn straight into the grid, the hours it cannot start in are refused, and placing the day offers to book it for you.

Check a step off and the reagent leaves the shelf

A step's materials carry live stock from Inventory, and the lot defaults to the one expiring first while leaving you free to pick another. Checking the step off draws those reagents down for real, against that lot, so the numbers move as you work and the next person to start this protocol opens it knowing what is left. It also means a result traces to a lot number without anyone writing one down twice.

Record each measurement on the step that produced it

The author decides which measurements each step collects, and a run of that protocol carries those fields with their units on the step itself: eluate volume in µL, A260/A280, pool concentration in nM. Notes and Deviation sit on every step for what you saw and what you did differently. At the end of the list a checklist counts what finishing would write down: steps ticked, capture fields filled, outputs recorded, deviations logged, each with a jump to the step still waiting. The gaps are visible while you are still at the bench, which is the only time they are cheap to fill.

Scale the whole run with one number

Set the batch to three and every reagent volume and every capture field scales with it, with the recipe's own figure kept beside the scaled one, struck through. The multiplier sits on the run card above the steps, and every change to it lands in the run's history.

More in the Protocols workspace

Writing the method

  • Written from steps and day breaks

    Steps, expected results, and day breaks are the pieces a protocol is built from, each with a place of its own on the page.

  • Safety notes at four grades

    Info, Caution, Warning, and Danger, so the hazard reads at the step it belongs to.

  • Branching steps

    Split a step into named cases, and picking a path at the bench reveals only the steps that belong to it.

Running it at the bench

  • Each run works from a frozen copy

    Edits to the protocol while you are running it leave your copy alone, so what you followed is what gets recorded.

  • Instruments and image analysis on a step

    A step can carry the instrument to book and an image analysis that launches with the author's saved settings.

  • Timers that come with you

    A step timer keeps counting anywhere in Conspecta, rides a bar along the bottom of the screen, and chimes wherever you are.

  • Timer sequences

    A preset that walks a stain through block, stain, three washes, and counterstain, one wait after the next.

  • The run travels to the bench

    The same steps, timers, and capture boxes on a phone, so what happened is written down where it happened.

What the run records

  • One run across a sample group

    Start from a sample or a whole group and every one of them links to the run as an input.

  • What the run consumed and produced

    Materials drawn down fill in as you go, and new samples you record show the run upstream of them on their Connections tab.

  • Review after the record locks

    Mark a finished run Completed or Needs review with a named reviewer, or flag it for yourself if you are the only one on the project.

  • Run history and a full audit trail

    Every run of a protocol in one list, each holding who checked what, every timer that ran out, and every captured value before and after an edit.

Learn more: Run a protocol·Write lab notes·Plan your experiments

Turn a method into a run

Write a protocol, publish it, and run it as a recorded checklist. Free for you and one collaborator.