Incident Add New Issue

The Add New Issue section of the User Guide is split into several section. Use the links below or on the left-hand side to navigate to the required section.

On this page:

Sub-pages:

ADD NEW ISSUE

All new issues are entered from the Add New Issue page, the default landing page for Lucidity Incident. They can be entered by the individual reporting the Issue or by a manager or an admin on their behalf.

Video

Lucidity Incident: Add New Issue Overview

Issue Types

There are 5 issue types to chose from when entering a new issue, dependant on the Issue being reported and individual organisational requirements.

Incident report
Non-conformance
Hazard
Complaint
Improvement opportunity

There are some similarities between the 5 issue types. These include:

The details captured for each issue may vary slightly between each system configuration. Fields marked with*are mandatory
There are a range of fields that can be used to categorise each issue type. These can assist when filtering, sorting or reporting on issues and can be edited via the Settings tab

Add New Issue

To add a new issue, from the Add New Issue page:

Click the required issue type
Complete the shared fields for the issue (see table 'Definition of Fields - Shared Features below)
Complete the unique fields for each issue (see relevant definition table for each issue type on the relevant page in the user guide - use menu on left)
Once complete, click:
- Previous: to save changes and return to the previous screen
- Save: to save changes and return to the List Issues page
- Cancel: to discard changes and return to the List Issues page
- Save and Manage: to save changes and progress to the Manage page
- Save and add another injury: to save and open a new injury report screen (injury report only)
- Save and Next: to save and progress to the next incident category (injury report only)
Once each page is complete, the issue can then be managed, approved, tracked, closed and reported on from the List Issues page. The workflow and casual analysis can also be viewed. See the List Issues page in this user guide for full details.

Definitions of Fields - Shared Features

General	Entered By*	Pre-populated to name of person currently logged in
	Responsible Manager*	Select the responsible manager for the issue. The responsible manager conducts or supervises the investigation, creation of actions and approves the issue when it is ready to progress. In order to appear in the responsible manager list, a user must have applicable permissions allocated in Lucidity Access.
	Closeout Manager*	Select the closeout manager for the issue. The closeout manager reviews the issue as a whole following completion of all identified actions, and if satisfied closes the issue. They can also return to the issue to the responsible manager for additional action. In order to appear in the closeout manager list, a user must have applicable permissions allocated in Lucidity Access.
Admin Details	Organisation Details	Select organisation details as applicable such as division, location, project etc. Note location is listed as an open text field. This can be used to detail exactly where within the location the issue occurred. The location may be the Millennium Falcon but the detailed description may be "in the kitchen area of the cafeteria on the Millennium Falcon."
Other Shared Fields	Date Reported/ Detected	Use the date selector tool or enter the date the Issue was reported or detected (defaults to date entered)
	Reported/ Identified By*	Select the name of the employee or person who is reporting or identified the issue Select the name of the employee or person who is reporting or identified the issue from the drop-down list or type their name if it doesn't appear in the list
	Upload a File	Upload any files such a photographs for the issue Click 'Add Document' Locate the document Click 'Open' Enter the file name and description as applicable Click 'Upload'
	Further Actions Required?	Select 'Yes' or 'No' If 'No' is selected, this indicates the issue does not required management and will be closed. This can be useful in circumstances when a hazard, for example, needs to be reported but won't be investigated. The feature may be visible for some issue types and not others.

*The roles involved can overlap. For example, the same person entering the issue may also be the responsible manager and/ or the closeout manager.