More than a notebook. A platform for the work.
The value of an experiment is what it makes possible next: a better method, a stronger process or a question you could not answer before. Seal connects that progression. The notebook, sample, instrument evidence, controlled method and quality record belong to one platform, with neil able to work across the records you can access.
If the answer lives in a chat, the method in a document and the execution in another system, someone still has to translate between them. In Seal, neil can help investigate the result and prepare a change to the workflow that produced it. The evidence, proposed configuration and review stay connected.
Why choose Seal for the laboratory?
- Less template administration. Describe the protocol and its constraints to neil. Review a proposed configuration of steps, fields, calculations and record links, rather than translating every instruction into a form by hand.
- Less evidence reassembly. Experiments refer to samples, material lots and equipment records with their own history. A comparison can follow those relationships back to the source, instead of starting with exports from several tools.
- A shorter path from research to routine use. Development evidence can support a QC method or manufacturing procedure in the same platform. Carry the scientific context forward while adding the controls needed for its intended use.
- A system that can keep improving. Configuration, specifications, verification and approval stay together under change control. A better method does not have to mean starting a separate software project from a blank requirements document.
Start with a question: “What changed between these runs?” Follow it back to the protocol version, sample history, reagent lots, observations and original measurements. Then use what you learn to propose the next experiment. That connection between understanding and execution is the reason to put the work in Seal.
Start with neil. Put the protocol into the work.
Bring an existing procedure or describe the experiment you need to run. neil can help configure its steps, inputs, calculations and linked records in Seal. Scientists review the proposed structure against the actual method, including units, required fields, expected outputs and where judgement is needed.
The result is a reusable protocol that runs in the platform. Each experiment records the version used and the values entered. Shared calculations and fields give your team a consistent basis for comparison; observations and attachments leave room for the unexpected.
PR-014 / preparation
Prepare 10 mL at 2 mg/mL from a 10 mg/mL stock. Record the reagent lot, incubate and retain the original reading.
neil proposes the fields, calculation and record links. The scientist checks the configuration against the method.
- Material
- Reagent lot linked to its own record
- Inputs
- Stock 10 mg/mL / target 2 mg/mL / final 10 mL
- Calculation
- Stock volume = (2 × 10) / 10 = 2 mL
- Conditions
- Planned and actual incubation time
- Evidence
- Original instrument file, observations and review
Test units, missing values and zero concentration before use.
For a dilution workflow, that configuration can include stock concentration, target concentration, final volume and the calculated stock volume, with units and invalid-input behaviour defined. The sample and reagent are links to records, not names copied into a note. The source measurement, observation and review belong to the run. Scientists can examine the proposal and test it before relying on it.
The same principle applies to a larger assay: a reusable preparation step, measurements with defined units, shared calculations, linked instrument output and the required review. You do not need to choose between a blank text page and one enormous template covering every variation. Configure the reusable parts and make the differences between runs explicit.
The protocol in Seal
Preparation, required values and calculation definitions live in the same protocol.
The research configuration is visibly a draft, not a released QC method.
A protocol should fit the science. Distinguish a deliberate research variation from a change to a controlled method. Capture what was changed and why, rather than silently replacing the instructions that an earlier run followed.
The result is only the beginning of the record.
Record the conditions needed to interpret and repeat the work: sample identity, preparation, material lots, equipment, timing, units, calculations and observations. Link those to records with their own history instead of retyping names into a page.
A reagent-lot relationship lets a scientist find other experiments using the same material. A sample relationship connects parent material, aliquots and downstream tests. An equipment relationship makes its identity and relevant status available alongside the run. Labels identify those records; they do not replace the underlying lineage.
One experiment. Relationships you can follow.
Sample recordsReagent lot record
RG-018
Supplier evidence, storage and other experiments using the lot.
What that makes possible
Find the other runs using RG-018. Compare preparation and acquisition conditions before deciding whether the lot warrants a controlled follow-up experiment.
Instrument files belong with the experiment too. Seal Edge and scientific data management connect supported local exports to records in Seal. Preserve the original acquisition, distinguish it from a processed report and verify any extracted values against the source. Attaching a file does not imply that every proprietary format can be interpreted.
The advantage becomes tangible when a material is questioned. Follow the lot to its experiments, inspect the conditions and source results, and identify work that needs assessment. Those relationships are useful during normal science as well as an investigation. The records collected to perform the work become the evidence used to understand it.
Compare runs without losing the differences.
neil can help find accessible experiments, compare recorded conditions and assemble evidence for a question. Ask which runs used a lot, which protocol versions were used or which measurements support a reported result. The useful output is a comparison you can inspect: the included runs, relevant conditions, source references and differences that need attention.
In the sample runs above, EXP-042 and EXP-043 share a recorded incubation time but use different reagent lots. Asking only which time produced the highest signal misses that distinction. A useful investigation follows both the method and the material, then defines a comparison that can test the question. neil helps assemble that context and prepare the proposed next step; the scientist directs the work.
The experiment and its context
The protocol and reagent lot open their own records.
Incubation, signal and source-file reference sit alongside the run comparison.
Observations are retained without presenting an interpretation as an approved conclusion.
Keep units, method versions and sample preparation in the comparison. Missing values are not zeros. A changed lot, instrument or calculation may make two results unsuitable for direct comparison. Correlation can suggest a follow-up experiment; it does not establish a cause or validate a method.
When you decide what to try next, keep the question, supporting experiments and proposed protocol change connected. The next run then tests an explicit idea, and its outcome becomes evidence for the next decision. The long-term value is a body of science your team can use, not a growing archive someone has to read from the beginning.
Carry the method from development into controlled use.
Development, routine laboratory testing and manufacturing do not need separate copies of the scientific story. Seal connects ELN and LIMS, manufacturing execution and quality workflows through the same platform. The development runs remain available behind the proposed method.
The receiving team can inspect the protocol, material choices, calculations and supporting results behind the transfer. Required fields and calculations can be reused where appropriate; controlled criteria, training and review are defined for the receiving workflow. This reduces the handoff between “the method we developed” and “the method we now operate.”
Explore conditions across linked experiments.
Original runs keep their recorded version.Define required inputs, calculations and review gates.
Specifications and verification linked to the proposal.Release after the required evidence review and approval.
New runs use the approved version.Moving into controlled use is more than changing a permission. Define the intended use, required inputs, calculations, acceptance criteria, review responsibilities and training. Assess the method qualification and transfer work required for the receiving laboratory or operation. Keep that evidence linked to the proposed version.
Once approved, the controlled method governs new work. Earlier experiments retain the versions, conditions and observations recorded at the time. A later improvement must not rewrite the history of how a result was obtained.
Continuous validation is part of the platform.
The configuration should be able to evolve as the science improves. Change control and continuous validation keep the proposed configuration, its specifications, verification evidence and approval in Seal. This is a platform capability, not a separate set of documents to reconstruct after every change.
For a changed calculation, identify the inputs, units, formula, rounding and downstream results affected. Update the relevant user requirements, functional and design specifications and configuration specification. Run the applicable automated checks and repeatable UAT checks; retain results and exceptions with the changed version.
For example, a proposed dilution-
Current version
The work already performed stays intact.
Runs retain their instructions, values, calculations and review history. A proposed configuration does not silently replace them.
Proposed next version
The change carries its evidence.
Review the difference, why it is needed, the affected workflows and the checks required before it can govern new work.
URS, FS, DS and configuration specification linked to the affected behaviour.
Applicable automated checks and repeatable UATs, with results and exceptions.
Impact assessment, training and required approvals retained with the version.
One change record connects the reason, configuration, checks and release.
The team reviews the evidence and authorises release. A successful automated check is evidence for that decision, not a substitute for it. The benefit is continuity: improve the method, update the operating workflow and retain the basis on which both old and new work were performed.
Collaboration that stays with the experiment.
Share project records with the people who need them and set the appropriate access. Keep observations, reviewer questions, responses and signatures attached to the relevant work and version. A witness or reviewer needs the evidence and the meaning of the signature, not only a finished report.
Reports should identify the experiments and versions they summarise. Keep original measurements distinct from calculated values and interpretations. A revised summary should still lead a reader to the exact evidence behind it.
For internal prior work, neil follows the requester’s access permissions. For external literature, retain the publication and citation behind a claim and check its relevance to the method. Neither a generated summary nor a signature should be presented as a guarantee of scientific validity or intellectual-
Begin with one protocol and a question worth answering.
Choose work that matters to the team: a difficult comparison, a frequently repeated assay or a method approaching transfer. Bring a representative protocol, a few sample runs and the files behind the results. We can arrange an NDA before you share confidential records.
Together, define the required structure, source connections, calculations and review. Test a normal run, missing data, a deliberate variation and a changed protocol. Start with a useful, reviewable workflow, then extend the same connected foundation across the laboratory.
Existing notebooks can remain part of the evidence. Scope the available exports, attachments, metadata and access history before migration. Keep gaps visible; importing a PDF cannot recreate a missing native record.