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

# What is Visual Work Orders?

Visual Work Orders turn the full work order into a PDF-based document.

Employees complete that document directly in the app.

### How Visual Work Orders work

A Visual Work Order starts with a visual template.

You link that template to the right work type.

When you create a work order with that work type, you can use the visual layout.

### What Visual Work Orders add

Visual Work Orders help when you need:

* a fixed PDF layout for the full work order
* consistent output per work type
* one document flow instead of separate screens and forms

### What stays the same

The work order still belongs to the normal OutSmart process.

Data still stays linked to the work order record.

### Frequently asked questions

<details>

<summary>Can I still use standard work orders too?</summary>

Yes.

You can use standard and visual work orders side by side.

</details>

<details>

<summary>Do I need Visual Forms first?</summary>

Usually yes.

Visual Work Orders build on the Visual Forms approach.

</details>

<details>

<summary>Is Visual Work Orders available for every account?</summary>

No.

It is a beta feature.

</details>

### Related topics

* [**Visual Work Orders (beta)**](/marketplace-packages-and-power-ups/power-ups/forms/visual-work-orders-beta.md)
* [**What is Visual Forms?**](/marketplace-packages-and-power-ups/power-ups/forms/what-is-visual-forms.md)
* [**Create a Visual Work Order**](/marketplace-packages-and-power-ups/power-ups/forms/visual-work-orders-beta/create-a-visual-work-order.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/what-is-visual-work-orders.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.