Deviation Management

Every deviation handled the same way

On the night shift a deviation goes in a notebook, and the next morning one just like it is handled differently. In VisualQMS each deviation is a record that follows the same steps, linked to the corrective action it leads to.

  • The same steps every time
  • Linked to the corrective action
  • Found by customer or product
Three screens of VisualQMS: the process Deliver Products and Services as a map of activities with the roles that do them, the metadata card of the CAPA CAP-2026-004 with the people in each role, and the metadata card of the published procedure SOP 004 with its approver and next review date
Set up your way

From the first report to the corrective action

Each deviation follows the workflow you have agreed. The steps, and the people in them, can be set up to match how you work.

  1. Register it

    Record what happened, with the details the workflow asks for.

  2. The person responsible acts

    The workflow sends the task to the designated people, with reminders, and escalates it if it runs late.

  3. Find the cause

    Look into the cause, and link a CAPA if the fix needs one.

  4. Linked to what it concerns

    The deviation stays cross-referenced to its CAPA and to the documents it concerns.

See two shifts handle a deviation the same way

Whichever shift found it

What happened and what was done, kept together

Out of the notebook

Every deviation is a record in VisualQMS, whichever shift found it.

Linked to the corrective action

When the fix needs a CAPA, the deviation and the CAPA refer to each other.

Find them by customer or product

Filter and sort the records by their fields, such as customer, product or vendor.

Beyond the record

When a deviation points to something deeper

A CAPA can reference the deviation that started it. Non conformances have a module of their own, and so do recorded issues and customer complaints.

The process maps show the process a deviation departs from, with each activity linked to its approved documents. Customers, products and vendors can come from your ERP or CRM, so they are kept in one place.

The process Deliver Products and Services as six activities from onboarding new customers to transitioning them to support, each with the roles that do it and arrows between them, and an ISO 9001 tag on Validate Delivery Acceptance

Show us the deviation that keeps coming back

Tell us about a deviation you have had more than once, and we show you in a personal demo how VisualQMS takes it from the first report to the corrective action. We answer the same working day.

Questions about Deviation Management

What makes this different from a spreadsheet log?

A spreadsheet records that a deviation happened. In VisualQMS each deviation is a record with its own workflow, the workflow can require certain information before the record moves on, and the record is cross-referenced to the CAPA and documents it concerns.

Is Deviation Management a core module or an add-on?

It is an add-on module. Non conformances have one of their own, with workflow states such as Registration, Investigation, Closure, Review and Approval.

How does a deviation connect to a CAPA?

Both are add-on modules, fully cross-referenced to the other modules, so a CAPA can reference the deviation that started it.

How does follow-up stay on time?

The quality activity modules use standardised workflows with scheduling, reminders and notifications. Workflows route tasks to the designated people, and overdue tasks are escalated.

Can we use customer and product data from our ERP?

Yes. VisualQMS can fetch customers, products, manufacturers or vendors from your ERP or CRM through APIs, direct ODBC connections and other methods, so the information is used in quality work without being created or maintained again in VisualQMS.

Do we have to file deviations in the right folder to find them later?

No. VisualQMS is metadata-driven, so records are found through views that filter and sort by their fields instead of by folder location.