IT systems · Practical guide

Validating LORENZ docuBridge: tracing submissions back to the correct document versions

A technically valid LORENZ docuBridge submission can contain the wrong revision or metadata. Connect the edition, configuration, source documents and published dossier. The lifecycle example distinguishes software validation, technical eCTD checks and content review. It gives smaller regulatory teams failure cases for changes and migrations beyond checking the document count.

Table of contents

At a glance

How do you validate docuBridge for its intended use?

Define the docuBridge edition, regional modules, format, criteria version and submission workflow. Test approved source material, document versions, metadata, lifecycle relationships and actual output. Link technical reports to the tested package and proof of transmission. A successful eCTD check does not establish configuration suitability or replace review of submission content. The procedure and affected records determine regulatory scope.

  • ONE, TWO and FIVE have different intended uses and module boundaries.
  • Record the software build, regional configuration and validator profile separately.
  • Technical eCTD review and subject matter content review address other questions.
  • Document identities and lifecycle relationships are more informative than a simple count alone.

Separate software validation from submission review

docuBridge supports the compilation, publication, import, and review of regulatory submissions. The subject matter is a dossier comprising documents, metadata, and lifecycle relationships. The product is not a system for handling individual adverse event cases. Clinical data are not solely collected within docuBridge merely because a study report later becomes part of a submission.

Separate three questions. Does the configured system support the intended workflow? Does the output package meet the technical submission rules? Is the content correct and appropriate for the procedure? A successful validator run does not answer all three. European eCTD guidance explicitly distinguishes technical validation from content review.

Therefore, first determine the product, process, recipient, format, and key records. Annex 11 is relevant in the appropriate human medicinal product GMP context, not automatically applicable to every authorization activity. For US-based electronic records, the specific Part 11 scope must be clarified. The product name does not establish a specific GAMP category nor a general signature requirement. The following review recommendations relate to the described use case and do not replace a process-specific regulatory decision.

Sources: [1] [8] [12] [11]

Further reading:

Specify the edition, module, and operation in detail

docuBridge is a product family. Public descriptions differentiate between ONE, TWO, and FIVE. ONE is designed for a single-user work environment. TWO is described as a standardized multi-user solution, while FIVE is positioned as a configurable modular system. However, the names alone do not indicate which regional modules, interfaces, or enhancements you have actually purchased and implemented.

For a small regulatory team, the standardized version may represent a different starting point compared to a globally interconnected installation. This is not an automatic recommendation based on your company's size. Inquire about the required formats, regions, concurrent tasks, external sources, and audit pathways. The public edition matrix also outlines various local and cloud deployment models.

The work help shows what should be determined before the detailed planning. An additional module described in FIVE is not transferred to TWO or ONE without testing. Especially important is the separation between an integrated validator, a separate eValidator edition and the actual criteria profile. Hold the assigned scope of delivery and the responsibility for operation, configuration and changes.

Own definition based on the publicly described docuBridge family
Variant or componentDocumented starting pointTo be clarified on-site
docuBridge ONE Single-user; local workstation Region, Format, and Required Import Capabilities
docuBridge TWO Standardized multi-user solution; integrated validator Regional modules, optional DMS and operating mode
docuBridge FIVE Modular and configurable; additional interfaces possible Purchased modules, custom configurations, and external sources
Validator profile Assessment of technical submission criteria Profile, criteria version, settings, and report
Cloud or on-premises deployment Different offered operating modes Operational responsibilities, access, security, and change tracking

Sources: [1] [2] [3] [7]

Separate maintenance of software and regional regulations

The software build is only one component of a verifiable state. This also includes the regional publishing module, the validator profile, and, if applicable, a Regulatory Update Package. LORENZ describes such packages as a separate mechanism to adapt submission configurations in response to specification changes. Therefore, a unchanged software version does not necessarily imply an unchanged submission process.

The public description of docuBridge 25.2 references EU eCTD-4.0 functionalities based on the then-existing draft of the Implementation Guide. This does not justify any general conclusion regarding currently allowable EU procedures. As of July 2026, the EMA indicates an optional use of these functionalities for new centralized marketing authorization applications, with continued separate evaluation of the continuation of existing 3.2.2 lifecycle phases.

Define for a specific test the released target: region, procedure, format version, criteria set, and relevant modules. Align this with Regulatory Affairs. Purposefully verify that an inappropriate profile has not been selected. The manufacturer’s calendar does not replace this assignment; a release schedule based on April/October cycles does not imply the latest available version is to be used.

