Benchbot - Lab Robotics Tracker for Protocols, Robot Runs and Sample Lineage

Dashboard, run queue, run detail, plates and lineage, and plate detail. Every one of the 28 demo runs and 27 plates opens its own detail page.

Protocol version approved, requester trained on every instrument, area containment level, reagent lots in date, instruments in service and calibrated, tips and plates in stock, and input plates located.

Glycerol stock to expression, clarified lysate, 384-well assay and hit pick. Expanding a node shows the well mapping, such as the 96 to 384 quadrant stamp.

4 active, 10 waiting and 14 finished runs, with 12 instruments, 10 protocols, 8 experiments, 9 reagent lots, 5 run errors and 8 staff users.

Which Version Made This Result

Protocols lived as files inside the scheduler, edited in place. Without a version history tied to each run, a result could not be traced to the exact steps, parameters and deck layout that produced it.

Errors at 03:00 With No Record

Tip pickup failures, clots, gripper slips and driver timeouts happen mid-run. The recovery chosen - retry, skip a well, intervene by hand or abort - changes what the data means, yet it was rarely written down.

Lineage Traced by Hand

Child plates were barcoded, but their parent plates, wells and reagent lots were not linked. Confirming one hit meant walking back through glycerol stocks, expression plates and lysates in spreadsheets.

Containment, Training and Staff Data

Work with genetically modified E. coli and yeast falls under the Containment Ordinance, worker protection rules under SAMV, and training records and audit trails are personal data under the revFADP. Swiss employment law also limits systems that monitor staff.