> 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/use-workflows-in-the-mobile-app.md).

# Use workflows in the mobile app

Employees use workflows directly inside the OutSmart app.

When a work order has a linked workflow, the app opens it automatically.

### What employees see

The app shows:

* the current step
* the next action
* the workflow progress
* validation when required data is missing

Employees move through the workflow with **Next**.

They can only continue when the current step is complete.

### Typical flow in the app

{% stepper %}
{% step %}

### Open the work order

Open a work order that uses a workflow.

The first workflow step appears.
{% endstep %}

{% step %}

### Complete each step

Add the required information for the current step.

This can include timers, materials, photos, forms, or signatures.
{% endstep %}

{% step %}

### Move to the next step

Tap **Next** to continue.

If required data is missing, the app keeps you on the current step.
{% endstep %}

{% step %}

### Finish with Send

Complete the final **Send** step.

The work order is then sent back to the office.
{% endstep %}
{% endstepper %}

### Platform notes

The exact layout can differ between **iOS** and **Android**.

The workflow logic stays the same.

### If an employee leaves the workflow

Employees can leave a work order and return later.

Their progress is kept until they complete the workflow.

### Frequently asked questions

<details>

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

Usually not.

They need to complete the current step first.

</details>

<details>

<summary>What happens if a step fails validation?</summary>

The app shows that the step is incomplete.

The employee cannot continue until it is fixed.

</details>

<details>

<summary>Can employees return later?</summary>

Yes.

Progress is preserved until the workflow is finished.

</details>

### Related topics

* [**Workflows**](/marketplace-packages-and-power-ups/power-ups/workflows.md)
* [**Introduction to Workflows**](/marketplace-packages-and-power-ups/power-ups/workflows/introduction-to-workflows.md)
* [**Workflow settings and device policies**](/marketplace-packages-and-power-ups/power-ups/workflows/workflow-settings-and-device-policies.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/use-workflows-in-the-mobile-app.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.