Changelog

Follow up on the latest improvements and updates.

RSS

  • Auditor packet:
    one print-ready PDF of register logs for a date range, covering deviations, CAPAs, change controls, complaints, training and equipment.
  • Equipment:
    calibration and maintenance due dates on the quality calendar, reminders, and a record PDF. Failed calibrations and out-of-service events appear in the auditor packet.
  • Out-of-specification results:
    attachments, a record PDF, and Phase I due dates on the calendar with reminders.
  • Reactivated employees receive the group training they missed while inactive.
New capabilities are switched on per organization. Read the release notes.
  • Change controls
    can hold implementation until every listed document has a newer approved revision or an independent, signed QA waiver.
  • Named approvers:
    a change control can list its approvers, with one required final QA approver.
  • Notifications:
    organization-wide notifications are marked read per person.
  • Automatic sign-out
    after 15 minutes without activity, and an 8-hour session limit.
  • Sign-off refusals now say why, instead of reporting a wrong password.
  • Reopening a deviation, CAPA or complaint always requires an electronic signature.
  • Record PDF layout fixes.
  • Deactivated employees leave training cohorts, and legacy training targets no longer match on names.
  • A daily email digest of overdue items has been built but is not switched on for any organization.
New capabilities are switched on per organization. Read the release notes.
  • Certificate holders get in-app alerts 30 days and 7 days before expiry, and for 30 days after it.
  • An optional quality-calendar layer shows certificate expiry dates.
New capabilities are switched on per organization. Read the release notes.
  • Equipment register:
    calibration and maintenance requirements, accepted events with evidence, out of service and return to service.
  • Internal audits:
    programme-year plans, graded findings, responses, linked CAPAs and QA close-out.
  • Out-of-specification results:
    the original result, frozen at first submission, and a Phase I laboratory investigation with independent review.
  • Certificates and licences:
    a register with expiry dates, evidence and independent verification, shown in each employee's training file.
  • CAPA risk scores
    before and after corrective action.
  • Scheduled CAPA effectiveness checks
    , with a follow-on CAPA offered when a check fails.
  • Recurring quality tasks
    , with due-soon and overdue reminders for quality tasks.
  • Change controls:
    file attachments and a list of the documents a change will revise or retire.
  • Documents:
    approval is refused while another approval task is still pending, and an optional pane shows the actual approval status.
New capabilities are switched on per organization. Read the release notes.
  • Guided 5 Whys
    on deviation investigations, alongside fishbone.
  • Deviation timeline:
    CAPAs, actions, change controls and tasks nested under a deviation, with items that run past their parent's due date flagged.
  • SOP training coverage:
    from an SOP, see the curricula and people trained on it, and list SOPs that no training covers.
  • Quality calendar:
    training due dates as a layer you can turn on and off.
  • New SLA extension requests are hidden on finished change controls; their history stays.
  • CAPA and deviation summaries count days in your organization's time zone.
New capabilities are switched on per organization. Read the release notes.
  • CAPAs:
    every action needs an owner and a due date, a CAPA can no longer be opened from a closed deviation, and a signed return no longer records an effectiveness result that was never given.
  • Change controls:
    reviewers return or reject a change with an electronic signature, a rejected change control is locked, and change-control training skips people who are no longer available.
  • Imports and downloads:
    CSV imports refuse stray quote characters, controlled-PDF downloads refuse malformed document IDs, and over-long text is refused with a clear message.
  • Reports:
    date ranges keep the end day you chose.
Read the release notes.
  • The public homepage now shows real product screens in a redesigned layout.
  • New Security and Validation pages explain the product's controls and current boundaries.
  • The Users & Roles table gives invitation status, role labels and action buttons more room.
No account setup or workflow change is required. Product permissions and organization feature settings are unchanged.
Read the release notes.
  • Controlled documents
    now open on their effective version: the version currently in force, rather than simply the newest version number. Every existing document was checked before the release and shows the same version as before. This is groundwork for revising an effective document while the current version stays in force, which is still in development and not yet available to any organization.
  • Emails
    from Invariant (invitations, password resets and notifications) now show
    Invariant
    as the sender name instead of QualityCore. The sending address is unchanged.
This release changes no organization's enablement and includes no schema migration or sign-in change.
Read the release notes.
  • Complaints:
    when two people save changes to the same complaint at the same moment, each save now waits for the other, so the "before" values written to the tamper-evident audit trail are always the values that were actually replaced.
  • Deviations:
    the audit entry written when a deviation is created now also records which closure-target cycle was applied.
  • Groundwork for future corrections of deviation severity and SLA targets ships switched off; it is not available to any organization.
This release changes no organization's enablement and includes no sign-in change. The supporting database changes were applied the same day and are not visible to users.
Read the release notes.
  • Record corrections, where enabled per organization:
    the
    Correct record
    control now also appears on change controls that have not yet been submitted for review. Administrators and QA Managers can correct the content fields (title, description, change type, impact assessment, action plan, requires-training and GMP-impact flags, planning due date, training targets and attachment references) with a reason for change; the previous and corrected values, the reason and the actor are written to the tamper-evident audit trail. Submitted, approved and implemented change controls are not correctable. A save that collides with someone else's edit or comment is refused and the draft is kept. A corrector counts as an author for the independence check on approval and implementation.
This release changes no organization's enablement; enablement remains per organization on request. No schema migration or sign-in change is included.
Load More
→