Define the method
Create or reuse a protocol with steps, materials, parameters, checks, conditions, and expected timings.
BenchLog guides the protocol and captures notes, timings, deviations, voice and outcomes while the work unfolds.
Start with one recurring protocol and a conversation about your lab’s workflow.
The official write-up often misses the decisions that shaped the experiment.
The interface follows the experiment rather than forcing the researcher to translate it into a separate software workflow.
Create or reuse a protocol with steps, materials, parameters, checks, conditions, and expected timings.
Record notes, timers, changes, deviations, and short voice notes exactly when they matter.
Review the timeline, record the outcome and interpretation, then export when it is ready.
The live runner brings protocol guidance and documentation into one working view. The example below shows what a colleague can read afterwards.

The actual BenchLog mobile beta: step guidance, parameters and capture tools in the same working view.
The installable PWA saves locally, queues changes, and makes sync state visible.
Steps, observations, deviations and retractions remain in the experiment’s timestamped record.
Personal and lab records stay distinct. Shared protocols and runs are visible to authorized members.
Outcome and interpretation close the run instead of a simple stop button.
An event-log CSV, complete JSON, Markdown, and print-ready reports support review and sharing.
Offline sign-in and background reminders have device and connectivity limits. We cover these when setting up a pilot.
Capture observations during the experiment and reduce the write-up afterwards.
Clearer methods, ownership, and visibility into active and completed work.
Shared experimental knowledge without beginning with a heavy software rollout.
The beta starts with the record of one experiment. Broader lab memory is a future direction, shaped by what researchers need in real use. These are directions, not promised delivery dates.
Protocol guidance, notes, timings, deviations and a reviewed outcome form the current working tool. Beta feedback helps us understand where it helps and where it gets in the way.
Start with a recurring method and a small team. Evaluate practical lab use, recovery and handover, then use those findings to guide the next improvements.
Cross-run comparison and richer lab memory are future directions, guided by pilot feedback. The aim is to understand how methods change and pass a project on with its reasoning intact.
A supported pilot lets a small wet-lab team evaluate BenchLog in its own workflow. We begin with a familiar method and the documentation problem you want to solve.
Tell us what you repeat, how you document it today and who needs the resulting record.
Agree a bounded pilot and prepare one protocol with the researchers who will use it.
Review capture effort, repeat use and whether a colleague can understand the record.
Invitation-only beta for non-regulated research and development. We agree the scope, support and any fees before a pilot begins.
Leave your name and work email. We review requests individually and contact suitable labs to discuss a pilot. Access is by invitation; the conversation comes before any commitment.
Your request is already recorded. These details help us prepare the conversation. Please keep research details out of this request.
Questions or trouble requesting access? hello@benchlog.de
Already a tester? Sign in to BenchLog