Forms change. You reword a question, add a page, drop a field that wasn't earning its place. The problem that creates is in your results: if a response is shown against today's form, an answer given six weeks ago gets read under a question that no longer exists — or worse, under a different question that happens to sit in the same spot.

big solves that by keeping a version of your form every time its questions change, and stamping each response with the version it was answered on.

How versions are created

• Saving changes to your form's questions creates a new version automatically and makes it live. You don't have to remember to snapshot anything.
• Renaming the form or changing its status doesn't create a version — nothing about the questions changed.
• Saving without making changes creates nothing.
• Save as version does the same thing as a normal save, but lets you give the version a name — "before the spring rewrite", "short version for stories" — so you can find it later.

Versions are numbered in order (v1, v2, v3…) and named ones show their label alongside.

Going back to an older version

Open the version list on your form and choose Set active. That version's questions become the live form immediately, and anyone who opens your public link from that moment sees them.

Setting an old version active doesn't erase anything in between — those versions stay in the list, and the responses collected under them stay attached to them.

Duplicate version copies an older version into a new one without making it live. Use that when you want to build on an old draft: duplicate it, edit it, then set it active when you're happy.

What this means for your results

• Responses show which version each person answered. A question that didn't exist in someone's version is shown as not asked — clearly different from a question they were asked and left blank.
• Stats can be read per version, so you can answer the question that actually matters: did the change help? Shorten a form from five pages to three and you can compare the finish rate before and after, instead of averaging two different forms together.
• Drop-off is tracked per version too. Since pages get added and reordered, drop-off numbers pinned to a version stay meaningful — otherwise editing a form would silently rewrite the history of every number.

Your public link never changes

Versioning is invisible to the people filling in your form. Your /f/ link stays the same, it always shows the live version, and switching versions doesn't break a link you've already shared.

Good to know

• Versions are read-only snapshots. You edit the live form; you don't edit an old version in place. To change an old one, duplicate it first.
• Existing forms already have a v1. Everything created before versioning was added is recorded as v1, and every response already collected is attached to it.
• Deleting a version doesn't delete the responses collected under it — those responses simply stop being tied to a stored definition and fall back to the live one.