Category Archives: LORENZ Development News

This category shows information from the Development of LORENZ.

LORENZ Changes Its Release Naming – Unified release naming system starting in April 2018

We are switching to a unified release naming system for all of our products, based on the calendar year.

The year-based nomenclature makes sense as LORENZ products become more and more integrated – acting as interlocking components in a single Regulatory Information Management suite. The new naming convention also follows best practice in the industry, and will help increase clarity on which version of each product is the most current – especially for customers who are using two or more LORENZ solutions in integrated environments.

For a detailed explanation of the new naming system, please click here.

To stay informed about both major and minor releases, please subscribe to Product & Service Update Announcements in your LORENZ ID.

docuBridge FIVE 5.11, docuBridge TWO 1.0, docuBridge ONE 2.4, drugTrack 5.3 and eValidator 5.10 released!

The October releases of docuBridge, drugTrack and eValidator are available!

Release Highlights:

With this release we are introducing docuBridge TWO, an addition to the docuBridge range geared specifically to small- to mid-sized companies with multiple users.

Continue reading

docuBridge 5.8, drugTrack 5.1.1, eValidator 5.7 and docuBridge ONE 2.1 released!

The April releases of docuBridge, drugTrack, eValidator and docuBridge ONE are available!

Click here for selected highlights of the new versions of docuBridge and drugTrack:



What’s new in docuBridge 5.8?



What’s new in drugTrack 5.1.1?


docuBridge ONE now supports 8 different regions: AU, CA, CH, EU, GCC, TH, US, ZA!


Purchase docuBridge ONE in our Online Store.


The way we do things around here [Part 3]

Last blog post from our Director Development Christian Kaas and his series of articles talking about “The way we do things around here” at LORENZ.

Responding to change
“Humphrey’s Law” says that customers never know what they want until they have working software in their hands to actually work with. To illustrate the point, let’s say we plan our April 2016 release with a list of features that was previously agreed in October 2015. We finish the project on time in April, delivering all of the features promised. But there’s still a high probability that a customer won’t be fully satisfied, simply because what we defined back in October is not necessarily what the customer needs in April. If customers aren’t exposed to working software before the end of our release, it’s then too late to incorporate their feedback.

Continue reading