Let's start by defining a 'SOP'


A folder template consisting of several protocols related to the same procedure which form a work plan.

Use Cases

Initiating experiments from the SOP will create a folder in the project of your choice with experiments originating from each of the protocols in the SOP.

The SOPs feature also includes a Gantt tool that enables you to set the required duration for each operation and easily create dependencies between activities to make sure everything is executed in the predetermined order.

We’ve gathered a few use cases to demonstrate scenarios in which using SOPs is recommended:

QC Lab

Routine QC lab work often consists of stability and batch release testing, which usually includes various standard tests for samples. By collecting all stability or batch release protocols in a SOP, you can create a ready-to-use standard testing template to be executed when necessary. The SOP can be permanently locked to prevent any changes and to promote uniformity in the testing process, as required in QC labs.

Using SOPs provides you with the benefit of initiating all protocols at once instead of initiating each protocol separately and placing it in the corresponding folder, thus saving time and increasing efficiency.

R&D Lab / Upstream / Downstream

An R&D lab, or any other lab that develops processes requiring optimization, such as protein purification or cell growth and harvest, can employ the SOPs feature to combine all process-related protocols into a defined work plan and achieve continuous optimization by work plan versioning. This will empower users to oversee the whole process while monitoring optimization changes.

Did this answer your question?