> ## Documentation Index
> Fetch the complete documentation index at: https://docs.altoura.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Procedures, Tasks & Steps

> The Altoura Frontline content model — how procedures break down into tasks and steps, the step types, and the media and 3D content a step can carry.

This page is for anyone who will run or build procedures. In a few minutes you'll understand the content model that every Altoura Frontline experience is built on: the procedure → task → step hierarchy, the step types you'll encounter, and what a step can show on your device.

***

## What a procedure is

A **procedure** is a digital, interactive, step-by-step work instruction. Think of it as a paper job aid made alive — anchored to the real equipment, enriched with 3D models and media, and followed hands-free on your device.

Procedures solve the two problems of traditional work instructions:

* **Authored once, updated centrally.** The Procedures Portal is the single source of truth. Updates reach every device automatically.
* **Delivered where the work happens.** Steps, 3D models, and media appear anchored to the real equipment — not on a clipboard or a screen off to the side.

***

## The hierarchy: procedure → tasks → steps

<CardGroup cols={2}>
  <Card title="Tasks" icon="folder-tree">
    High-level groupings of related work. A procedure can have many tasks — for example, *Prepare Equipment*, *Replace Filter*, *Validate*.
  </Card>

  <Card title="Steps" icon="list-ol">
    The individual actions within a task that the worker performs in sequence. Each step can carry its own media and 3D content.
  </Card>
</CardGroup>

The **task list** shows the full task and step structure of a procedure, so workers can see where they are and navigate directly to a step when needed.

***

## Step types

Most steps are simple, sequential instructions. Two special step types shape the flow:

| Step type           | What it does                                                                                                                                                                                                        |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Standard step**   | A single instruction the worker performs, then moves to the next step. Displays a step number, task title, description, and navigation controls.                                                                    |
| **Choice step**     | Presents one or more selectable options, each wired to a **destination step**. The worker must pick an option to continue — this is how a procedure branches into separate paths based on what the worker observes. |
| **Completion step** | Marks the end of a procedure path — either the system-generated final step, a manually added completion step within a task, or the end of a branch created by a choice step.                                        |

***

## What a step can carry

Each step can be enriched so it guides the worker precisely:

* **Media** — images, video, and audio shown in a media panel alongside the step instructions.
* **3D models** — assets from the shared asset library, positioned, scaled, and rotated by the author to appear exactly where needed in the physical environment.
* **Anchor gems** — spatial markers that visually link the step to a specific physical location, connected to the step panel by a tethered line. See [Anchoring & QR Codes](/frontline/overview/concepts/anchoring-and-qr-codes).
* **Completion criteria** — rules for how a step or task is considered complete: explicit confirmation, a choice, or progress through a sub-list.

***

## The lifecycle, in one glance

<Steps>
  <Step title="Design">
    A subject-matter expert decides what procedure is needed and identifies the tasks and steps.
  </Step>

  <Step title="Author">
    They author the procedure in the Procedures Portal (browser) or directly on a device in Author Mode.
  </Step>

  <Step title="Enrich">
    They add 3D models, media, choice logic, and anchor gems so the procedure guides the operator precisely.
  </Step>

  <Step title="Publish">
    The procedure is published and becomes available to operators across the tenant.
  </Step>

  <Step title="Run">
    Operators open the procedure on their device and follow step-by-step AR guidance.
  </Step>

  <Step title="Iterate">
    Authors update the procedure based on field feedback. Operators automatically get the latest version next time they run it.
  </Step>
</Steps>

For where authoring happens and how published content reaches devices, see [How Content Flows](/frontline/overview/concepts/how-content-flows).

<Tip>
  Next: learn who builds procedures and who runs them in [Author vs. Operator](/frontline/overview/concepts/author-vs-operator).
</Tip>