Jump ahead to:
Before you create an event, here are some things to be aware of:
Every event is built from a template. Event templates define the structure and default settings of an event. Learn more about event templates here.
Any user with access to the Events tab in the top navigation bar can create new events in Qualio. Learn more about Event Permissions here.
Events cannot be deleted once created, nor can they be archived.
Events can be created from either the Qualio Dashboard, or the Quality Events page.
Dashboard: Click the Create button, then select Event.
Quality Events page: Click the Events tab, then from the Quality Events sub-tab, click the Create Event button. With this option, you’ll first need to specify what type of event to be created in the New Event form.
Note: If you have not been given access to the Events feature, you will only see a video after clicking "Events" on the top navigation bar. Consult with your Quality team or use the in-app chat to send a message to Qualio Support Team.
New Event form
The first screen is the New Event form. Here you will provide initial information about the event. Many of these properties can be updated as the event evolves.
The form’s structure and fields cannot be modified/customized.
Event type: From the dropdown, select the event type/template for this event. Once the event is created, this selection cannot be modified. Required.
Title: Provide a concise and easily identifiable title as it will appear on the main events page as well as at the top of the event when opened, and the file name of exported events 255 character limit. Required.
Owner: Select yourself or another Qualio user to own this event. An event owner can be any Qualio user, in any user role, that has been granted access to the Events feature. Event owners are notified by email of event updates. Tip: If the list is very long, begin typing the name of the owner then select. Required.
Description: Consider this a high-level summary of the event. It can be modified and updated to include final outcomes. Text field; no character limit; allows non-latin characters; does not allow images, tables, HTML, etc. Will be displayed on the exported cover page as well as at the top of the event, under the title, when opened.
Related To: Specify other Qualio documents or events related to this event. Note: It is common for an initial event, like an incident, to result in other events, like a Security Breach event. By outlining and separating the different event types, and linking to one another using the Related To property, customers can create dynamic and robust event strategies.
Severity: Select Low, Medium, or High. Not customizable. See Understanding Risk Parameter for more information. Required.
Probability: Select Low, Medium, or High. Not customizable. See Understanding Risk Parameter for more information. Required.
Tags: Apply related tags to an event to distinguish products, projects, locations, visibility, etc.. Learn more about Qualio Tags here.
Time to resolve (days): Define the time limit from creation date before an event may be deemed overdue. Default value provided by the event template “Time Limit (days)” field, but can be adjusted on individual events.
Product: Select a related Product from the dropdown for better reporting.
Root Cause: Select a root cause from the dropdown for better reporting. If not initially known, this can be updated later.
After completing the form, click the Create event button. The event will be created and the Event ID assigned. Event IDs cannot be adjusted or changed.
Event Step Types
Once created, continue working on the event by clicking the event on the Quality Events main page to open. You’ll be brought to the event’s workspace where predefined Steps are listed in the main body of the page based on the template selected.
The image below displays an event with three steps. These steps were configured in the event template for this type of event and demonstrates the different types of event steps: content, tasks, and validation. Each step type has a unique workflow and features to help event owners log details, prescribe and assign tasks to team members, and provide final validation of the event outcome.
To proceed, event owners will click the Add content or Create task options in each step.
After clicking Add content, you’ll be brought to the Properties tab of the event step. Content steps require a Quality Approver be assigned to approve the work detailed and performed. Optional Reviewers and Other Approvers (non-Quality Users) can be added to the event step.
Next, move to the Content tab. Similar to Qualio Documents, content steps have a predefined structure with subheaders/sections that cannot be modified, moved around or deleted. Additionally, default content can be included like tables and instructions.
Attachment sections need to be included in the template to allow attachments like screenshots and other evidence to be added to the event step. Attachment limit is 100 Mb per file.
When you are done editing the step content, click the Done editing button. If you’d like to go back to the event, click the View issue button at the top.
Task steps allow users to map out tasks such as investigative or corrective actions. Tasks require the assignee to upload/document objective evidence of the task they have completed.
To begin listing tasks, click the Create task option of the Task Step. A task modal form will open where you must enter a task title and owner. Description is optional. Adjust the Complete before field to display the number of days the assignee has to complete the task before it will be flagged as overdue. The default value is provided by the event template.
Once tasks are created, they will be listed on the main event workspace for easy viewing.
To learn how to complete tasks, advance to Complete Tasks.
Validation steps are like content steps in that they require at least one Quality User approver and have a content tab with a text editor. But they are unique from content steps in a couple of ways.
First, every event must have one validation step and it must be completed after all previous steps have been approved. All other event steps can be completed in any order. Second, validation steps may have time delay. The validation step time delay is intended to prevent users from sending the final step for approval before a specified timeframe (in days) passes. This allows end-users to successfully verify the effectiveness of any actions taken, where required. The time delay begins when the event is created, and is specified on the event template and cannot be modified for individual events.
Although the validation step must be COMPLETED last, event owners can still create draft versions and save as their event investigation and resolution progresses. Below is an image of a validation step with an initial draft (version 0.1).
Not all event types must have Task steps prescribed in the event template. But if they do, the event owner can create and assign tasks to themselves and other team members to complete. Task assignees will receive an email notification that a task has been assigned to them, and it will also be displayed on their Qualio Dashboard.
To complete an assigned task, click the task listed on your Qualio Dashboard. Perform the prescribed task and enter your comments in the space provided.
The comments field is a text only field. Comments can be added in the space provided, then click the Comment button to have the comment added to the comments thread located below the Description. As comments are added, the newest comment is placed at the top of the comment thread along with the date/time stamp. This will show event owners a task’s progression. Only the latest task comment will be visibile on pdf exports.
Attachments can be added below the comments field by browsing for a file or dragging and dropping the file into that space.
When finished, task owners can click the Complete button at the top of the task. Enter their digital signature and provide any additional comments needed to justify the completion of the task for the event owner to view (required to proceed), then select a Resolution: Success or Fail.
Once all tasks have been completed, regardless of individual tasks being marked as a success or failure, the Task Step must be completed by a Quality or Normal user, regardless if the event is owned by a Basic user. The Quality or Normal user will click the Complete step button at the top of the Task Step, then enter their digital signature.
Reviewing & Approving Steps
Send for Review
Once you have finished editing the information in a content or validation step, it can be sent for review if reviewers were listed on the Properties tab by clicking the Send for review button at the top of the page.
Reviewers will receive an email notification and see the open action listed on their Qualio Dashboard.
Reviewers should read through all provided content and properties, and post comments when they need to draw attention to something. Event owners receive an email notification whenever new comments are posted to their event. Comments can be added to the Properties and Content tabs.
Some comments may result in the need to revise content. To do this, event owners will click the Revert to draft button at the top of the page, edit the content, then resend for review.
Otherwise, if the reviewer is satisfied with the content, they can click the Mark as reviewed button. Event owners will receive an email notification when all reviewers have completed their review.
Send for Approval
Once reviewed, when applicable, event steps can be sent for approval by clicking the Send for approval button.
Approver(s) will receive an email notification and see the open action to approve steps on their Qualio Dashboard.
Event step approver(s) should view content, properties, and comments before approving. They have the option to approve or decline by clicking the respective buttons at the top of the page.
Click the Decline button. Enter your digital signature and provide comments for the event owner, then click the Decline approval button.
Comments will appear on the email notification sent to the event owner as well as the Properties tab of the content or validation step.
Event owners can then revert the step to draft and resolve errors before resending for review (when applicable) and approval.
Click the Accept button. Enter your digital signature and comments, then click the Approve button. Once all approvers have approved an event step it becomes Effective and the event owner and all Quality users are notified by email.
The Effective step will be represented on the event with a green check mark and an updated Content status.
If changes must be made to the step, it must be reverted to draft and cycle through the review and approval process again before becoming Effective.
Once the step has been approved, continue to complete the remaining steps in the event using the process outlined above. All but the validation step can be approved/signed-off in any order/sequence. The final validation step must always be completed (approved) last.
Once all preceding Steps and Tasks have been approved/completed, and the optional Validation Step Time Delay has been met, the final Validation Step can be sent for approval. Once approved, the Event will automatically be closed. Successfully completed Events display green check marks on each Step and have a Status of Closed.
Closing an event unsuccessfully/prematurely
If an event needs to be closed due to an unforeseen issue or lack of information, you can close it by clicking the expansion menu button on the top-right of the event workspace, and select Close from the dropdown.
You’ll be prompted to provide your digital signature and comments/explanation for the premature close. These comments will be included in the Audit Trail Report.
Outstanding event steps will be updated with a “Closed” status.
Outstanding tasks will be updated with a “Cancelled” status.
An event closed unsuccessfully/prematurely will display with the prohibited symbol on each step.
Reopening an event closed unsuccessfully/prematurely
If an event has been closed early and more information becomes available, a Quality user can reopen the closed event to allow teams to record the new, additional information.
First, reopen the event by clicking the expansion menu button in the top-right of the event workspace and selecting Reopen from the dropdown. Provide your digital signature and comments related to the reopening of the event. Comments will be included in the Audit Trail. Report.
Next, revert the relevant Step(s) to record the additional data then resubmit for review/approval. All cancelled Task steps and tasks will re-open so that task owners can complete.
Event, Step, and Task Ownership
Event creators can assign event ownership to a different user from the initial Event Creation form or later from the event workspace. When event ownership is changed, an email is sent to the new owner.
Initial Creation Form
Change Owner From Event Workspace
To change ownership of an existing event, Event owners or Quality Users can open the event, then from the event workspace, click the expansion button and select Change Owner.
If a task needs to be reassigned, browse to the Event Workspace and click on the task. A slide-open drawer will preview the task. Click the pencil/edit icon in the top-right. Then identify the new task owner in the Assigned To dropdown.
Manage Events with Tags
Adding Tags to Events allows users to easily find events with the Tags filter. There is no limit to the number of tags that can be applied to an Event. Tags can also be used to restrict visibility to users. Learn more about Qualio Tags here.
Tags can be added during initial event creation or later by editing the event.
Initial Creation Form
Add or Remove Tags From Event Workspace
To add or remove tags from an existing event, Event Owners can open the event, then click the expansion button in the top right of the Event Workspace, select Edit, then modify tags as needed in the event form modal that opens.
Once applied, Tags can be viewed on the Quality Events page in the Tags column. Use the Tags filter to identify specific products, teams, topics, etc.