> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.itential.com/itential-platform/6/studio/command-templates/overview/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.itential.com/_mcp/server.

# Command templates overview

> Command templates send commands to devices at runtime and evaluate responses against defined rules, used as pre- and post-checks in network procedures.

Command templates send commands to a set of devices at runtime and evaluate the responses against a defined set of rules. They are typically used as pre- and post-checks around a network procedure—such as a router upgrade or service migration—to verify device state before the change and confirm expected outcomes after it.

A template runs in two phases:

1. It executes each command against the specified devices and collects the responses.
2. Then it evaluates those responses against the rules you have defined, marking each rule as `passed` or `failed`.

This makes command templates a structured way to enforce acceptance criteria and catch unexpected device states without manual inspection.

## In this section

* [Use command templates](/itential-platform/studio/command-templates/use) — Create a template, add commands and rules, test against a live device, and manage templates in the collection view.
* [Command reference](/itential-platform/studio/command-templates/reference) — Rules, flags, severity levels, variables, and comparison operators.
* [Configuration examples](/itential-platform/studio/command-templates/configuration-examples) — Working examples for common rule and comparison patterns.

> Command templates send commands to devices at runtime and evaluate responses against defined rules, used as pre- and post-checks in network procedures.