Define the method
Create or reuse a protocol with steps, materials, parameters, checks, conditions, and expected timings.
Private research beta
Run the experiment. Keep the real record.
BenchLog guides the protocol and captures notes, timings, deviations, voice and outcomes while the work unfolds.
The official write-up often misses the decisions that shaped the experiment.
- During
- Small timing changes, substitutions, and observations disappear in a busy run.
- Later
- Reconstructing events from memory strips away the context needed to understand a result.
- Across
- Lab owners need visibility without asking researchers to duplicate their work.
How it works
One continuous path from protocol to reviewed run.
The interface follows the experiment rather than forcing the researcher to translate it into a separate software workflow.
Work at the bench
Record notes, timers, changes, deviations, and short voice notes exactly when they matter.
Complete the record
Review the timeline, record the outcome and interpretation, then export when it is ready.
A real BenchLog experiment screen from the current mobile beta.
Built for the active experiment
The work stays visible. The record forms around it.
The live runner is BenchLog’s defining surface: protocol guidance and documentation tools share one readable working view.
Follow the protocol at the bench
Steps, instructions, parameters, and completion state remain in view throughout the run.
Document changes in context
Timers, notes, voice, and deviations attach to the step where they occurred.
Review before completing
Researchers deliberately review the run and its outcome instead of stopping it accidentally.
Available in the beta today
A focused system for documenting experiments as they happen.
Work through weak Wi-Fi without losing the thread.
The installable PWA saves locally, queues changes, and makes sync state visible.
Traceable run history
Steps, notes, changes, deviations, and retractions remain timestamped.
Shared methods, clear ownership
Personal and lab records stay distinct while protocols and runs remain visible to the right people.
Scientific completion
Outcome and interpretation close the run instead of a simple stop button.
Useful data out
An event-log CSV, complete JSON, Markdown, and print-ready reports support review and sharing.
Built for the people closest to the experiment.
Researchers
Capture observations during the experiment and reduce the write-up afterwards.
Lab owners
Clearer methods, ownership, and visibility into active and completed work.
Small R&D teams
Shared experimental knowledge without beginning with a heavy software rollout.
Product direction
Start with better capture. Grow into dependable lab memory.
We build this in order, not all at once. Each stage has to work in a real lab before it earns the next, so what follows is a sequence we are committed to, not a set of dates.
Get capture right at the bench
A small group of labs run real experiments in BenchLog and tell us where it helps and where it gets in the way. Everything after this waits on what they find.
Make it dependable for a whole lab
More devices and more people, plus the unglamorous work underneath: clean recovery when a run is interrupted, and an account a new lab member can pick up without a walkthrough.
A year of runs you can actually use
When every experiment leaves the same structured trace, a lab's history stops being a shelf of notebooks only their author can read. You can search across runs, see how a method drifted over months, and hand a project to the next person with the reasoning intact. That is what the groundwork now is for.
Capture the experiment while it is still happening.
BenchLog is an invitation-only beta and we add a small number of labs at a time. Leave your email and we will get in touch when a place opens.
The questions below are optional. They help us start with the labs BenchLog fits best.
Already a tester? Sign in to BenchLog