> 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/manage-form-versions.md).

# Manage form versions

Forms change over time as your process changes.

When you update a form, the change affects future use of that form.

### What stays the same

Completed form results on older work orders stay as they were when they were filled in.

That means older work orders keep the version that was used at that time.

### Why careful changes matter

Careful updates help you:

* avoid unnecessary disruption
* keep future work clear and correct
* preserve trust in historic results

{% stepper %}
{% step %}

### Open the form

Go to **Settings → Forms**.

Open the form you want to update.
{% endstep %}

{% step %}

### Change only what is needed

Make the smallest change that solves the problem.

Avoid broad edits when a small edit is enough.
{% endstep %}

{% step %}

### Save the form

Save the update.
{% endstep %}

{% step %}

### Test the new version

Use the updated form on a new work order.

Check the form flow and the PDF output.
{% endstep %}

{% step %}

### Review older results if needed

Open older work orders when you need to confirm historic results still display correctly.
{% endstep %}
{% endstepper %}

### Good change practices

* test before you roll out major changes
* avoid renaming fields unless necessary
* plan major edits outside busy periods

### FAQ

<details>

<summary>Do old work orders change when I update a form?</summary>

No.

Completed form results stay attached to the work order as they were.

</details>

<details>

<summary>Can I undo a form change?</summary>

That depends on your setup.

It is safest to test before you save major edits.

</details>

<details>

<summary>Should I update forms during busy periods?</summary>

Usually not.

Quieter periods make testing easier.

</details>

### Related topics

* [Create a form](/marketplace-packages-and-power-ups/power-ups/forms/create-a-form.md)
* [Export and print Forms](/marketplace-packages-and-power-ups/power-ups/forms/export-and-print-forms.md)
* [Create a Visual Form](/marketplace-packages-and-power-ups/power-ups/forms/create-a-visual-form.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/manage-form-versions.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.