Undoing a Change to a Field

See the values a field has held, and put an earlier one back without retyping it.

Someone types over an answer that was already correct. It happens on every long form, and until now fixing it meant opening the form’s change history, working out which section the field belonged to, navigating there, and retyping the old value from memory.

Every field now carries its own history. You can see the values it has held, who set each one, and put any of them back in a click.

Who this is for. Anyone editing a form in your workspace. Clients filling in a form through an intake link don’t see field history — it’s a staff tool.

Find the history for a field

Open the form and go to the section containing the field. Hover over the question — or tab to it — and a small clock icon appears next to the field’s label. Click it.

The icon stays hidden until you hover because most fields have history and you rarely need it. On a touchscreen it’s always visible.

If there’s no icon, the field has no earlier values to offer. A field shows one only once it has been changed more than once — a field you filled in and never touched again has nothing to go back to.

Read the list

The panel lists the values the field has held, newest first. Each row shows the value, who set it, and how long ago.

The top row is marked Current and has no button — it’s what the field holds right now.

Values are shown the way you entered them, not the way they’re stored: a country appears as its name rather than its code, dates use the same format as the date picker, Yes/No questions read as Yes and No, and a field marked as not applicable reads Does Not Apply.

Typing is grouped, so a value you typed in one sitting appears as one entry rather than one entry per keystroke. Coming back later and changing the same field creates a separate entry.

Put a value back

Click Restore on the row you want. The field updates straight away — there’s no confirmation step, because nothing is destroyed.

The value you replaced stays in the list, so you can restore it again if you change your mind. Every restore is recorded in the form’s change history like any other edit, showing who did it and marked as Restored.

Restoring a Yes/No answer doesn’t bring back its follow-up answers. If a question reveals extra fields when you answer Yes, restoring the Yes re-reveals whichever answers are still stored underneath it. Check them before submitting — the same is true when you change the answer by hand.

When you need more than the last few changes

The panel shows a field’s recent changes. For anything older, or to see the whole picture across the form, use Change History on the form overview.

That page lists every change ever made to the form, including ones the field panel groups together. Each row’s field name links straight to that field in the editor, so you can go from a change to the field it affected without hunting for it.

What it doesn’t cover

  • Uploaded documents. Photos and passport scans aren’t restorable this way — replace the file instead. See document storage.
  • Deleted rows. Removing a repeated entry — an extra address or a previous trip — isn’t undone from here. Add the row again.
  • Bulk translation. Translating or resetting a form’s translated values doesn’t create field history.