> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/workflows/introduction-to-workflows.md).

# Introduction to Workflows

**Workflows** guides employees through a fixed set of steps when they complete a work order.

You use it to make sure the right data is registered in the right order.

A workflow is linked to one or more **work types**.

When an employee opens a matching work order in the app, the workflow starts automatically.

### What Workflows helps you do

* standardize how work orders are completed
* require key registrations before sending
* reduce missed hours, materials, photos, and signatures
* improve data quality in the BackOffice

### How it works

A workflow consists of **steps**.

Each step covers one action, such as checking customer details, starting a timer, adding pictures, filling in a form, or capturing a signature.

Employees move through the workflow step by step.

They can only continue when the current step is complete.

### When to use Workflows

Workflows is useful when:

* technicians follow the same process on every job
* you need mandatory checks before completion
* you want cleaner handover from field to office

### What employees see

Employees see the workflow in the mobile app when they open the work order.

The app shows the current step, the next action, and the remaining steps.

### Frequently asked questions

<details>

<summary>Can I use different workflows for different work types?</summary>

Yes.

You can create multiple workflows and link each one to the right work types.

</details>

<details>

<summary>Are workflows required for every work order?</summary>

No.

Only work orders linked to a workflow use one.

</details>

<details>

<summary>Can employees skip workflow steps?</summary>

Usually not.

Employees must complete each step before they continue.

</details>

### Related topics

* [**Create and manage workflows**](/marketplace-packages-and-power-ups/power-ups/workflows/create-and-manage-workflows.md)
* [**Workflow step types**](/marketplace-packages-and-power-ups/power-ups/workflows/workflow-step-types.md)
* [**Use workflows in the mobile app**](/marketplace-packages-and-power-ups/power-ups/workflows/use-workflows-in-the-mobile-app.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/workflows/introduction-to-workflows.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.