Create Your First Checklist

Checklists in Zeltask are called "Inspections." They're based on templates and executed by operators or supervisors. This guide shows you how to run your first inspection.

Before You Start

• You need at least Staff Member permissions to execute inspections
• To schedule inspections for others, you need Manager or Admin permissions
• At least one inspection template must exist in the system

Understanding the Inspection Flow

Inspections in Zeltask follow this process:

1. Templates define the checklist structure (created by managers or admins)
2. Inspections are executed based on those templates
3. Results are recorded and can trigger actions or incidents

Steps to Execute an Inspection

Step 1: Open the Inspections module

1. Click Inspections in the left sidebar
2. The module loads showing your completed and in-progress inspections

[Screenshot: Sidebar with Inspections menu item highlighted]

Step 2: Start a new inspection

1. Click Execute Inspection
2. A modal opens where you select which template to use

[Screenshot: Inspections module with Execute Inspection button highlighted]

Step 3: Select a template

1. Browse the available templates
2. Click the template you want to execute
3. The inspection form loads

[Screenshot: Template selection modal showing available inspection templates]

Step 4: Review the inspection structure

Before answering questions, notice:

• Inspection name and description at the top
• Sections that group related questions
• Progress indicator showing completion percentage
• Total number of questions

[Screenshot: Inspection form showing header, sections, and progress indicator]

Step 5: Answer the questions

Work through each question in order:

Question Type	How to Answer
Yes/No	Select one option
Multiple Choice	Select from available options
Text	Type your response
Numeric	Enter a number
Photo/Video	Capture or upload evidence
Signature	Sign on screen

[GIF: Answer a Yes/No question, then answer a Multiple Choice question]

Step 6: Handle triggered conditions

Based on your answers, the template may trigger:

• Notifications — Alerts sent to specific users or teams
• Required Evidence — You must upload a photo or video
• Ticket Creation — A form to create an incident

If a ticket is triggered, complete the fields:

• Name and description
• Priority and due date
• Assigned person or team
• Location and asset (if applicable)

[Screenshot: Triggered ticket creation form within an inspection]

Step 7: Add comments (optional)

While working through the inspection, you can leave comments to provide context or flag concerns. Comments are visible in the inspection history.

Step 8: Review and submit

1. When all questions are answered, click Continue
2. The Summary screen shows all your answers
3. Review for accuracy
4. If you need to change something, click back to edit
5. Click Finish to complete the inspection

[Screenshot: Inspection summary screen showing all answers with Finish button]

Viewing Completed Inspections

After submission:

1. The inspection appears in your completed list
2. Click any inspection card to view details
3. Download or view the inspection report

[Screenshot: Completed inspection card showing date, template name, and status]

Scheduled Inspections (for Managers)

Managers can schedule inspections in advance:

1. Click Schedule Inspection
2. Select the template
3. Set the schedule:
   • Start date and due date
   • Recurrence (daily, weekly, monthly, yearly)
4. Assign to a user or team
5. Click Submit

[GIF: Schedule Inspection form — select template, set recurrence to Weekly, assign to a team]

Assigned users receive notifications about scheduled inspections.

Tips

• Complete inspections in order—the template may have conditional logic that depends on previous answers
• Take clear photos when evidence is required
• If you notice an issue, create a ticket immediately rather than waiting until the end
• Use comments to explain unusual findings or provide context