Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

Understanding SeqOne Workset Versions

How workset versions work, how long each version lives, and what it means for your validation file.


The essentials

  • New versions run alongside your current one, with no cutover and no interruption to your production, throughout your migration window.
  • You migrate only when your version retires, and we notify you well ahead, with dates and next steps.
  • Migrations come with full documentation, plus a defined set of free revalidation samples.
  • Past analyses stay openable, permanently.


Why we manage versions this way

Labs have told us two things clearly: frequent changes disrupt routine production, and every change needs to be documented well enough to support an ISO 15189 file. This lifecycle model is our answer to both.

Every time a workset you use gets a new certified version, you get a guaranteed, documented migration window, and we tell you personally when yours opens. It's a planning tool: you always know where you stand, what evidence you'll have, and how long you have to act.

Four things are true every time:

  1. At least 12 months of life per version in Main (X.Y), and the clock only starts once a newer version exists to move to.
  2. You never migrate blind. Every new version ships with a non-regression report, updated technical documentation, and a change log.
  3. You never migrate alone. The old and new versions run side by side on Main, so you validate without ever stopping production, and revalidation samples are covered.
  4. Analyses already run stay openable, always. Retiring or removing a version never touches results you've already produced.


Platform version vs. workset version

The platform release version is tied to a season. Spring26, for example, is platform version 2.1, and Fall26 is 2.2. It changes for everyone, three times a year, whether or not anything you personally use has changed.

The workset version belongs to a single analysis pipeline, for example GermVar 3.12. It changes only when that pipeline itself changes: a new certified version ships when there is an analytical improvement to release, not on a fixed schedule. A given workset can keep the same version across several platform releases, since it only advances when there's an actual improvement to ship.

A lab running several worksets illustrates the shape well. All seven worksets below sit on the same platform release, but each carries its own, independent workset version:

Your ISO 15189 file should cite workset versions, since that's the number tied to the actual analysis pipeline that processed your sample.


What changes when the number changes

Read a version like GermVar 3.12.2 as: analytical version 3.12, at patch 2.

💡 If you're ever unsure whether a release affects you: check which digit moved. If it's the first two, read the documentation. If it's only the third, carry on as normal.


The four states


The clock

Every version in Main (X.Y) is guaranteed at least 12 months of life, in two parts:

  • Fully Supported, no successor yet: as long as no newer certified version exists for that workset, your version stays Supported indefinitely. There's no expiration by age.
  • Once a successor exists: your version stays fully Supported for one more release cycle, then moves to Retiring for one more cycle, with a published removal date, before it's removed.

Since Main ships three times a year, this works out to roughly 12 months of total life per version, and at least 6 months (usually 7 to 9 in practice) from the day a successor first appears.

In practice, you'll typically see two live versions of a given workset at a time, and never more than three.

Validating at your own pace

You validate on Main, not Preview. The new certified version appears alongside the one you're already running: both live, both certified, so your routine production continues uninterrupted while you validate in parallel. There is no switch-over date and no freeze.

Every analytical migration comes with:

  • a non-regression test report (old version to new) written for your ISO 15189 file,
  • an updated technical characteristics document and the full change log,
  • free revalidation samples included: we cover a defined number of your samples for revalidation, at no cost to you.

Your account team is your point of contact for the whole window. Reach out any time to plan your migration together.


Frequently asked questions

Will my existing analyses disappear when a version is retired?

No. Analyses already run remain openable permanently, including results, reports, and the version that produced them. The only change is that you can no longer launch new analyses on that version.

Am I forced to revalidate on a fixed schedule?

No. Revalidate before you move to a new analytical version, and complete your move before the published removal date. Inside that window, the timing is yours. Patch-level changes never require revalidation.

Is a Retiring version still valid for accreditation purposes?

Yes. Retiring is still an IVDR-certified state: certification, technical characteristics, and validation evidence are unchanged, and non-conformity and cybersecurity corrections continue to be applied. Retiring simply means a successor exists and a removal date is set. It says nothing about the quality or validity of what you're running.

A new Main release just landed. Did all my pipelines change?

Almost certainly not. Most worksets don't move at any given release. Check the change log for the worksets you actually use and look at which digit changed. It's a five-minute check, not a project.

Can I use Preview for clinical reporting?

No. Preview is Research Use Only and not certified. It's optional early access, never a prerequisite for anything running on Main. It also moves faster than Main: a Preview version can change more often, and each new one immediately replaces the previous version, with no side-by-side period.

What if I need more time to migrate?

Tell us as soon as you see the removal date published, which is at the start of the Retiring period, not the end. The earlier we know about your constraints, the more options we have to work with together.

How will I be notified?

You'll hear from us via e-mail, ahead of time, with the specific worksets and versions that affect you and the dates that apply. You don't need to monitor release notes to catch this.

Glossary


Still have questions? If you need help understanding how workset versions apply to your lab or planning your migration, reach out to your account team—your Field Application Scientist and Account Executive—or contact our Support team at support@seqone.com.