You can create as many event types as necessary. For each type of event you can also preconfigure some things like the ID prefix events should get automatically, which impact levels are relevant and which QA team will need to follow up. You can also configure if you would receive email notifications for all status, or if you would like to skip a few.
If we want employees to log events at all times, we need to make it easy for them. That’s why the event registration form has been kept complete and compliant, but simple. Registering an event shouldn't take more than a minute.
Keeping track of which products, projects, services, clients, vendors, etc. are causing the most events is fundamental. Knowing this will give you specific clues about which parts of the company (or which external stakeholders) are failing to keep up with your quality standards.
In the QualityKick Events module you can link events to almost anything. This enables you to gain the necessary insights on the long term.
QualityKick’s Events module supports file uploads across the board. This way proof can be uploaded during the event registration or while performing root cause analysis and impact assessment during the event investigation phase.
You can upload multiple files and on the Event Detail page there’s a Files section where you can find all uploaded files neatly listed for your convenience.
Once an event is created it goes into the investigation phase, in which the appointed investigators gather information performing root cause analysis and impact assessment. After the investigation phase, review is required by the responsible person first and by QA after. During these phases you will typically decide if a CAPA is required or not, after which the event can be closed.
If a CAPA is required, the event can be linked to it, to maintain full traceability in the application. But you can learn more about this in the CAPAs module.
