Create new checklist modules or sidebar shortcuts

Overview

How do I organize checklists into separate groups or modules?

If you’re managing a large number of checklists in CxPlanner, the fastest and safest way to organize them is by using sidebar shortcuts. Shortcuts let you create focused navigation views without changing where your checklists live.

For more permanent separation, you can also create module instances, which act as independent containers.

Only users with the project role Manager or higher can create or manage checklist modules and shortcuts

When and why to use this

Should I start with shortcuts or modules?

In most cases, start with shortcuts. They solve the majority of organization problems with zero structural risk and can be changed or removed at any time.

Use shortcuts first when:

You want faster access to frequently used systems or assets
You need discipline-based or phase-based navigation (Mechanical, Electrical, Level 1, Level 2)
Different team members need different “views” of the same checklists
You want to avoid accidentally separating or relocating checklists

Only consider module instances when you truly need hard separation between checklist sets.

Why shortcuts should be your default choice

What makes shortcuts so powerful?

Shortcuts are pure navigation tools. They don’t change data, ownership, or structure — they simply help users get where they need faster.

Key advantages of shortcuts:

✅ No risk of losing or misplacing checklists
✅ No duplication or data fragmentation
✅ Can be created, renamed, or removed instantly
✅ Perfect for large projects with shared systems
✅ Ideal for role-based or phase-based navigation

Think of shortcuts as custom menus, not folders.

How to create a shortcut from the sidebar

Go to System and Test view.
Right-click on a checklist, system, or asset.
Select Add shortcut to sidebar.
The shortcut appears immediately in the sidebar.

When does it make sense to use module instances?

What problem do modules solve that shortcuts don’t?

Module instances are best when checklists must live in separate containers, for example:

Different contractual phases that must not mix
Parallel commissioning scopes with identical systems
Sandbox or test environments
Handover vs. construction-phase checklists

Important to understand:

A module instance is a separate checklist container
Checklists created inside it do not appear elsewhere

This is powerful - but also easier to misuse.

How to create a new module instance

Open the Menu.
Select Settings.
Scroll to the bottom and click Add new module instance.
(Optional) Rename the module.
(Optional) Adjust its sidebar order.
To remove it, select Delete.

Video example:

Behavior and results

Shortcut behavior

Shortcuts are navigation-only
They do not move or duplicate checklists
Multiple shortcuts can point to the same system
Removing a shortcut never affects data

Module instance behavior

Each module is an isolated space
Checklists belong only to the module they were created in

Troubleshooting

Problem	Cause	Solution
Can’t create shortcut or module	Insufficient role	Ask a Project Admin for access
Deleted module but checklists missing	They were moved automatically	Check the default module
Sidebar shortcut not visible	UI not refreshed	Refresh the page

Quick facts

Recommended first choice: Sidebar shortcuts
Requires: Project role **Manager **or higher
Affects: Navigation only (shortcuts) / Checklist structure (modules)

Can I remove or rename a shortcut?

Yes - shortcuts can be modified or deleted without affecting checklists.

Can multiple shortcuts point to the same system?

Yes - this is a common and recommended pattern.

What happens if I delete a module?

All checklists are safely moved back to the default module.

Updated on: 12/18/2025

Was this article helpful?

Thank you!