Key Concepts in Zeltask

Zeltask is built around connected workflows. Understanding these core concepts—and how they link together—helps you get value from the platform quickly.

The Connected System

Before diving into individual concepts, understand that Zeltask's value comes from connection, not from isolated features. An inspection finding links to an incident, which triggers a corrective action, tied to an asset—all with context preserved. This traceability is created as work is executed, not reconstructed later.

Actions (Work Orders)

An Action is any task that needs to be completed by your team. Zeltask uses "Action" and "Work Order" interchangeably.

Type	Description	Example
Preventive	Scheduled, recurring tasks to maintain equipment	Monthly compressor inspection
Reactive	Tasks created in response to an issue or urgent need	Repair a broken conveyor belt

Actions can be assigned to users or teams, linked to assets and locations, and tracked through states: Open, In Progress, On Hold, and Done.

[Screenshot: Action card showing title, status, priority, assigned user, and linked asset]

Connection: Actions are triggered by inspections, incidents, or schedules—and link to assets to build maintenance history.

Inspections

An Inspection is a structured checklist executed on the plant floor. Inspections replace paper forms with digital execution that preserves context and enables follow-up.

Inspections can include:

• Multiple sections and pages
• Different question types (yes/no, text, numeric, photos, signatures)
• Conditional logic that triggers actions based on answers
• Required evidence capture

[Screenshot: Inspection being executed on mobile showing questions and progress indicator]

Connection: When an inspection reveals a deviation, you can create an incident or action directly—linked to the relevant asset and location.

Templates

A Template is a reusable form that defines the structure of an inspection or procedure. Templates ensure consistency across your organization.

Templates contain:

• Sections and questions
• Answer types and validation rules
• Conditions and triggers (notifications, required evidence, action creation)

[Screenshot: Template editor showing sections, questions, and condition settings]

Templates are created once by managers and executed repeatedly by frontline teams.

Assets

An Asset is any piece of equipment your organization needs to track:

• Production machinery (mixers, packaging lines, ovens)
• Auxiliary equipment (HVAC, compressors, water systems)
• Tools (multimeters, calibration equipment)
• Digital devices (sensors, PLCs, control panels)

[Screenshot: Asset detail view showing photo, specifications, and activity history]

Connection: Assets are the backbone of Zeltask. Every inspection, action, and incident links to assets, building a complete operational history over time.

Locations

A Location represents a physical space—a building, area, room, or zone. Locations help you:

• Organize where tasks happen
• Assign assets to specific areas
• Filter reports by site or zone
• Use QR codes for quick field access

[Screenshot: Location card showing name, description, and linked assets count]

Incidents

An Incident is an issue or unexpected event that needs reporting and resolution.

Incidents can:

• Be created manually or triggered from inspections
• Include photos and contextual evidence
• Generate corrective actions with clear ownership
• Track root cause analysis

[Screenshot: Incident detail showing description, evidence photos, and linked corrective action]

Connection: Incidents close the loop between detection and resolution—linking the finding to follow-up actions and affected assets.

Inventory

Inventory tracks spare parts and materials across storerooms. When completing work orders, technicians log which parts they used, keeping stock levels accurate.

Connection: Parts consumption links to specific actions and assets, helping you understand maintenance costs over time.

Teams and Users

• Users are individual people with access to Zeltask
• Teams are groups organized by function, area, or responsibility

Actions and inspections can be assigned to individual users or entire teams.

How Everything Connects

This diagram shows the flow between modules:

Templates → define → Inspections → find issues → create Incidents
                                                        ↓
                                               generate Actions
                                                        ↓
                                          performed on Assets
                                                        ↓
                                             located at Locations
                                                        ↓
                                               consume Inventory

The result: full traceability from detection to resolution, with context preserved at every step.

Terminology Quick Reference

Use This	Not This
Action / Work Order	Task, Job
Inspection	Audit, Checklist (alone)
Asset	Equipment, Machine
Incident	Issue, Problem