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

# Use Visual Forms in the mobile app

Employees open Visual Forms from the work order in the app.

They fill in the form on top of the PDF.

### What employees do in the app

* open the work order
* open the Visual Form
* fill in the fields on the PDF
* save the result

{% stepper %}
{% step %}

### Open the work order

Open the work order that contains the Visual Form.
{% endstep %}

{% step %}

### Open the form

Select the Visual Form on the work order.
{% endstep %}

{% step %}

### Fill in the form

Add the answers in the right places on the PDF.
{% endstep %}

{% step %}

### Save your work

Save the form.

Then continue with the work order.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Test the form on the device your team uses most.
{% endhint %}

### Frequently asked questions

<details>

<summary>Can employees complete a Visual Form on site?</summary>

Yes.

That is a common use.

</details>

<details>

<summary>Does the form still look like the PDF?</summary>

Yes.

That is the main difference from a standard form.

</details>

<details>

<summary>Should I test the form on mobile first?</summary>

Yes.

That helps you check spacing and readability.

</details>

### Related topics

* [**Forms**](/marketplace-packages-and-power-ups/power-ups/forms.md)
* [**Create a Visual Form**](/marketplace-packages-and-power-ups/power-ups/forms/create-a-visual-form.md)
* [**Use forms in the mobile app**](/marketplace-packages-and-power-ups/power-ups/forms/use-forms-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/forms/use-visual-forms-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.