Configuration & Design

THE PROBLEM

When every change is a development project, the system falls behind the lab

In many lab systems, configuration depends on proprietary scripting or vendor professional services, not just at implementation but for every change afterward. Even a small workflow adjustment waits in a queue, and simple or complex, every change carries the same overhead.

The result is familiar: long implementations, workflows that never fully match the SOP, and workarounds that live in spreadsheets. Every workaround is a step the system doesn't control and the audit trail doesn't see.

CAPABILITIES

Configuration your team controls

Visual workflow editor

Build workflows in a visual BPMN editor with user tasks, decision gateways, and nested workflows, using the terminology your analysts already know. The diagram you draw is the workflow that runs.

Workbooks without scripting

Define what happens at each task in the workbook configuration editor: the entity types a step works on, the fields analysts complete, and how entities are grouped. No custom code is required.

See every change before it deploys

Compare any draft with the version it started from. Added, modified, and removed steps are color-coded side by side, so reviewers approve exactly what changed.

Ship only what you meant to

Spot an unintended edit in review and discard changes to a single workflow, a single workbook configuration, or the whole draft before anything reaches an environment.

HOW IT WORKS

How configuration works in Labbit

Open a draft

Start a draft from the configuration currently deployed to an environment, so every edit is tracked against a known baseline.

Design

Model steps, decision points, routes, and workbook fields in Designer, using your lab's own terms.

Review and deploy

Review the visual comparison, run pre-deployment checks, and deploy as a versioned changeset recorded in the environment's configuration history.

IN PRACTICE

See it in practice

GMP BIOMANUFACTURING

Batch Execution & Review

Review by exception, not by binder

DIAGNOSTIC TESTING

NGS

Sequencing workflows from library prep to sign-out

DIAGNOSTIC TESTING

Spatial & Multi-Omics

Emerging assays with complex genealogy

ANALYTICAL QC

Stability Studies

Protocol through pull point to trend

FAQ

Frequently Asked Questions

Do we need developers to configure Labbit?

No custom code is needed to configure workflows and workbooks in Designer. Labbit implementation consultants typically configure the initial rollout, and trained customer system administrators make ongoing changes afterward. Changes still go through your review and validation process.

What can be configured in Designer?

Designer configures workflows, including nested workflows, and the workbook configuration behind each task. Other configuration, such as custom entity types, is managed in Labbit's configuration files, and everything deploys together as one versioned changeset.

How is configuration different from workflow orchestration?

Designer is where the process is modeled and reviewed. Lab Ops is where the deployed workflow runs, and change control records and promotes every deployment between them.

Does Labbit use AI to configure workflows?

Labbit's Configuration Assistant can draft configuration from a plain-language description. Its output goes through the same review and is recorded in the same deployment history as any other change.

How do configuration changes stay controlled?

Every change is reviewed as a diff and deployed as a versioned changeset. The environment's configuration history records who deployed it, when, and a categorized summary of what was added, modified, or removed.