The form is gone. The submit button was pressed, the page said thanks, and now there is a reason to check what was actually written in there: a date, a file that was attached, the phone number that may have had a digit wrong. Google Forms does not hand respondents a list of everything they have ever submitted, so the answer depends on decisions the form owner made before the link was ever sent.
That is the part worth understanding, because it also explains why some forms are easy to look back at and others are a dead end. Below are the places a copy of a response can exist, what each one requires, and what the picture looks like from the owner's side of the same form.
Why a submitted response is not simply sitting somewhere
Google Forms has two sides that barely meet. On the owner's side there is a Responses tab that holds every submission, with a summary view and a per person view. On the respondent's side there is no equivalent screen. Forms has no page that lists a respondent's own past submissions, and nothing in a Google Account collects the forms that have been filled out over the years.
What does exist is a set of settings the owner can switch on, each of which leaves a different trail. Response editing leaves a link that reopens the answers. Autosave leaves a draft. A results summary leaves a shared page of aggregated answers. Email collection makes it possible for the submission to be tied to an address at all. None of these are on by default in every form, and the respondent cannot see which ones are active until the moment they matter.
So the practical question is not "where are the responses stored" but "which of these four or five trails did this particular form leave". Checking them in order takes a few minutes and usually ends in a definite yes or a definite no.
The places a copy can exist
The confirmation screen, before it is closed
The screen shown immediately after submitting is the one chance the form gives without any setting at all. The owner can customise that message under Settings, next to Presentation, using the Confirmation message field, and many owners put the useful thing there: a reference number, a next step, a contact address. If that page is still open in a tab, it is worth reading before closing it.
An emailed copy of the answers
Some forms send the respondent an email containing what they wrote. This is a setting on the form rather than a default behaviour, and it is tied to the form collecting email addresses in the first place. A search of the inbox and the spam folder for the form's title, or for the name of the organisation that sent it, is the fastest test. If nothing arrives within a few minutes of submitting, no email copy was configured, and waiting longer will not change that.
The form URL, reopened in the same Google Account
Reopening the original link is the single most useful move, and it can produce two different results.
If the owner turned on Allow response editing under Settings next to Responses, the form offers a link back into the submitted answers, where they can be read and changed. This is the only route that shows the response itself, field by field, exactly as it was sent.
If the form was never submitted and was abandoned partway, the draft may still be there. Google documents that when a form is filled out while signed in to a Google Account, progress is saved as a draft for 30 days, and that the way to find a draft is to reopen the form URL in the same Google Account used to create it. Two caveats come from the same documentation: autosave does not work offline, and if access to the form is lost, access to the draft is lost with it. A form that shows "Saving disabled" at the top means the owner switched autosave off.
The results summary, if it was shared
Under Settings, next to Presentation, an owner can turn on View results summary, which shares a summary of results with respondents after submitting. Google notes that these summaries show full text answers or charts for each question and are visible to anyone who can respond to the form. That makes it a partial answer at best. It shows what the group said, and one individual answer may be identifiable inside it, but it is not a receipt.
The form owner
Every response is in the owner's Responses tab whether or not the respondent can see it, and Forms has a built in path for reaching them: responders can contact a form owner with questions or feedback, and the owner's help documentation covers blocking a sender from the bottom of that email. A short, specific message works better than a general one. Name the form, give the date and the email address used, and ask for the one field that matters rather than the whole submission.
Two things that quietly break the search
The first is the account. Forms ties both drafts and the editing link to the Google Account that was signed in at the time. A form filled out at work and looked for again on a personal laptop, or filled out while signed out and looked for again while signed in, produces nothing even when the setting was on. Before concluding that a form left no trail, open the link in each account that could plausibly have been used. Browser history helps here too, since the form URL will be sitting in it under the form's title.
The second is file uploads. Google's documentation on responding to forms is explicit that completing a file upload question requires signing in to a Google Account, that the owner can set restrictions on the number, type, or size of files, and that a file cannot be uploaded from a shared drive. Practically, that means an upload question is the one part of a submission most likely to have failed quietly, and also the part most worth verifying. If the form allows response editing, reopening it shows whether the file is attached. If it does not, the owner is the only person who can confirm that the attachment arrived, and asking early is better than assuming.
There is one more error worth recognising. Google documents that when "Unable to save your draft" appears, the response can still be submitted and all answers will be recorded, but closing the form before submitting may lose the progress made. That message is a warning about the draft, not about the submission, and people abandon otherwise complete forms because of it.
What the same form looks like from the owner's side
Reading the owner's view is useful even for someone who only ever fills forms in, because it explains what can reasonably be asked for.
Opening the form and clicking Responses gives a Summary tab, which appears only once at least one response exists, and an Individual tab that steps through submissions one at a time. From the same screen, Link to Sheets connects the form to a Google Sheet, and the More menu offers Download responses as a CSV file. An owner can also turn on email notifications for new responses from that menu, and Google points to a Form notifications add-on for more notification options and customised follow up emails.
The limits are equally visible. Turning on "Limit to 1 response" requires respondents to sign in to a Google Account, and Google's own note says usernames are not recorded unless the setting to collect email addresses is switched on. An owner can stop accepting responses, set a close date, or set a maximum number of responses, after which the form shows a closed message. Nothing in that toolkit gives a respondent self service access to their own submission. It is all owner side.
Which route to try, and what each one needs
| Route | Depends on | Shows | Time to check |
|---|---|---|---|
| Confirmation screen | Nothing, if the tab is open | Whatever the owner wrote there | Seconds |
| Emailed copy | Email collection plus the copy setting on the form | The full answers as submitted | A minute, including spam |
| Reopen the form link | Response editing turned on | The full answers, editable | A minute |
| Saved draft | Signed in, autosave left on, within 30 days | An unsubmitted draft only | A minute |
| Results summary | Results summary shared by the owner | Aggregated answers for everyone | A minute |
| Ask the owner | Someone reading the inbox | Whatever they choose to send back | Hours or days |
Read top to bottom and stop at the first one that works. The order is deliberate: it goes from what costs nothing to what costs someone else's attention.
If this keeps happening on forms that are sent out
There is a second reader for this question, and it is the person who runs the form rather than fills it in. Every request to confirm what someone submitted is a signal that the intake was built to collect and not to answer. Three settings remove most of that traffic before it starts.
Turn on email collection and send respondents a copy of their answers, so the receipt lives in their inbox and not in a support queue. Turn on response editing for anything that people reasonably need to correct, such as dates, file uploads, and contact details. Write the confirmation message as though it were the only thing the respondent will ever see about this process, including what happens next and how long it takes.
Those three cover the respondent's side. The harder half is what happens after the response lands, because a spreadsheet row does not record who is handling it or whether anyone replied. That is the gap between a form builder and a form tool with response management: the second kind gives every response an owner and a status, keeps the reply on the same screen as the answers, and makes the history of a request readable months later. The use cases that suffer most from the gap are recruitment, applications, and support intake, where the same person often gets asked twice for the same information. Seeing a response, its owner, its status and the replies sent in one place is the part that is worth looking at in a working demo rather than reading about.
What to change first
If this is a one off, reopen the form link in the same Google Account and search the inbox for the form's title. Those two checks settle it. If the question keeps coming back because of forms that go out under an organisation's name, switch on an emailed copy and response editing today, then decide whether the intake belongs somewhere that keeps the reply beside the response, which is the shape Halict is built around.
Q1. Can a list of every Google Form ever submitted be opened somewhere?
No. Google Forms has no history screen for respondents, and a Google Account does not collect past submissions. What can be recovered depends on each form's settings, which is why the routes have to be checked form by form.
Q2. Why did no confirmation email arrive after submitting?
Because an emailed copy is something the form owner switches on, and it depends on the form collecting email addresses. If nothing arrives within a few minutes, including in the spam folder, that setting was not enabled and the email will not appear later.
Q3. Is it possible to change an answer after submitting?
Only if the owner turned on Allow response editing under Settings next to Responses. When it is on, the form provides a link back into the submitted answers. When it is off, the only route to a correction is asking the owner to amend the record.
Q4. How long does an unfinished Google Form draft last?
Google documents drafts as being saved for 30 days when the form is filled out while signed in to a Google Account. Reopening the same form URL in that same account brings the draft back, and losing access to the form also loses the draft.
Q5. What is the fastest way to get an answer out of the form owner?
Give the identifying details in the first message: the form name, the date of submission, and the email address used. Asking for the one field in question rather than the whole submission also makes the reply easy to send, which usually means it arrives sooner.