1. Klir Knowledge Hub
  2. Klir Comply for Community
  3. September 2024 Release Additions and Enhancements

Compliance Communications Tracking

Event Log Overview for Compliance Issues and Violations Management System

Introduction

The Event Log is a new feature in our Compliance Issues and Violations Management system designed to enhance the tracking and documentation of significant events related to compliance issues or violations. Each issue or violation now includes a dedicated 'Event Log' tab, facilitating thorough oversight of the case resolution process.

Benefits of the Event Log

  • Transparency: Provides a clear, organized record of events, allowing all team members and stakeholders to follow the progress of each case.
  • Accountability: Easily identifies actions taken, enhancing accountability within the team.
  • Compliance Assurance: Ensures all events leading to resolution are documented, supporting teams in meeting regulatory requirements.

Creating an Event Log

Users with editing permissions for an Issue or Violation can create an event log by filling out the following fields:

  1. Title: A concise summary of the event.
  2. Type: Configurable by Admin in the Lookup management area, indicating the nature of the event.
  3. Event Date: Defaults to the current date, with an option to modify it.
  4. Utility Participant(s): Dropdown of internal users involved.
  5. External Participant(s): Dropdown of external contacts with an option to create new contacts.
  6. Description: A detailed account of the event, providing context and key information.

Event Log Actions

After creating an event, users can access the event log profile page to perform the following actions:

  • Edit Event: Modify event details at any time if the user has edit permissions.
  • Add Attachments: Include relevant documents, emails, or files to support the event log.
  • Comments Section: Facilitate internal discussions or inquiries to improve collaboration.

Auto-Generation of Events

In addition to manually creating event logs, the platform will automatically generate event logs when specific actions are taken on issues or violations. This feature ensures that important changes are accurately recorded and documented within the Event Log. The following actions trigger auto generated events.

  • Creation of a New Issue or Violation: Automatically logs when a new case is initiated.
  • Linking/Unlinking Issues and Violations: Logs actions of linking or unlinking cases.
  • Re-opening an Issue or Violation: When re-opening, a modal prompts for a mandatory description explaining the reason for reopening, which is saved in the event log.
  • Changing Ownership: Logs ownership changes, requiring a reason for the update via a modal.
  • Updating Status: Automatically records status changes in the event log.
  • Editing Other Areas of the Page: Captures modifications made to other sections of the issue or violation page.

Conclusion

The Event Log enhances our Compliance Issues and Violations Management system by providing a robust framework for tracking significant events. This feature not only promotes transparency and accountability but also ensures compliance with regulatory requirements, ultimately streamlining the resolution process.

Compliance Tracking 

In our compliance management system, users have the ability to link an issue to a violation or escalate it directly into a violation. When this happens, all Event Logs and Actions from the issue are carried over to the violation. This ensures that the case can continue to be built from within the violation profile, providing a comprehensive view of all tracked changes.

To maintain the traceability, events carried over from the issue will be tagged with an “Issue carry-over” label. This allows the user to easily identify which events originated from the linked issue, the user can also find a hyperlink to the issue within the event profile. 

 

For example, issue: Spill Incident (ID:21294) was linked to the violation: Aquatech solution- spill incident (ID:10215). As seen in the second image, the events from the issue were carried over into the violation with the “Issue carry-over” label. This traceability feature helps ensure that the communications from the issue are maintained in the violations record.