How do wet-lab teams move instrument files into a reviewable experiment record?
I’m curious how wet-lab teams handle this today.
A typical experiment can leave behind CSV or XLSX exports, NanoDrop or plate-reader files, notebook notes, protocol details, and messages in Slack or Teams. The calculations may be correct, but the context is often split across several places.
When someone needs to review, reproduce, or hand off the work, what does that process look like in your lab?
A few questions I’d especially love to hear about:
• Which instrument or file format creates the most friction?
• Do you keep the raw file, the calculations, and the experiment notes together?
• Where does the handoff usually happen: an ELN, LIMS, shared drive, Slack/Teams, or somewhere else?
• What would make an experiment record genuinely useful for review or collaboration?
I’m working on SciTuu, a browser-first toolkit for wet-lab calculations and experiment handoffs. It includes Data Inbox, Instrument Inbox, guided workflows, and reviewable Experiment Packets. The core calculations run locally in the browser, and the product is intended for research use only.
I’m less interested in pitching the product here than understanding how real lab teams manage this workflow. Any examples, frustrations, or strong opinions would be very helpful.
For context, SciTuu is scheduled to launch on Product Hunt on July 29:
https://www.producthunt.com/products/scituu-wet-lab-tools?launch=scituu-wet-lab-tools

Replies