Versioned protocols
An experiment will refer to a specific procedure version, including after subsequent changes.
All projects
LABORATORY / PROTOCOLS / EXPERIMENTS
Rewinit BENCH
From protocol to a structured result.
We are building a digital experiment journal for small research teams. BENCH is intended to connect protocol versions, execution records and result files so teams can revisit research and compare successive runs.
Delivery preparation
A plan that leads to deployment.Delivery preparation
As of 28 October 2026Scope defined. Next step: delivery.
We have prepared the project identity, first-version scope and acceptance criteria. The next stage is to build and verify the described journey with a partner. Timing will be agreed for the selected deployment.
- Prepared
- Scope and identity
- 01 / Next stage
- Protocol versioning, experiment records, attachments and comparison of two runs.
- 02 / Planned stage
- Partner pilot
Who are we building this for?
Small laboratories and R&D teams developing their own research procedures.
Where do we begin?
The protocol is in a document, observations in a notebook and results in another folder. BENCH is intended to bring these materials together around an experiment and preserve its execution context.
What will the first version include?
Research work journal / Rewinit BENCH
Execution and deviations
An experiment record will connect steps, observations and deviations from the plan.
Comparable runs
Results and attachments linked to an experiment will make successive runs easier to compare.
Explore the planned journey.
Choose successive steps to see how the project’s first application is intended to work.
Interactive delivery plan
Rewinit BENCH / 01
Choose a protocol
Example scenario
Experiment TEST-B12 uses version 2 of a procedure.
Planned outcome
The record retains a reference to the selected protocol version.
An example scenario using prepared data. This presentation illustrates the planned process; it does not operate external systems.
A plan that leads to deployment.
Each stage follows verification of the previous outcome. The pilot scope will be agreed with a partner.
Prepared
Scope and identity
Project mark, visual direction, audience, first-deployment scope and acceptance criteria.
- 01
Next stage
First version
Protocol versioning, experiment records, attachments and comparison of two runs.
Acceptance criterionChanging a protocol does not change an earlier experiment record; export preserves notes, versions and file relationships.
- 02
Planned stage
Partner pilot
Run one research workflow with a partner laboratory and have a researcher assess record completeness.
- 03
Planned stage
Preparation for availability
Agree team access, exports and backups. CYCLE integration will be a separate stage after acceptance of the device interface.
Development journal
Rewinit BENCH / DEVELOPMENT
First-deployment scope and identity prepared.
We have prepared the project mark and visual identity and defined its audience, first scenario, milestones and acceptance criteria. The delivery plan describes the next outcome to verify.
Project identity
A distinct mark and colour within the shared Rewinit system. The identity accompanies the project from planning to first-deployment materials.
Download SVG logoRewinit BENCH / PARTNERS
Build the first deployment with us.
We are seeking a partner to adapt the scope to a specific process and evaluate the outcome in a pilot.
Discuss BENCHA useful starting point
- One research workflow
- An example protocol and result files
- A researcher to assess record usefulness