Justified extensions workflow | Invariant eQMS Roadmap

Justified extensions workflow

complete

QualityCore Product

A formal extension-request workflow (reason, approver, new due date, full audit trail) so that a legitimately extended CAPA or deviation — for example, one waiting on a third-party lab result — doesn't simply appear as a breached SLA on the dashboard.

July 17, 2026

QualityCore Product

Updated 2026-08-31 — three improvements to the justified-extensions workflow, all from real usage:
• The rules are stated before you click, not after. The justification minimum and the constraints on the new date are now shown up front rather than surfacing only once a request was rejected.
• The date you see is the date that is checked. A CAPA could reject a due date that was visibly later than the one on screen, because the display and the validator resolved different dates.
• One pending extension per record, enforced by the database. Stacked requests could previously be approved out of order and produce a due-date history that depended on approval order.
Details: https://docs.elevatedsignals.ai/qualitycore/changelog

Amar Singh

updated the status to

complete

Amar Singh

updated the status to

in progress

Amar Singh

updated the status to

complete

Amar Singh

updated the status to

planned