Every time you click Save new version in Dapple Form Builder, your form is versioned and updated. New creators see the new version immediately; existing submissions stay linked to whatever version they originally used. You can always see the exact form a creator saw when they submitted. The whole versioning model is automatic — you just save.
Can I update a form after submissions have opened?
Yes — you can edit a form at any time, even mid-opportunity. New creators see the updated version the moment you click Save new version. There's no need to pause, close, or reopen the project.
What happens to existing submissions when I update the form?
Existing submissions are not modified.
Each submission stays linked to the exact form version used at the time of submission.
When you view an old submission, you see the original form version with the original questions and answers.
This means you never lose context — you can always see what was asked, regardless of how the form has changed since.
How to update a form
Open Settings → Organisation Settings → Projects.
Select the project you want to change.
Click Form Builder.
Make your changes — edit fields, add fields, change design, etc. Form Builder auto-saves continuously.
When you're ready to make the changes live, click Save new version in the top-right corner.
New creators immediately see the new version.
How do I view previous versions?
Open Form Builder → Design & Settings and click into Version History to see every version saved over time. This is useful for tracking changes, comparing previous versions, or checking exactly what creators saw at a specific date. You can review old versions but creators always submit through the latest published version.
When should I update vs duplicate?
You want to… | Best approach |
Fix a typo, add a missing field, tweak copy | Edit the existing form. Click Save new version when done. |
Run a new cycle of the same programme | Duplicate the project. Edit the form on the duplicate. The original stays as a record of last year's setup. |
Change the form's purpose or scope significantly | Duplicate the project. Start a fresh form rather than rebuilding the live one. |
Best practice for form versioning
Duplicate the project for a new cycle rather than editing your live form — it preserves the old setup as a clean record.
Click Save new version explicitly when you've made meaningful changes. Auto-save keeps your work but doesn't publish it.
Test changes by previewing the form in a new tab before clicking Save new version on a public project.
Use Version History as a paper trail — useful for legal reviews or to revert quickly if a change breaks something.
Where to go next