Skip to content

Changelog

Release notes for LQMS — user-visible changes, one entry per released version. A version listed here is an official, promoted release running at lqms.ch.

v1.0.1 — 2026-09-24

The polish release — everything the first acceptance round taught us, one day later.

  • Discard and restore — a draft created by mistake can now be discarded (it keeps its number and its history; nothing ever disappears), discarded documents live in their own administration view with search, and a discarded document can be restored: a new draft of the same document, with the full story in the trail.
  • Rare actions moved out of harm's way — revoking a released document and discarding a draft now live behind a quiet "More actions" menu in the document header, away from everyday buttons.
  • Release with a future effective date — a released version can be dated to come into force later; until then it visibly says so.
  • The details panel is now collapsible at every screen size, and the version badge answers "in force since when?" on hover.
  • Legal hold is visible — a scope under legal hold shows a quiet indicator explaining why records there cannot be disposed.
  • A calmer, more consistent surface — unified spacing, one icon language, consistent dialogs, and dozens of small alignment fixes across every screen.

v1.0.0 — 2026-09-17

The first official release.

LQMS 1.0 is a complete quality management system for regulated document work:

  • Documents with a real lifecycle — draft, review, approval, release, revision and revocation, with four-eyes enforcement (the submitter of a review round gives no verdict on it) and a full audit trail on every act.
  • Structured content, not files — documents are edited in place with structured templates, tables, diagrams and cross-references; released versions are frozen and exportable as PDF with a complete identity block (who wrote, who approved, who released).
  • Projects and mandators with hard separation — every record belongs to exactly one scope; separation is enforced in the database itself (row-level security), not only in the application.
  • Roles, review policies and training — configurable roles and staffing, review coverage rules, and training acknowledgements with their own audit story.
  • Emergency cover (break-glass) — timed, reasoned, audited self-staffing for the moment the one authorized person is unavailable; every refusal names the door.
  • Project arrival and export — a project can arrive from a source system with its released corpus, people and operating model intact (records arrive as they were; the trail claims nothing that did not happen here), and can leave the same way.
  • An in-app manual and a public documentation site — docs.lqms.ch, with the same topics available from every "?" in the application.

Operationally, 1.0 is the first promoted release: the exact image accepted on the UAT environment is moved byte-identically to production — nothing is rebuilt between acceptance and release.