Based on user feedback, we are considering allowing data collectors to make edits to finalized or sent forms that are already on their device. This functionality would be off by default.
We discussed this topic on the April 3rd Insiders call. I'll share the takeaways and summary in a subsequent post.
Proposal
Provide additional support for workflows that want to enable data collectors to edit finalized or sent forms so they can capture new insights or fix mistakes. This is valuable for project managers because the data collector is in the field and has the context.
Example scenarios we've heard:
We collect demographic information on households. A data collector can mistakenly enter wrong date of birth or select the wrong gender and submit.
Enumerators are in a hurry during the day to reach their targets. Fixing any mistakes and resubmitting gives them time to review and check for any errors and as a project manager I prefer them to do it.
We currently imagine that the functionality would be accessed as a new option shown when tapping on a finalized or sent form in a form list:
In Central, these edits would be tracked exactly like a web-based edit: the change would appear in the submission activity feed and the submission's state would change to Edited.
We know there are workflows where making edits after the form is sent isn't appropriate, and project managers want to maintain control over the data quality process, which is why it would be off by default.
Longer-term, we may consider supporting a more structured experience where project managers on the server can "send back" submissions to specific data collectors with comments. For now, this idea is about editing submissions already on the device with data collectors having control of when that happens. Project managers would have to request edits through another channel (phone call, WhatsApp, etc).
In scope for a short-term feature 
- Editing finalized or sent forms (off by default)
- Configured in form design
- Collect users can make multiple resubmissions
- Once an edit is made in Central, Collect users can’t edit
- Data collector would have option to submit as new
- When deleted in Collect, it can only be edited in Central
Out of scope 
- Edit of submissions collected by other device
- Collect would work off local data only
- No “Send back submission” with comments or issues
- Workaround is to use other channels (e.g. whatsapp)
- Can implement something like it with Entities
Why are we considering this functionality now?
Over the past year, user feedback has centered on giving data collectors more control over their submissions, as reviewing and editing submissions has been limited to Central users. In our user research about form finalization, we heard that people get confused about what state they are in, when they can edit, and when forms have been sent.
Now that finalization is truly final, we have clearer workflows and the foundation for new Entities functionality.
Depending on your needs, you could decide what option works best for your workflow:
Relationship to Entities: The big picture for Entities is supporting more workflows and improving data flow between “field” and “office”. This concept provides a different way to get at this goal and in particular supports folks who may not have longitudinal workflows but have more need for coordination between field and office.
Let us know what you think
What does your editing process look like? Does your workflow require editing or fixing mistakes after the data collector sends their forms? Even if you are not sure you would want to use this functionality, that is helpful feedback!
) drafts, and only then calls me to say 'oh the form is out of date/wrong/missing something/can we update-change this', and I have to tell them, yes, of course, however you have to trash all those drafts and start again once you sync to the new definition. So being able to apply the collected values to the most recent definition for drafts / sent forms would be very helpful