SLM Checklist Configuration Guide
SLM checklist configuration allows administrators to create structured verification checklists that guide and document compliance with specific procedures, tasks or standards. Checklists provide predefined items that users can review and complete consistently within Safety Lifecycle Manager.
Administrators can create checklist definitions and individual checklist items, configure checklist-specific statuses, add custom fields and attach completed configurations to objects throughout SLM.
This guide explains the SLM checklist configuration process, including how checklist statuses influence completion percentages and how definition and non-definition custom fields behave when users work with an attached checklist.
Understanding SLM Checklist Configuration
Checklists in SLM are structured tools designed to guide and document compliance with specific procedures, tasks or standards. They help improve consistency and thoroughness by providing users with a predefined collection of items to review or complete.
Administrators manage these configurations through the System module under Verification Checklists.
From this area, existing checklists can be edited or deleted and new checklists can be created. A checklist can contain its own items, statuses and custom fields before being attached to an object elsewhere in SLM.
The main configuration process consists of:
- Creating the checklist.
- Adding checklist items.
- Configuring checklist-specific statuses.
- Adding custom fields where required.
- Attaching the checklist to an SLM object.
- Tracking completion through item statuses.
Creating a Verification Checklist
To create a checklist, navigate to the System module and select Verification Checklists.
When adding a new checklist, the training demonstrates configuring information including:
- Checklist name
- Checklist ID
- Description
- Hidden status
- Category
The description is optional, while the Hidden setting allows the checklist to be hidden when required.
A category can also be assigned to help organize the checklist. After the required information has been entered, saving the configuration creates the new checklist and allows its individual items to be added.
Adding and Organizing Checklist Items
After the checklist has been created, individual checklist items can be configured.
Select the required checklist and use the Add Checklist Items function. Each item can contain:
- Item name
- Item ID
- Description
- Hidden status
- List order
The list-order setting controls the sequence in which the configured items are presented within the checklist.
Additional items can be created using the same process, allowing administrators to build a structured series of verification steps appropriate to the procedure or activity being managed.
For a broader introduction to working with checklists as an SLM user, see the SLM-101 Checklists Guide.
Configuring SLM Checklist Statuses
SLM checklist configuration supports both global checklist statuses and statuses created specifically for an individual checklist.
The global statuses demonstrated in the training include:
- Not Started
- Not Applicable
- In Progress
- Failed
- Complete
Global statuses can themselves be managed by administrators, including adding, editing or deleting statuses where appropriate.
Additional statuses can also be created for an individual checklist. The training demonstrates adding Open and Closed statuses that apply specifically to the tutorial checklist.
A checklist-specific status can include a code, background colour, list order and settings that determine whether it represents an initial or final status.
Initial and Final Checklist Statuses
Initial and final status settings are particularly important because they influence how SLM determines checklist completion.
In the training example, Open is configured as an initial status while Closed is configured as a final status.
The final-status property identifies checklist items that SLM treats as completed when calculating the overall checklist completion percentage.
For example, the training creates a checklist containing two items. One item is subsequently set to Closed, which is the configured final status, while the other remains Open.
After the changes are saved, SLM reports the checklist as 50% complete because one of the two checklist items has reached a final status.
This means administrators should consider the effect of initial and final properties when designing statuses rather than treating statuses as visual labels alone.
Adding Custom Fields to Checklist Items
Administrators can extend checklist items by adding custom fields to the checklist configuration.
The training demonstrates two types of custom field:
- Definition fields
- Non-definition fields
A definition field is displayed as a read-only value on each checklist item. It can therefore provide predefined information that users can reference but do not modify while completing the checklist.
A non-definition field can accept user input. In the training example, a non-definition field is configured as a dropdown so users can select a value while working with the checklist.
Custom fields can also have their own labels and list order, allowing the checklist configuration to be adapted to the information that needs to be captured during verification.
Attaching a Checklist to an SLM Object
Once the checklist configuration is complete, it can be attached to an object within an SLM module.
The training demonstrates this process using an object within the Global module. The user selects the object and chooses Attach Checklist before selecting the required checklist category and checklist.
After the checklist has been attached, its configured items become available on the object.
Opening the checklist provides information for each item including:
- Description
- Findings
- Status
- Verified By
- Last Status Changed
- Modified By
- Modified On
- Configured custom fields
The checklist-specific statuses appear alongside the applicable global statuses, giving users the available status choices when working through each checklist item.
How Checklist Completion Is Calculated
SLM checklist configuration uses the status properties assigned by administrators to determine checklist completion.
When an item reaches a status identified as final, that item contributes to the checklist’s completed percentage. Items that have not reached a final status remain incomplete for this calculation.
The example demonstrated in the training contains two checklist items:
- One item with the final Closed status.
- One item with the initial Open status.
Because one of the two items has reached a final status, SLM displays a checklist completion value of 50%.
Correctly configuring the status properties is therefore essential if the completion percentage is intended to represent progress through the checklist accurately.
Designing Effective SLM Checklists
When creating verification checklists, administrators should consider the checklist structure as a complete workflow rather than configuring each element independently.
The checklist items define what must be reviewed, statuses define the progression of those items, custom fields provide additional information or data capture, and final-status properties determine how completed work contributes to the overall percentage.
A practical configuration should therefore consider:
- Whether each checklist item represents a clear verification activity.
- The order in which items should appear.
- Which global statuses are appropriate.
- Whether checklist-specific statuses are necessary.
- Which statuses should represent completed work.
- Whether users need additional editable custom fields.
- Whether read-only definition information should accompany each item.
Keeping these elements aligned helps create a checklist that is straightforward for users to complete while providing meaningful progress information within SLM.
For broader guidance on designing and maintaining structured checklists, administrators can refer to the NIST National Checklist Program guidance, which discusses checklist development, use, maintenance and lifecycle management. SLM-specific checklist configuration should continue to follow the workflows and controls provided within Safety Lifecycle Manager.
Managing Checklist Configuration in SLM
SLM checklist configuration provides administrators with control over both the structure of a checklist and the way users interact with it.
Administrators can create and organize checklist items, control visibility, define checklist-specific statuses and add custom fields appropriate to the verification process.
Once attached to an object, the checklist combines these configured elements with user-entered findings, verification information and status history.
The use of initial and final status properties also allows SLM to translate individual checklist-item statuses into an overall completion percentage.
Together, these capabilities allow verification checklists to support structured and repeatable activities throughout the SLM environment.
Modification of Checklists
0:06
Welcome to this Application Explainer video, part of our system topic range.
0:10
In this video, we’ll cover the subjects of the modification of checklists in SLM.
0:16
In SLM, checklists are structured tools designed to guide and document compliance with specific procedures, tasks, or standards.
0:24
They ensure consistency and thoroughness in executing processes by providing a predefined list of items to be reviewed or completed.
0:33
The following information will be covered in this training.
0:36
How to create a modified checklist, how to create a modified checklist items, how to add new checklist statuses, and how to create a checklist for an object in the system.
0:50
In order to create a checklist, users need to go to the System module, then click on Verification Checklists.
0:57
In here, users will be able to edit or delete existing checklists, as well as adding new ones.
1:04
Let’s just add a checklist name in here, Checklist ID.
1:12
We can add a description if we want to.
1:14
Checklists can be hidden at any point in time.
1:17
For this tutorial, we’re just going to leave this unchecked.
1:20
Let’s add a category for the checklist.
1:23
Let’s click Save and now the checklist has been created.
1:28
After the checklist has been created, we can start adding the checklist items.
1:34
Let’s filter for and click on our checklist.
1:39
Then we click Add checklist Items.
1:42
Let’s add item one.
1:45
Item ID can be item one as well.
1:48
Add a description.
1:55
Items can also be hidden, but for this tutorial we’re just going to leave this unchecked.
1:59
We can also add a list order for each one of the items.
2:05
Let’s go ahead and add a second checklist item and click Save.
2:16
We can also manage checklist statuses per each checklist.
2:22
Before creating a unique status for this checklist, we can go over the checklist verification.
2:30
There are already some global statuses for all checklist.
2:34
These global statuses can also be managed.
2:38
You can delete, edit or add new global statuses.
2:42
Currently we’ve not started, not applicable, in progress, failed and complete.
2:50
Let’s just go to the checklist that we’ve created, and let’s add two more statuses that will only apply for tutorial checklists.
3:05
So we can say open, open for the code.
3:11
We can also hide the status if we want to, but we’re not going to in this instance.
3:16
This status can be initial status or a final status.
3:20
These two flags will indicate the completion of the task list, especially the final status, which will identify each of the checklist items and take a look at the completion percentage based on the final status.
3:33
So let’s select initial status.
3:37
We can add a background colour and the list order and click Save.
3:48
And now let’s add a status of closed.
3:54
We’ll check this one as the final status, add our background colour, we’ll leave the text colour empty and a list order of two.
4:12
And we can see the background colours and foreground colours.
4:15
The default foreground colour which is going to be black for both.
4:18
For these two checklist statuses, we can also manage custom fields for checklist items.
4:25
If we click on manage custom fields and then add a custom field.
4:30
There are two types of custom fields, definition and non definition.
4:35
The definition is a field that will be read only on each one of the checklist items.
4:40
So let’s create a definition field.
4:42
We’ll just call it field one.
4:44
Have a label of field one.
4:47
The definition value will be.
4:48
This is a definition field.
4:54
We can set the list order to 0 and click save.
4:58
Now let’s create a non definition field by unchecking this tick box.
5:05
We’ll just call this field 2 field, label field 2 again.
5:10
And let’s say this non definition field is a drop down.
5:14
Select the value list order of one and click Save.
5:22
Now let’s go ahead and create a checklist in the system.
5:27
We can go to any objects in any module.
5:31
Let’s go to global.
5:34
Let’s go to units and click on Attach checklist.
5:41
The category was example.
5:44
The checklist was Tutorial.
5:46
Click on Save, we can see that the checklist has two items.
5:51
The checklist itself has a completion status, so if we click on tutorial, we’re going to be able to see the items.
5:58
Each item will have the description findings, status verified by and last status changed, modified by modified on and.
6:13
Here are the two custom fields that we added.
6:16
As we described previously, Field 1 was a definition field, so it’s going to be read only value that will be displayed on each checklist.
6:23
Item field #2 was defined as a drop down and users can change this value.
6:30
Then if we go to the status, we’re going to be able to have the open and close statuses that we just added for this checklist as well as the global statuses as well.
6:40
Complete failed in progress, not applicable and not started.
6:44
Now let’s say that we select one as closed and we select one as open, and then we click Save changes.
6:53
If we close the checklist and go back to the checklist, we’re going to be able to see that the checklist completion status is going to be 50% because one of the status was set as final status and the other one was set as initial status.
7:07
And this is how the percentage completion is calculated based on what properties have been assigned to each one of the statuses.