Lab Rush

Lab Rush: What It Actually Does and How to Get It Running Without Cursing

Lab Rush is a desktop application designed to streamline laboratory workflow management. It lets you track experiments, manage sample inventories, schedule instrument time, and generate reports without jumping between three different spreadsheets and a whiteboard. The interface is functional, not beautiful. That's the point. You can grab it from their official site at labrush.io/download. I recommend the Windows 64-bit build even if you're on a recent MacBook with an ARM chip—the Apple Silicon version had some quirks last time I checked, particularly around barcode scanner integration. The installer is about 180MB. Go through the default settings, but make sure you uncheck "Launch Lab Rush on startup" unless you want it hogging 300MB of RAM before you've even logged in. During installation, it'll ask whether to install the SQLite client tools. Say yes. You will need them later when you want to do anything beyond the basics, and digging them up after the fact is annoying.

Setting Up Your First Workspace

When you open it, you're looking at a blank project structure. There's no wizard. I've watched people spend twenty minutes staring at the dashboard, wondering where to begin. Just click New Project and fill in the fields. The project name gets baked into the database filename, so don't use spaces or special characters. I learned that the hard way when one of my projects ended up as lab_rush_v2_(draft).ldb and nobody could find it in the file explorer. After that, you need to map your lab instruments. This is where Lab Rush actually earns its keep. You can either add devices manually or let it scan your local network for connected equipment. The network scan misses things about thirty percent of the time—particularly older spectrophotometers and centrifuges with proprietary serial connections. I just add those manually. You select the protocol each device uses (CSV export, API, direct serial), and then you define what data it produces. Once your instruments are mapped, you create workflows. A workflow is just a sequence of steps: load sample, run assay, record result, flag anomaly, notify principal investigator. You can chain these together so the software automatically pulls the next step when the current one finishes. This is the feature people sell Lab Rush on, and it genuinely works for routine assays. It falls apart if your lab does anything non-standard because the step-by-step model assumes linearity.

Common Pitfalls That Will Waste Your Afternoon

The biggest problem beginners hit is the sample queue deadlock. What happens is you load forty samples into the tracking system, assign them to a plate reader, and hit start. The software tries to check every sample's metadata before it begins the run. If even one sample has an incomplete entry—missing lot number, ambiguous storage location—the entire queue freezes. It doesn't warn you upfront. It just hangs at "Initializing..." for about four minutes before crashing back to the main screen. I spent two days figuring out which single sample was causing this. The workaround is to filter your queue by completion status before launching. Any queue item missing required fields should be flagged yellow. Red flags never start a run. Another issue nobody mentions in the documentation is the report generation timeout. If you're running a batch of more than two hundred samples and asking for a combined PDF report, Lab Rush will attempt to compile everything in a single process. On a machine with less than 8GB of RAM, this typically crashes around sample 147. The fix is to split the batch into groups of one hundred and generate separate reports, then merge them externally. It takes an extra five minutes and saves you from losing six hours of work.

What the Documentation Doesn't Cover

The export functionality in Lab Rush uses a proprietary format by default. That's fine until you need to hand data off to someone who isn't running Lab Rush. The built-in CSV exporter is decent, but it strips out the timestamp precision—it rounds to the nearest second. If your experiments require millisecond-level timing for kinetic assays, you need to enable raw data export in the preferences menu under Advanced > Data Handling > Preserve Timestamp Resolution. Nobody reads the preferences menu. I missed this for three months and had to redo a temperature ramp experiment because my timestamps didn't match the logger's output. There's also the issue of concurrent access. Lab Rush supports multiple users on the same project, but only through its own network share. Third-party cloud syncing—Dropbox, Google Drive, OneDrive—will corrupt the database if more than one person is logged in at the same time. The error is subtle. You won't get a corruption message. You'll just see missing rows and ghost entries that appeared during the sync window. I've recommended sticking to the built-in sharing and adding the project to a shared NAS drive if you need broader access. That's slower but it doesn't eat your data.

Is It Worth the Setup Time?

Lab Rush is not a tool you start using casually. Expect about six hours of initial configuration for a small lab—two instruments, one standard workflow, a handful of regular users. Once it's configured, it replaces probably three separate tools you were juggling. That configuration time pays off after about two weeks of daily use. Before that, it feels like extra work. That's normal. The main weakness is its handling of non-standard lab protocols. If your work involves anything outside routine plate-based assays, you'll spend more time configuring the software than actually running experiments. In those cases, a simple shared spreadsheet with conditional formatting might actually be faster. Lab Rush shines when you have repetitive processes with strict tracking requirements—quality control labs, diagnostic workflows, anything where audit trails matter. It's not free. The single-user license runs about forty dollars a month, and team licensing scales per seat. Students and academic labs get a thirty percent discount if you contact their sales team directly. The trial version is available for fourteen days with full features, which is enough time to set everything up and break it in a test project before committing.

Alternatives If Lab Rush Isn't Right for You

If the price is a factor, LabArchives offers basic lab notebook functionality at a lower tier, though it doesn't handle instrument integration the way Lab Rush does. For pure inventory tracking without the workflow automation, Excel with Power Query can get you most of the way there if you're willing to maintain it yourself. If you need something open source, OpenELIS has a steeper learning curve but covers similar ground at no cost, assuming you have someone who can maintain the server. The bottom line is that Lab Rush does what it says it does. It automates routine lab tasks and keeps track of samples better than paper ever could. It's not going to solve every problem in your lab, and it will frustrate you during the first week. After that, it's usually worth keeping around.