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

# Record tool usage on a run

> Require a tool on a procedure step with a Tool field, then log which tool was used during run execution.

To [capture which tool an operator used](/build-hardware/tools/overview#tool-usage-on-runs), add a **Tool** field to a procedure step.

## Require a tool on a procedure step

1. While editing a step, add a field and choose the **Tool** field type.
2. Set the field name and help text as you would for any data-collection field.
3. To accept only tools that are currently available, select **Only accept "Available" tools**.
4. Use the **Validations** menu to constrain valid input:
   * **Type** restricts input to a tool [subtype](/build-hardware/tools/manage-tool-models#categorize-tools-with-subtypes), spanning multiple models.
   * **Part Number** restricts input to one specific tool model.

For the full list of step field types, see [Step field types](/build-hardware/procedures/steps/fields).

## Select a tool during a run

When an operator reaches the step in a run, the Tool field shows a **Select a tool...** picker listing tool inventory that meets the field's validations. The operator picks the tool they used to complete the field.

## Related

* [Step field types](/build-hardware/procedures/steps/fields)
* [Manage tool inventory](/build-hardware/tools/manage-tool-inventory)
* [Run a step](/build-hardware/runs-and-execution/step-execution)