CLUE provides a built-in template management tool that lets you design and manage the checklists your team fills out in the field. Each template you create becomes a structured form that operators, inspectors, or technicians complete during an inspection, a preventive maintenance (PM) check, or a fuel report. You control the questions on the form, what responses are required, and how the form behaves within the mobile apps. Once the template is published, they become available for your team to use directly through CLUE's Inspections feature.
This feature is primarily used by anyone that is responsible for defining what gets checked in the field.
Within your CLUE dashboard go to Company Settings > Template Manager > My Templates. This is where all existing templates are listed. From here you can view, edit, or duplicate any template.
While on the My Templates page, click on the + New Template button. You have three options to get started:
Before building out your checklist, configure the template settings. This includes selecting the template type, defining the scope of who and what it applies to, and setting compliance and behavior rules that control how the form is submitted.
Building your checklist involves adding categories that will group related items. Then add individual checklist items within each of the categories you've defined. For each item, select the appropriate response type such as pass or fail, text input, a numeric value, or a photo capture.
Click on the Preview button to see exactly how the template will appear to operators on their mobile devices. Review the layout and item ordering before publishing to ensure it's clear and easy to complete in the field.
There are three template types. Each type serves a specific purpose and determines how the completed form is processed in CLUE.
Import options convert existing forms into CLUE templates. If your team already uses paper forms or spreadsheet-based checklists, you can import them directly rather than rebuilding them from scratch. Review all imported items after the import is complete to confirm the structure and response types are correct.
Templates must be published before they are available to use in the field. A draft template will not appear for operators or inspectors until it has been fully configured and published.
Editing a published template applies changes going forward only. Completed inspections or checklists that used a previous version of the template are not affected by changes made after the fact.