How it works
1

How it works · Step 1

Plan

Creating your templates and their components has never been this easy.

Start from scratch or from a simple AI prompt, and adapt Argus Omnis to just about any type of inspection. Attributes, evaluations, states and containers give every template the structure and format your inspections need.

Two ways to start

From scratch

Build your template step by step, choosing every component yourself.

The building blocks of a template

Every template is assembled from four kinds of components. Combine them to match your inspection exactly, in your format.

01

Attributes & attribute lists

Identify what you are inspecting.

Attributes are free-form entries that identify what is being inspected, and for whom. Group them into attribute lists by area of concern: equipment information such as name, make and model, or client information such as name, address and phone number.

  • Each attribute uses the proper value type, such as text, number or date.
  • Make each attribute mandatory or optional.
  • Group related attributes into lists you can drop into any template.
Equipment informationExample
  • NameTextRequired
  • MakeTextRequired
  • ModelTextRequired
  • Serial numberTextOptional
  • Commissioning dateDateOptional

02

Evaluations & evaluation lists

Define exactly what needs to be inspected.

Every item to be inspected or evaluated starts with a simple criterion. Inspecting a vehicle's brake system, for example, involves several criteria: pad thickness, disc thickness, fluid leaks and more. Grouped into evaluation lists, criteria pinpoint exactly what must be checked.

  • One criterion per thing to check: clear for inspectors, precise in reports.
  • Group criteria into evaluation lists, such as a brake system or an emergency exit.
  • Give each criterion the state list that fits its outcome.
  • Add properties to an evaluation when needed, such as a required comment or photo when the outcome is a warning or a fail.
Brake systemExample
  1. 1 Pad thickness Wear level
  2. 2 Disc thickness Wear level
  3. 3 Fluid leaks Good / Bad
  4. 4 Brake hose condition Good / Bad

03

States & state lists

Define the allowed outcomes.

A state is an allowed outcome for a criterion. The simplest state list is Good or Bad. When you need more detail, define your own state lists based on the measured outcome: brake pads with 20% wear are a pass, while 70% wear can trigger a warning.

  • Start with simple lists like Good / Bad or Pass / Fail.
  • Create detailed lists with as many states as your inspections need.
  • Tie states to measured outcomes, so results stay consistent from one inspector to the next.
Good / BadExample
GoodBad
Wear levelExample
  • 0 – 50%Pass
  • 51 – 80%Warning
  • 81 – 100%Fail

04

Containers

Group attributes and evaluations together.

Some inspections repeat the same checks on several identical parts. Containers group attribute lists and evaluation lists together, and they can be nested. Inspecting a vehicle's tires, for example, is the same inspection four times, plus the spare, each with its own identification: a Tires container holds one container per tire, each with its tire attributes and tire evaluation.

  • Group the attributes and evaluations that belong together.
  • Nest containers to mirror how the inspected item is built.
  • Repeat the same structure for identical parts, each with its own identification.
Tires Example
  • Front – driver side

    Tire attributes

    • Make
    • Model
    • Rating

    Tire evaluation

    • Tread depth
    • Air pressure
    • Wear
    • Cuts and tears
  • Front – passenger side
  • Rear – driver side
  • Rear – passenger side
  • Spare

A component library that grows with you

Every attribute, evaluation, state and container you create, along with their lists, is saved to your library. Reuse them in future templates: the more you build, the faster each new template comes together.

  • Build once

    Create each component a single time.

  • Reuse everywhere

    Drop it into any future template.

  • Stay consistent

    The same criteria and states across all your inspections.

  • Duplicate and adapt

    Need more or less detail? Duplicate a component and shape the new copy to your needs.

A complete example

Here is how the four building blocks come together in a real template: a vehicle inspection. Expand and collapse each group to explore it.

  • Template
  • Attribute list
  • Evaluation list
  • Container

Vehicle inspection

  • Name TextRequired
  • Phone number Phone
  • Last visit Date
  • Make TextRequired
  • Model TextRequired
  • Trim Text
  • Year NumberRequired
  • Mileage Number
  • VIN TextRequired
  • Make Text
  • Model Text
  • Rating Text
  • Recommended pressure Number
  • Tread depth Wear level
    Comment on Warning, Fail Photo on Warning, Fail
  • Wear Wear level
  • Cuts and tears Good / Bad
    Comment on Bad Photo on Bad
  • Pressure Good / Bad
  • Engine oil Fluid level
  • Coolant Fluid level
  • Brake fluid Fluid level
  • Transmission fluid Fluid level
  • Power steering fluid Fluid level
  • Windshield washer fluid Fluid level

Publish and schedule

When your template is ready, publish it to make it available to your teams, then schedule inspections and assign them to your inspectors.

Step 2: Publish and inspect

Ready to build your first template?

Tell us what you inspect and we will show you how quickly you can get started.

Talk to us

© 2026 Argus Omnis. All rights reserved.