Sources: [4] [6] [9]

Approved source, release, and references bind

A submission may be technically readable yet contain the incorrect document version. Therefore, describe how a released source version enters docuBridge and how it is recognized in the issued package. Relevance includes document identity, version, positioning, and links. When an external content management system integration is involved, the importance of the transferred metadata becomes significant.

LORENZ describes for FIVE both its own Regulatory Content Management and integrations with third-party systems. This serves as a starting point for defining the system boundary, not as evidence of a specific interface. Assess a planned transfer and a deliberately erroneous state. If a document with the same filename but a different revision is provided, your procedure must appropriately recognize and handle the difference.

During rendering or post-processing, the actually generated output is considered. For relevant document types, assess content, readability, and target references against a predefined and independent specification. A successful import alone does not validate these attributes. Conversely, it is not necessary to verify every format option without a specific usage context. The selected cases should identify errors that would actually impair submission or subsequent use of the documents.

Sources: [3] [1] [8]

Example: Same number, different document content

This example does not represent a completed product test. Only the intended use documents from a defined eCTD-3.2.2 lifecycle are considered, not XML files or complete regulatory dossier requirements. In the current state, A1, B1, C1, and D1 are active. The planned follow-up sequence replaces B1 with B2, adds E1, and removes D1 from the current set. A1 and C1 remain unchanged.

The expected current inventory consists of A1, B2, C1, and E1. Four source documents plus one added minus one removed from the current inventory again results in four. Replacement does not alter this count. Historically, six file versions must be considered: the four original versions, plus B2 and E1. The delete operation in the example is not a claim that the historical file is physically deleted.

The table is defined prior to review. Afterward, compare identities, target references, and current views—not just the number of documents. A failure case occurs when B2 is incorrectly referenced to C1, despite B1 being intended for replacement. In such cases, the total count may still appear plausible. Additionally, a erroneous metadata value and a broken link are investigated. Prior to each scenario, the original sequence and the same released source files are restored.

Example: own desired matrix for operational documents; no measured results
DocumentStarting pointPlanned OperationExpected current status
A A1 current Unchanged A1
B B1 current B2 replaces B1 B2; B1 historically traceable
C C1 current Unchanged C1
D D1 current Remove from current inventory Not current; history remains to be classified
E Not available Add E1 E1

Sources: [1] [8]

Interpret a Validator Report in a technically accurate manner

docuBridge TWO and FIVE are described with an integrated eValidator. For the standalone edition eValidator FIVE, LORENZ lists among other things current, previous, and extended checklists. Specific features available within its own integrated setup must be separately confirmed. A profile name lacking a version and configuration renders the report only partially interpretable.

The technical review considers defined rules. The European guidance explicitly states that criteria cannot verify the accuracy of all metadata. Therefore, a technically valid entry may still be incorrect for the product or process. Complement this with targeted professional cross-checks against the released source and the intended dossier scope.

Maintain a consolidated record of package status, profile, timing, and results. A report from a previous release does not automatically address the question regarding a later-sent package. Evaluate alerts based on the actually applicable regulatory framework and their content. The article does not establish a universal approach to handling every warning. A formally successful run does not in itself constitute evidence that the software is appropriately supported by your configuration and interfaces to meet the intended workflow.

Sources: [2] [3] [7] [8]

Conduct review, submission, and regulatory authority response separately

Before submission, the reviewed submission status should be clearly defined. This should be aligned with the technical review decision and the intended recipient. A status displayed within the system describes an initial internal state. For the next step, additional verification is required to confirm that the configured submission uses the correct package status and the correct destination.

The EMA identifies the Gateway and Web Client as submission channels with technical feedback capabilities. Such technical feedback must not be automatically considered part of the substantive marketing authorization decision. Therefore, it is essential to distinguish between submission, technical receipt, and technical acceptance, and the subsequent regulatory process status. This distinction is particularly important when notifications are automatically forwarded back into a RIM system.

A correction first requires clarification of whether the issue is technical or substantive, and which submission pathway aligns with applicable guidelines. A silent replacement of the internally stored PDF would result in a loss of traceability to the previously transmitted version. Agree on responsibility, decision documentation, and assignment of the subsequent sequence or retransmission. The specific regional regulation is decisive; a single process is not assumed to apply uniformly across EU, USA, and other regions.

Sources: [5] [10] [8]

