> 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/mobile-app/ios-outsmart-app/core-functionalities/workflows.md).

# Workflows

Complete a work order step by step with a guided workflow.

## Workflows

### Workflows

A **workflow** guides you through a work order one step at a time. Your company configures the steps. Complete them in order.

#### How workflows work

* A work order uses a workflow based on its **type of work**.
* Steps have a fixed, numbered order.
* A step unlocks after earlier steps are complete.
* Open **Client Information**, **Job Details**, **Schedule**, and **Equipments** when enabled.

#### Work through a workflow

{% stepper %}
{% step %}

#### Open the work order

Open a workflow work order from **Overview**.
{% endstep %}

{% step %}

#### Complete each step

Tap the first step and complete it.

Steps can include timers, materials, photos, forms, objects, comments, signatures, and email.
{% endstep %}

{% step %}

#### Move to the next step

Complete the current step to unlock the next one.

Continue until every step is complete.
{% endstep %}

{% step %}

#### Send the work order

Use the final step to review and send the work order to BackOffice.
{% endstep %}
{% endstepper %}

#### Keep in mind

* You cannot skip ahead while earlier steps remain incomplete.
* Complete required forms before sending the work order.
* Available info items depend on your company's settings.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledge.out-smart.com/mobile-app/ios-outsmart-app/core-functionalities/workflows.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.