We are excited to be kicking off this work to allow edits for finalized/sent forms 
We wanted to share a bit about where we landed based on all the user feedback and what to expect next.
Who is this designed for?
Workflows that want to enable data collectors to edit finalized or sent forms so they can capture new insights or fix mistakes because they have the context in the field.
Who is this not designed for?
Workflows that prefer all edits to be made by project managers to maintain integrity and quality, which is the default experience or the most common. Allowing edits on device after submission also isn’t suitable for workflows that use Entities. Entity-based workflows can introduce Entity update forms to allow edits.
How will this work? 
- Allowing edits on device will be off by default and configurable on a per-form basis. We will be sharing more in a spec design thread soon.
- If a form is configured to allow edits, a data collector can edit locally, and save an edit as a draft until they are ready to finalize. Once it’s sent, project managers will see it in Central.
- The data collector will be able to view all edits when viewing their sent forms.
- Once an edit is made in Central, the data collector won’t be able to make any edits. They will be able to open the submission for editing but when they try to send the edit, it will be rejected. Communicating that an edit has happened in Central will have to happen outside of Collect.
- Edits can only happen on the most recent version. For example, if I try to edit “Pine”, but I have already made an edit “Pine (Edit 1)”, I will be prompted to edit "Pine (Edit 1)" instead.
Future considerations 
- Clone form: making a copy or cloning your form is something that will come later.
- Send back for revisions: this is a much bigger piece of work that we know will add a lot of value but isn’t something that will come any time soon in the roadmap.
- Allow edits for a certain period of time: allowing edits for 2 days or restricting the number of edits came up in user feedback and is something we want to hear feedback on once we’ve released this first version.
What’s the timeline? 
We will start implementation shortly. This functionality is planned for Collect v2025.2, currently projected for April or May.
If you’re unsure if this would be helpful for your workflow, you don’t need to worry because it will be off by default. If you have questions, please add them to this thread.