# Versioned forms and entry history

Canonical: https://useformwork.com/product/versioned-forms

Updated: 2026-09-17

Publish a new form without silently changing the schema behind existing entries, and inspect revisions to submitted answers.

FormWork keeps form versions and entry revisions as separate concepts. A **form version** defines the fields, rules, and workflows. An **entry revision** records changes to an entry's answers. Together, they help explain both what a form meant and how a response changed.

## Example: changing an application process

Suppose version 1 asks applicants for three pieces of information. Your team decides that future applications also need supporting evidence.

1. Create or edit the draft version and add the evidence field and validation.
2. Preview and test the draft, including its workflow behaviour.
3. Publish the draft as the next version.
4. New entries use the newly published version. Existing entries, including entries already in progress, remain associated with their original version.

This avoids silently adding a new requirement to an older entry. It does not automatically migrate existing answers into the new schema.

## Draft, published, and archived versions

A form has at most one draft and one published version. Publishing replaces the current published version; earlier versions are archived. Archived versions can be viewed but do not have a preview. Workflows belong to the form version, so review workflow changes as part of publishing.

Draft previews create ordinary entries. They are not separately flagged as test data. Keep test data identifiable and follow your own cleanup process before treating reports as production results.

## Inspect changes to an entry

The [entry revision history](/docs/entries/revisions) records answer changes with their source, such as an administrator or a workflow. The current UI shows the latest 50 revisions. Changes to linked metafield entries have their own history, and rapid metafield edits may be batched.

Revision history is not a one-click restore feature. To correct an entry, make an administrator edit. There is also no automatic rollback of a published form: recreate the desired configuration in a draft, check it, and publish it.

Read the [form version guide](/docs/forms/form-versions) for the exact lifecycle, or see how versions fit into an [application review process](/use-cases/application-review).