Table of contents
At a glance
How do you validate Labfolder for its intended use?
Define which records and decisions Labfolder supports. Identify version, deployment model, permissions and review functions. Test representative entries against expected outcomes, including correction, confirmation, workflow changes and export. Check project ownership. Supplier evidence can support the assessment. An ELN product name or signature feature alone does not demonstrate the suitability of your installation.
- Labfolder remains as a standalone electronic laboratory notebook (ELN) within the current SciSure environment; Labregister serves as separate inventory management.
- Current support distinguishes Review workflows from the additional Review workflows plus.
- Workflow changes may affect open and already validated entries differently.
- The scope of the XHTML export depends on the project ownership as defined by the supplier.
Clarify the purpose of laboratory records prior to software validation
An electronic laboratory book can document exploratory experiments, facilitate scientific cooperation or keep records for a regulated quality decision. Capture which of these tasks your labfolder actually does. Also describe who will use the data later and whether results are passed on to a LIMS, a report or another decision-making process.
For human medicinal product GMP, Annex 11 and Chapter 4 are relevant guidelines. The current EudraLex index includes both in the version from January 2011. This classification does not automatically apply to all research activities. GLP, clinical studies, and medical devices have their own specific requirements; a general list of manufacturer standards does not define their applicable scope.
First, formulate the technical question: Can a subsequent reviewer trace who conducted a test, what corrections were made, and on which data the assessment was based? The answer requires more than a single product demonstration. It links the established workflow to representative data, appropriate controls, and a clear chain of evidence.
ELN, inventory and review expansion to be separately captured
The current supplier statement explicitly refers to Labfolder as an Electronic Laboratory Notebook and classifies both Labfolder and Labregister SciSure. Labregister is separately described for inventory tasks. The shared supplier does not constitute evidence of identical functionalities to eLabJournal or for an automatically included overall scope.
Today's help refers to Review workflows as successors to Sign & Witness and Review workflows plus as successors to Signature Workflows. The plus function is a paid add-on. Older versions of the help may therefore include different names and boundaries. Ensure that your team is aware of what is actually enabled and contractually available.
The public release portal shows version v3.25.39 for retrieval, with a technical release date of 24 September 2026. It explicitly states that technical release and availability for end users may differ; details for this entry were not provided. Therefore, whether the system is hosted in the cloud or on-premise, and the actual version in use, must be determined separately.
| Component | Documented reference | Clarify own usage |
|---|---|---|
| Labfolder ELN | Entries, Projects, and Collaboration | Leading recordkeeping and external original data |
| Laboratory register | Separate inventory management | Actual Usage and Sample Transfers |
| Review workflows | Signature process and potential witness procedure | Plan, Activation and Meaning in the process |
| Review workflows plus | Configurable test procedures | Assignment, Roles, Modifications, and Deletion |
| History / Export | Change view and PDF/XHTML output | Required Contents, Rights, and Ownership |
| Cloud / On-Premise | Different operating modes | Version, Operator Responsibilities and Recovery |
Explain the entry in the context of its original data
An entry can integrate text, tables, images, and files. Define for your study which components constitute the evidence. A annotated image can explain an observation; an original measurement file may contain additional information not fully retrievable from the displayed data. Therefore, name the required data scope based on subsequent evaluation.
The manufacturer support document describes access to previous elements via entry history, including downloadable files. For images, it distinguishes between original and annotated representations. This enables a meaningful, independent test: the reviewer can identify which image corresponds to the original capture and which annotations were added subsequently.
Also check for similarly named files from different studies. A correct file name alone does not prevent confusion. Define the relationship between study, sample, measurement, and file such that the relevant origin remains verifiable. If an external device system is leading the process, the pathway to it must be clearly described in the own traceability concept.
Hide, correct, and delete differ.
The Compliance Features help describes a history of entry modifications and access to remote data blocks. It also distinguishes between hiding an entry and complete deletion of a project, which depends on group settings. The page dates from 2022; verify the specific implementation in your current version.
For our own process, it is essential to determine whether a erroneous entry can be corrected and documented without disrupting the original context or making it incomprehensible. Define how a correction shall be explained and specify the information that will be required later. Not every correction to a laboratory record constitutes a change to the system configuration.
An appropriate negative test uses a feature that must not allow the removal of a required audit trail. A second scenario appropriately corrects a misassigned sample. Subsequently, review entry, history, and access. A manufacturer's statement such as "data cannot be deleted" is insufficient as a general safeguard when the same help documentation describes differentiated deletion options.
Establish review workflows aligned with professional qualification and validation.
The current base guidance describes review workflows as a two-stage process within the Advanced Plan. After signing, the content is locked; an authorized group member can be selected for review. The interface also provides a pathway without additional witness. Whether this approach is acceptable for your process depends on your procedure.
Review workflows also enables a configurable workflow for groups, folders, or projects. The current help specifies up to ten signatures, selectable individuals, and custom intentions. This represents a functional capability, not a mandatory requirement to use a specific number. Also evaluate standing authorization and the significance of a change request.
For example, separately define the confirmation of execution and the scientific evaluation. Verify that the selected personnel have access to the required data and that an unauthorized user could circumvent the decision-making process. A manually drawn signature and a login must not be considered equivalent evidence of identity without rigorous verification of their specific identity binding.
Consider open inspections during workflow changes specifically.
The Plus-Helper indicates a relevant impact when deleting a workflow: entries associated with the workflow are reverted to the base workflow. Open signatures are changed to "not signed" and the review must be restarted; completed signatures are retained. Therefore, such an action should therefore be verified not only using an empty test project.
Distinguish before making changes between new entries, entries currently under review, and completed entries. For each group, the department must establish a clear decision. Can an open process be continued with a different role sequence? Must it be re-evaluated? How is a previously granted approval incorporated in subsequent corrections?
Test the planned intervention to an appropriate extent and document the initial state, expected outcomes, and actual results. Additionally, verify visibility and permissions when confirmed entries are to be automatically moved to another project. A technically successful configuration step does not necessarily address these operational questions.
Example: Target state for five entries across two projects
The following case is not a run Labfolder test. Project P1 contains E1, E2 and E3; project P2 contains E4 and E5. Person A owns P1 and has read rights to P2, whose owner is B. For the transfer all five entries with their relevant files and references should be preserved.
The XHTML help limits the export to projects owned by the exporter. The first export by A is therefore insufficient for the desired overall goal: Three out of five entries belong to P1, two more are in P2. 3/5 correspond to 60 percent of the planned entry scope. This quantity check discovers the gap, but proves no content completeness on its own.
An independent list of all five entries, specifying project, owner, required files, and review reference, shall be prepared in advance. For the review, E1 and E2 shall be marked as completed, while E3 shall remain open. These statuses are intended to enable the evaluation of export and workflow changes under different initial conditions.
| Case | Defined starting condition / Action | Expected result | Additional content review |
|---|---|---|---|
| First XHTML export | A has access to P1; reads P2; exports its own projects | P1 includes 3 entries; overall objective of 5 not achieved | E1–E3 together with required components to be verified and matched |
| Complete transfer | Add a regulated export route for P2 | 3 + 2 = 5 unique entries accessible | Verify file records, project references, and review information |
| Double package | P1 accidentally entered twice, P2 do not export | 6 copies contain only 3 unique entries | Compare identities instead of merely comparing file counts |
| Delete workflow | E1/E2 completed; E3 open | Signed approvals from assistance have been received; E3 to be reviewed anew. | No silent equivalence established with completed review |
| Missing original file | E4 visible, required measurement file missing | Entry number 5 does not meet acceptance criteria. | The intended analysis cannot be reconstructed |
| Later readability | Open packages with intended reader role | Required content available without old user account access | Check links, special characters, and file formats |
Evaluate PDF, XHTML, and retention separately.
Labfolder describes PDF exports for entries or projects as well as XHTML for its own data scope. The separate XHTML help lists ELN data, raw data and templates, but binds the scope to project ownership. An administrator should therefore also ensure that the intended projects are captured by the export. A read right is not sufficient evidence for this.
Check with a small representative package whether the actual historical information is contained and how it is displayed thereafter. This may include prior contents, relevant attachments, and the significance of approvals. Whether the selected format fully supports the intended evidence cannot be determined solely from its file extension.
The system indicates that a generated PDF export is available for download for 48 hours; after this period, the export must be recreated. This availability period does not constitute a retention period for laboratory records. Determine the required retention period based on the purpose of the records and applicable regulations, and assess access, protection, and recovery under the anticipated future conditions.
Provider documents and operation refer to the actual scope
For regulated use, you need a clear linkage between requirements and existing evidence. Inquire about appropriate documentation for version, operating mode, employed functions, and configuration. Assess test conditions, results, deviations, and transferability. A package may contain sufficient evidence; neither complete coverage nor a restriction to pure standard functions should be assumed.
In the cloud and on-premise environments, specific operational responsibilities differ. Particular attention must be given to managing changes, data backup, recovery, and access to prior records. The provision of a backup is not sufficient evidence that the full required scope can be restored under your recovery conditions.
When applying updates, focus on affected functions and data pathways. Modifications to review logic, project permissions, or export capabilities may require additional validation assessments beyond a simple visual update. Leverage version information and operational experience, without automatically treating every change as necessitating full revalidation. The public release portal does not substitute for missing details regarding your specific update.
Introduction, inventory and preparation for changes to ensure workforce readiness
The Laboratory Manager describes recording and subsequent evaluation. QA defines the applicable scope and required controls. IT and system owners provide the current version, accounts, operating procedures, and export pathways; the supplier responds to product-specific limitations. Explicitly identify who owns the projects and who professionally determines acceptance criteria as well as remaining restrictions.
A limited, representative workflow facilitates onboarding. In existing systems, additional steps are required to classify legacy entries, prior rights, and established special routes. During changes, the affected documentation pathway is central. Key drivers of effort include inconsistent project owners, varied review configurations, external source data, and unclear handover protocols. A fixed duration or lump-sum fee cannot be generally derived from this.
- State the purpose of the record and specify future data usage.
- Version, Hosting, active Apps, and licensing scope to be documented.
- Aggregate project structure, owners, and access roles.
- Explain original files and their connection with entries.
- Define the significance of approvals and correction procedures.
- Prepare open and closed entries as test starting conditions.
- Prepare export list based on clear identities and required contents.
- Supplier documentation, restoration, and controlled modifications planning.
Project experience and collaboration
Link the entry version, confirmation and export
Your laboratory selects an entry whose sample, original files and processing state must remain traceable. We follow correction, confirmation and subsequent export, taking account of project ownership and the review functions in use. A limited use may need only a few clear rules and supporting tests. Where several projects, extensions or changed review routes are involved, we first distinguish their differences. The evidence should show exactly which version of an entry each confirmation covers.
Frequent Questions about Labfolder Entries and Exports
Is Labfolder merely a new name for eLabJournal?
No. Labfolder's current presence as a manufacturer calls it its own ELN in the SciSure environment. Labregister also remains a separately described inventory offer. The common provider framework does not provide identical functions or exchangeable evidence. Therefore, explicitly keep track of product line, actual version, active apps and operating form before you accept requirements or test cases from another application.
Sources: [4]
When does our Labfolder require a GMP-related suitability justification?
If the intended use relates to a GMP-relevant process—such as when records generated during the process support a quality decision—the need for validation is derived from that specific application and its associated risks. A research project is not considered GMP-related solely because it involves a laboratory notebook. Documentation of transfers and future usage must also be described. The necessary evaluation stems from the specific use case and its risk profile, not from a general manufacturer designation or a broad software category.
Which version statement is reliable?
The confirmed version of your environment including relevant additional functionalities. The public portal was made available on version v3.25.39 with a technical date of 24 September 2026, without providing corresponding release details. It distinguishes between technical release and end-user deployment. Therefore, use this entry as the source baseline and request the actual, appropriate change information for your update.
Sources: [7]
How do review workflows differ from review workflows plus?
The current guidance describes the Base Path as the successor to Sign & Witness; Plus is the paid successor to Signature Workflows. Plus enables configurable workflows and additional logic. Please verify which variant is currently activated. Previous instructions or earlier terminology should not be unverified in determining the current configuration or contractual availability.
Must every lab folder entry obtain two signatures?
A universal obligation does not arise from the product or the described core function. The assistance also allows for confirmation without additional witnessing. Whether this suffices for your process depends on the process and the regulatory domain. Define the meaning, identity, and required independent verification, and then evaluate the selected role sequence. A technical option is not a professional release.
Can we simply delete an ongoing review workflow?
First assess the affected entries. The current Plus-Help describes a rollback to the base workflow; open signatures will be marked as "not signed" and require a restart, while closed signatures remain unchanged. Review these differing outcomes with representative states. Prioritize agreement on how open activities shall be further processed and how existing evaluations shall be traceable and maintainable.
Does the entry history remain automatically protected from any data deletion?
The older help distinguishes remote data blocks, hidden entries, and final project deletion based on group settings. This does not establish absolute data security. Verify current permissions and relevant actions with your version. For the required evidence, the retained content, its contextual relevance, and future accessibility are relevant—neither solely the presence of a History toggle.
Is an administrator role sufficient for the complete XHTML export?
According to the manufacturer's guidance, the scope of XHTML is bound to the ownership of the projects. Therefore, an administrator must ensure that they hold ownership of the projects to be exported. Accordingly, verify the intended transfer by reviewing a project and entry list. Read-only access to a project belonging to another party shall not be considered evidence that its data is included in the export.
Sources: [10]
Which level of involvement and documentation determine the implementation effort?
You need a clear laboratory process, specific data examples, defined roles and project owners, as well as information on versioning, operation, and supplier documentation. Laboratory personnel, QA, and IT must be able to jointly decide on content and control. Inconsistent legacy projects, varied testing workflows, and scattered original files increase workload. Start with a limited validation pathway, with pre-defined acceptance criteria.
Is a PDF export already sufficient as an archive?
For adequate archiving, the required original files, historical references, and additional information must be retained and remain accessible for future use. A PDF can provide a readable representation, without covering all aspects. Therefore, evaluate the selected export scope in relation to the intended audit or traceability purpose. The 48-hour period refers to the availability of the generated export download and does not reflect the professionally or regulatorily required retention period.
Sources and review date
As of 6 October 2026. Product scope and features are based on the respective manufacturer websites. Current review identifiers are separated from older help pages. Technical release date, cloud deployment, and customer installation dates may differ; non-public release details and individual contracts are not depicted herein.
- European Commission: EudraLex Volume 4
- EU GMP Annex 11: Computerised Systems
- EU GMP Chapter 4: Documentation
- Labfolder by SciSure
- Review workflows
- Review workflows plus
- Labfolder Traceability Report: Release Notes
- Export data and download content
- Compliance Features
- What is included in a XHTML export?
Sources checked: .
Assess the actual evidence trail in Labfolder
We support you in consolidating entries, reviews, project responsibilities, and export paths into a traceable inspection and operational concept.
- Computer system validation →
Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