Maintain clear handling rights and historical statuses

For the intended workflow, it must be clearly defined who takes over source documents, modifies metadata, reviews a package, and initiates shipment. These tasks do not necessarily have to be performed by four distinct individuals. What is essential is justified assignment of responsibilities and actual authorizations. Evaluate an unauthorized attempt to modify an already critical version, as well as the intended controlled correction pathway.

LORENZ provides for docuBridge FIVE 24.2 an audit trail timeline with filters, such as by user or event. This functional description does not constitute a guarantee that your installation fully and unalterably captures all required information. Verify whether changes relevant to your process can be clearly reconstructed and how the corresponding information remains accessible thereafter.

When records support a GMP process, their relationships and controlled amendments must also be considered within the appropriate documentation context. For FDA-related electronic records, classification follows the specific scope. This does not result in a general electronic signature requirement for every publishing step. Similarly, retention requirements are justified based on the procedure and the specific records involved, not solely on a software feature.

Sources: [5] [13] [12] [11]

Evaluate modifications and transfers based on their impact.

Distinguish between program update, regional rule package, profile modification, and interface change. For each event, query which previously occupied assumption is affected. A modified validator profile, for example, may generate new results even if the documents and program interface remain unchanged. The appropriate review then focuses on criteria selection, alerts, and their assignment to the package.

The manufacturer describes Regulatory Update Packages as a separate change pathway. Its general statement regarding handling of complete revalidation is not adopted here as a blanket operational policy. Assess the actual scope, appropriate existing supplier documentation, and remaining gaps in evaluation. These documents may cover different configurations; neither complete coverage nor exclusive retention of unchanged standard functions is assumed a priori.

When migrating, the number and size of files that have been taken over is not sufficient. Your own target should contain relevant document identities, revisions, life cycle relationships, metadata and references. Check the current dossier status and selected historical states against the known source. Received PDF files with incorrectly assigned replacement goal would not be a suitable conclusion. Set as well as open findings and access to the old inventory are treated.

Sources: [6] [3] [4] [12]

Prepare the project with Regulatory Affairs, QA, and IT

A representative dossier, including a relevant follow-up sequence, should be available for an SME before launch. Regulatory Affairs sets out professional and regional purposes. Publishing managers explain source acceptance and output. IT respectively the operator describes installation, access and interfaces; QA is included for the appropriate quality scope and evidence decision.

The effort depends particularly on edition, regions, formats, external document sources, migration, and documented exceptions. Even a small user base can manage complex lifecycle processes. Conversely, a clearly defined, standardized usage does not automatically require evidence of every available extension. For a new implementation, the required scope is planned; in existing systems, actual versions, rules, and workflows are first reviewed and aligned.

The following preparation list ensures the task is verifiable. Existing documentation may be utilized, provided its scope and appropriateness are evident. Questions regarding an inaccessible supplier package will not be addressed by assumed contents.

  • State the edition, build, regional modules, and operating configuration.
  • Capture format and criteria versions, as well as Regulatory Update Packages.
  • Provide approved source documents and expected lifecycle.
  • Define responsibilities for content, publishing, review, and submission.
  • Prepare a secure testing environment and clearly segregated test batches.
  • Assign reports, shipping documents, and feedback to the correct package.
  • Supplier documentation, migration scope, and remaining inspection gaps are documented.

Sources: [2] [3] [6] [11]

Project experience and collaboration

Trace a submission version from its approved sources to the published output

With Regulatory Affairs and IT, we follow one submission version from approved sources to output. Known document versions let us check compilation, metadata and lifecycle links against the intended package. A limited change in criteria or modules may need focused retesting. For a large historical migration, we first map sources, earlier submissions and ownership. The technical validator report, substantive review and proof of transmission answer different questions. Your team should be able to identify exactly which package was reviewed and submitted.

FAQ on docuBridge and submission evidence

Does a successfully completed eValidator run automatically validate our docuBridge installation?

No. A technical evaluation report assesses a submission package against a specific set of criteria. The suitability of your installation, configuration, and operating procedures is a separate validation objective. Both results may be related, but must not be confused. Additionally, the technical accuracy of the content must be assessed; technically acceptable metadata may still be incorrect.

Sources: [7] [8]

Which edition should we consider as a small team?

The vendor specification is designed for TWO to support standardized multi-user usage; ONE and FIVE have different limitations. Key factors are your regional requirements, document formats, source systems, and required enhancements. Team size alone is insufficient. Confirm the actual module and operational scope, and plan validation evidence specifically for that scope, rather than assuming functionality from the most comprehensive edition.

