> 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/visual-work-orders-beta.md).

# Visual Work Orders (beta)

Visual Work Orders combine work orders with Visual Forms.

They give employees a work order that appears as a fillable PDF.

Use this when the full work order must follow a fixed layout.

### When Visual Work Orders fit best

Use Visual Work Orders when you need:

* a paper-like work order layout
* one fixed PDF for the full job flow
* different document templates per work type

{% hint style="info" %}
Visual Work Orders are in beta.

Behavior and availability can still change.
{% endhint %}

### Start here

* [**What is Visual Work Orders?**](/marketplace-packages-and-power-ups/power-ups/forms/visual-work-orders-beta/what-is-visual-work-orders.md)
* [**Activate Visual Work Orders beta**](/marketplace-packages-and-power-ups/power-ups/forms/visual-work-orders-beta/activate-visual-work-orders-beta.md)
* [**Create a Visual Work Order**](/marketplace-packages-and-power-ups/power-ups/forms/visual-work-orders-beta/create-a-visual-work-order.md)

### How it differs from a standard work order

A standard work order uses the regular work order screen and related forms.

A Visual Work Order shows the full job as a PDF-based document.

### Related topics

* [**What is Visual Forms?**](/marketplace-packages-and-power-ups/power-ups/forms/what-is-visual-forms.md)
* [**Use Visual Forms in work orders**](/marketplace-packages-and-power-ups/power-ups/forms/use-visual-forms-in-work-orders.md)
* [**Forms**](/marketplace-packages-and-power-ups/power-ups/forms.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/visual-work-orders-beta.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.