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

# Procedures

> Build reusable instructions and preserve the exact responses completed on each work order.

A Procedure is a reusable template of sections and fields for inspections, service routines, safety checks, and other structured work. Attaching one to a work order gives the technician a fillable snapshot of that procedure.

## Template and work-order snapshot

The Procedure Library holds the editable template. A work order holds one attached procedure snapshot with its own responses and progress.

That boundary preserves history:

* Editing a Procedure advances the template version and leaves existing work-order snapshots unchanged.
* **Delete** removes a Procedure from new selectors while existing work orders keep their copy and responses.
* A completed work-order Procedure is immutable, read-only maintenance history.
* Completed Procedure history remains readable when the Procedures feature is disabled.

Procedures can reach a work order through **Add Procedure**, a [Work Order Template](/help/work-orders/templates), Request approval, or the template snapshot in a [Maintenance Plan](/help/maintenance-plans/overview).

Admins and members manage the Procedure Library on the web. A person with access to an attached work-order Procedure can complete its supported fields. Completed snapshots continue to follow the parent work order's visibility.

## Available field types

| Purpose                   | Field types                                                           |
| ------------------------- | --------------------------------------------------------------------- |
| Confirmation              | Checkbox; Yes, No, N/A                                                |
| Written and numeric input | Text Field; Number Field; Amount (\$); Date; Meter Reading            |
| Choice and inspection     | Multiple Choice; Checklist; Inspection Check with Pass, Flag, or Fail |
| Evidence and sign-off     | Picture/File Field; Signature Block                                   |
| Structure                 | Heading                                                               |

Fields can include help text and can be marked **Required**. Choice fields carry ordered options. Numeric fields can define a unit, minimum, and maximum.

## Sections and tags

Sections group related fields and give longer procedures a clear order. Root-level fields can also sit outside a section.

**Procedure Tags** associate a template with specific assets or locations. Tags make the intended scope visible when teams review a Procedure; attachment remains an explicit choice on the work order or its source template.

## Web and mobile support

The web app can author and complete every listed field type.

Mobile can complete Checkbox, Text Field, Number Field, Amount, Multiple Choice, Checklist, Inspection Check, and Yes, No, N/A. Headings organize the mobile runner. Picture/File Field, Signature Block, Date, and Meter Reading display their saved value when present and show **Not yet available** for new mobile input; complete those fields on the web.

## Common tasks

* [Create a Procedure](/help/procedures/create-procedure)
* [Complete a Procedure on a work order](/help/procedures/complete-procedure)
* [Create a work order](/help/work-orders/create)
* [Export Procedure responses in a work-order PDF](/help/work-orders/comments-activity-and-pdf#export-a-work-order-pdf)