Sources: [1] [2] [3]

What version information do we need for docuBridge validation?

The actual build including regional configuration and criteria status, along with the corresponding manufacturer documentation. The functions described herein relate to docuBridge 25.2 and FIVE 24.2. These source versions do not confirm the latest or currently installed version. Additionally, minor releases and Regulatory Update Packages may alter the functions or technical criteria you are using and require a corresponding impact assessment.

Sources: [4] [6]

Can we restructure each EU dossier due to the 4.0 support?

The technical vendor function does not replace procedure-specific authorization. The EMA distinguishes between optional use for new centralized applications and the evaluation of existing life-cycle stages and other procedural types. Therefore, verify the applicable status for your submission. The note in docuBridge 25.2 referencing a previous draft does not constitute a general obligation or approval for transition.

Sources: [4] [9]

Why is the same number of documents insufficient after migration?

The count may be correct, even if the wrong version is currently active or a replacement points to the incorrect document. Additionally, compare identities, revisions, metadata, and lifecycle relationships against an independently defined expected standard. This article's example precisely illustrates this boundary: four current documents may relate to either a correct or a technically incorrect outcome.

Sources: [1] [8]

How do we handle a incorrect document revision from the DMS?

Define in advance which approved revision shall be incorporated and ensure its identity remains identifiable in the output. Specifically check for a deliberately incorrect version with a similar or identical filename. Whether the interface technically prevents or a controlled review detects such a version depends on the system architecture. The error must not go undetected and propagate undetected through the relevant batch.

Sources: [3] [8]

Is a successful technical feedback already equivalent to approval?

No. Submission, technical review, and substantive decision-making have distinct meanings. Ensure the appropriate feedback is provided to the correct package and process. An automated status change must preserve this distinction. Clarify with Regulatory Affairs which documentation is actually required for the next substantive step; a general "successful" without context is insufficient.

Sources: [10] [8]

What does the Audit Trail Timeline demonstrate?

The manufacturer's description for 24.2 references a view and filter for changes. It does not demonstrate verified completeness of the installation or universal immutability. Verify, with relevant examples, which information is recorded and subsequently presented in a comprehensible manner. The required signature and retention handling complies with the specific purpose of the record and the applicable regulatory framework.

Sources: [5] [11] [13]

Who must collaborate and what drives the effort?

Regulatory Affairs, Publishing, IT, and respective operators, as well as QA, must jointly define the intended use, release criteria, and validation evidence. Efforts are primarily driven by multiple regions, complex product life cycles, external data sources, and legacy data transfers. Current configuration details, representative source documents, and secure testing are required. A general time or cost commitment cannot be derived from edition or user count.

Sources: [2] [3] [6]

Must every regulatory update trigger a comprehensive re-evaluation?

The scope is aligned with the specific change and its impact on intended use. Assess affected rules, existing supplier documentation, and prior validation evidence. Supplement the test cases that identify a relevant new or altered failure mode. A blanket full retest or blanket waiver is not justified solely by the term Regulatory Update Package.

Sources: [6] [12]

Sources and review date

Source date: 6 October 2026. Public edition and functional descriptions for sections 24.2 and 25.2; no evidence of the most recently installed version or customer-specific modules. The example scenario pertains to eCTD-3.2.2 user documents. EU eCTD-4.0 procedures are to be distinguished separately.

  1. LORENZ: docuBridge product family
  2. LORENZ: docuBridge TWO
  3. LORENZ: docuBridge FIVE
  4. LORENZ: What’s new in docuBridge 25.2
  5. LORENZ: What’s new in docuBridge FIVE 24.2
  6. LORENZ: Software Releases
  7. LORENZ: eValidator FIVE
  8. EMA/eSubmission Expert Group: Harmonised Technical Guidance for eCTD Submissions in the EU
  9. EMA: eCTD v4.0 implementation
  10. EMA: eSubmission Gateway and Web Client
  11. FDA: Part 11 Scope and Application
  12. European Commission: EU GMP Annex 11 Computerised Systems
  13. European Commission: EU GMP Chapter 4 Documentation

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Filing process and system validations are purposefully linked.

We support you in defining the intended docuBridge usage and establishing appropriate validation evidence among Regulatory Affairs, Publishing, and IT.

  • 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.

Send a project enquiry Customer testimonials →