Someone has submitted the form and got something wrong. A typo in an email address, the wrong date, a number transposed. They ask for the link back so they can fix it, and the search for a setting begins. It is a reasonable thing to look for, because almost every other system that accepts input lets the person who typed it correct it.
Microsoft Forms does not have that setting. Not hidden under an advanced menu, not gated behind a licence, not present for quizzes and missing for forms. The full list of settings is published, and nothing in it turns on response editing. Once the submit button is pressed, the response is fixed. So the question worth answering is not where the setting is but which of several different problems is actually being solved, because each one has a different route out.
What the settings list actually contains
Under the response options, Microsoft Forms offers Accept responses, which turns collection on and off. Start date and End date, which schedule that window. Set time duration, a per respondent timer, where the documentation notes that respondents cannot edit their answers after the timer ends. Shuffle questions, with an option to lock specified ones in place. Disable question number for respondents. Show progress bar, available only on multi section forms. Hide Submit another response, which removes the link that otherwise appears on the completion page. Customize thank you message.
Under response receipts there are three more. Allow receipt of responses after submission, which gives the respondent the option to save or print a PDF of their filled in answers on the thank you page. Get email notification of each response. And Get smart notification emails to track the response status, which sends reminders when the invitation channel was used.
That is the whole set, and it is worth reading closely because two of those entries are frequently mistaken for the thing being looked for. The receipt setting produces a PDF of what was submitted, not a link back into the form. The receipt is proof of what was sent, not a way to change it. And Hide Submit another response is the nearest neighbour to an edit feature, which is a clue to the only route Forms supports natively.
There is also nothing on the owner's side. On the Responses Overview screen, the options for responses are to delete all responses, print responses, or share a summary link. Delete all, not delete one, and certainly not edit one. An owner who spots a wrong entry has the same options as everyone else, which is to say none.
Editing the Excel export does not edit the response
This is the route most teams try second, and it fails in a way that is easy to miss for weeks.
Opening results in Excel gives a workbook stored in OneDrive for work or school, or in SharePoint for a group form, with a live data connection back to the form. New responses appear in the workbook as they arrive. It looks exactly like an editable copy of the data, and correcting a cell feels like correcting the record.
Microsoft's documentation settles it in one sentence: any changes made to the workbook will not modify the content of the form. The connection runs one way. The form is upstream, the workbook is downstream, and a hand edit in the workbook is a local annotation that the form knows nothing about.
Two further details decide whether that annotation even survives. The data update can only be triggered by the form owner and by other users in the organization who have edit permission on the workbook, and external users cannot trigger it at all. And if the Open in Excel button reappears in the form, the live connection has been disconnected and has to be set up again. Neither of those is a disaster on its own, but between them they mean nobody can say with confidence what a given cell represents: the respondent's answer, or a colleague's correction, or a correction that was later refreshed away.
If a workbook is going to be the working copy, the honest version is to download a copy instead. That gives an offline workbook with no relationship or connection to the form, which at least makes the divergence explicit rather than accidental.
The same logic rules out the other variation on this idea, which is to push responses into a workbook or a database with Power Automate and edit them there. The edit is fine. What breaks is the assumption that the form and the destination still agree, because from the first hand correction onwards there are two versions of the truth and no field anywhere recording which one is current. Teams discover this at the worst possible moment, which is when somebody quotes the form back to a respondent.
The resubmission route, and how to make it survivable
The only route Microsoft Forms supports natively is letting the person submit again and treating the newest submission as the true one. It works, but only if three things are set up deliberately.
Leave the door open
Leave Hide Submit another response unchecked, which is the default, so the completion page keeps offering another go. Then make sure One response per person is off, because that setting exists precisely to block this. Note that the per person limit is only offered when responses are restricted to the organization, so on a form open to anyone it is not a factor.
Give yourself something to match on
A second submission is a new row, not an update, and the respondent ID is exclusive to each response, so it cannot join the two. Something else has to.
On a form restricted to the organization with Record name on, the workbook's first five columns carry respondent ID, start time, completion time, name, and email address, and name or email is a usable key. On an anonymous form, those name and email columns are blank, so a plain text email question has to be asked and then trusted, which is a real weakness: nothing stops a typo in the very field the deduplication depends on.
Tell the respondent what to do
Most people do not resubmit unprompted, because the completion page does not explain that resubmitting is how corrections work. Saying so in the thank you message is a one line change that converts a support email into a second submission.
The residual cost is the one this route never sheds. Duplicates accumulate in the response set, every export needs the same deduplication logic applied again, and anyone reading the raw responses without knowing the convention will read an old answer as current. It is a workable arrangement for a low volume form and a genuine liability on a busy one.
Routes that make the response an editable record
The alternative is to stop treating the submission as the storage. Three options exist, and they differ mainly in how much building they require.
| Route | Respondent can fix their own entry | Team can fix an entry | Change history | Build effort |
|---|---|---|---|---|
| Resubmit and deduplicate | Yes, by submitting again | No | No | None |
| Land responses in a list | No, unless given list access | Yes | Version history on the item | Low |
| Rebuild the form in Power Apps | Yes, if built that way | Yes | Whatever is built | High |
| Form tool with editable responses | Depends on the tool | Yes | Usually built in | None |
Land the submission in a list instead
Microsoft Lists can take a form of its own, and the submission becomes a list item. That is a different kind of object from a form response: an item is a record, and anyone with permission on the list can correct a field in it, with the list's version history showing what changed. The newer Lists forms experience also added conditional branching, extra field types including attachments, images, location, and lookup, form scheduling, and per form notification subscriptions.
The catch is about who can edit. Correcting an item requires permission on the list, and giving that to an outside respondent means giving them access to the list, which for most intake scenarios is the wrong trade. Lists solves the problem of the team being unable to fix an entry. It does not, on its own, solve the problem of the respondent wanting to fix their own.
Rebuild it in Power Apps
A Power Apps form over the same list can look up an existing item and let a signed in person edit it. This is the option that genuinely delivers what the original question asked for, and it is also the option that turns a ten minute form into a small application with an owner, a lifecycle, and a person who has to maintain it after they change jobs. Worth it for a process that will run for years. Not worth it for one round of event registrations.
The question underneath
Every one of these routes is answering the same design question, and it is worth asking it directly, because the answer decides the tool rather than the other way round.
Is a submission an event, or is it a record?
An event happened at a point in time and should not change. A survey answer is an event. A quiz attempt is an event. Editing them would corrupt the measurement, and Forms is built on this assumption, which is why it has no edit setting and why that is a defensible decision rather than an omission.
A record describes something ongoing. An application, an enquiry, a repair request, a membership. It arrives with some fields filled and then accumulates more: who picked it up, what stage it reached, what was replied, and yes, corrections to what the person typed in the first place. Forcing a record into a system built for events is what produces the spreadsheet with a hand maintained owner column and the two familiar failures: the applicant who gets two different answers from two colleagues, and the applicant who gets none.
Most of the forms that trigger this search are records wearing a survey's clothes. That is why the search happens at all. Nobody looks for an edit setting on a satisfaction survey, and everybody looks for one on an application. Tools built for the record case treat a response as something with an owner, a status, and a history, and the features list of any such tool is a quick way to check whether it does: look for whether a response can be reopened and changed, and whether the change is logged.
What to change first
Pick which of the two problems is actually urgent. If a handful of respondents occasionally need to fix a typo, turn off One response per person, say in the thank you message that resubmitting replaces the earlier answer, and deduplicate on email at export time. If the real trouble is that the team cannot correct or annotate what arrived, no Forms setting will help, and the next step is to look at what a response looks like once it is a record rather than a row. The demo is the quickest way to see whether that shape fits the work.
Q1. Is there any setting in Microsoft Forms that lets respondents edit their answers?
No. The published list of form settings covers accepting responses, scheduling, timers, shuffling, the progress bar, hiding the submit another response link, the thank you message, and response receipts. None of them reopens a submitted response for editing.
Q2. Can the form owner correct a wrong answer in a response?
No. On the Responses Overview screen the available actions are to delete all responses, print responses, or share a summary link. There is no per response edit, and no per response delete either.
Q3. If the Excel workbook is edited, does the form response change?
No. Microsoft states that changes made to the workbook will not modify the content of the form. The live connection carries data from the form to the workbook only, so a hand edited cell is a note in the workbook and nothing more.
Q4. How do you handle duplicates when respondents resubmit to correct something?
Match on an email address rather than on the respondent ID, because the ID is unique to each response. On an organization only form with Record name on, the name and email columns are populated automatically. On an anonymous form an email question has to be asked and the answers deduplicated by completion time, keeping the latest.
Q5. Does collecting into a Microsoft List let respondents edit their own submission?
Not by itself. The submission becomes a list item that colleagues with permission on the list can correct, with version history. Letting the original respondent edit it means granting them access to the list, which is usually not appropriate for people outside the team.
Q6. Why does the response receipt setting not help with corrections?
Because it produces a PDF of the answers as submitted, saved or printed from the thank you page. It is a record of what was sent, useful for the respondent's own files and for disputes, but it contains no link back into the form.