The Quality Incident object and lifecycle allows your organization to triage an incident to determine if it is necessary to initiate a quality event. This avoids skewing quality event metrics, and unnecessarily complicating audits. Information from a quality incident can be automatically copied to a quality event, including attachments that represent pictures and video documenting the incident.

Example: Quality Incident to Deviation

An employee at your organization, Peter Production, notices an issue with a piece of equipment while performing a routine maintenance procedure. Peter is unsure if the issue fits all the necessary criteria for a deviation. In this case, Peter could add a Quality Incident record, including any supporting material such as photos of the equipment and a description of the possible issue.

Another employee, Quincy Quality, can then triage Peter’s quality incident and determine whether it meets the requirements to become a true deviation or not. In the event that the incident is determined to be a true deviation, Quincy can change the state of the Quality Incident record to, for example, Requires Quality Event, automatically creating a new related Deviation record.. When Vault creates the resulting Deviation record, it copies attachments and other information from the originating Quality Incident to the Deviation.

Creating & Managing Quality Incidents

You can create and manage Quality Incidents like other object records in Vault. Once evaluation and triage of a Quality Incident is complete, the record is typically either closed or promoted to a state that automatically creates a related quality event, such as a Deviation or Nonconformance, for further processing.

Depending on the configuration set up by your Vault Admin, the lifecycle of Quality Incidents may automate quality event creation upon entering certain Quality Incident Lifecycle states.

To create and manage Quality Incidents, users require Read, Create, and Edit permissions for the Quality Incident object.