Deleted Google Forms Responses Still in Sheets?

A response that disappears from a fresh Forms CSV can remain in the spreadsheet your team uses. The linked sheet contains copies of submissions; deleting a response in Forms does not remove that external copy. For a few identifiable entries, clean up the corresponding sheet rows. For an outdated list that is difficult to reconcile, rebuild it in a new response spreadsheet.

Before rebuilding, look for information that exists only in the sheet. Staff assignments, contact notes, and processing statuses are not form answers just because they sit beside them. A new response destination will not reconstruct those additions.

Identify which record still contains the response

A Google Docs Community question describes exactly this mismatch: a deleted response was absent from a downloaded CSV but remained in the shared View in Sheets destination. An export created now and a spreadsheet collecting responses over time are different records.

Google’s Form reference distinguishes the form’s response store from external response destinations. Its deletion methods remove submissions from the store and summary without removing spreadsheet copies.

To take a fresh snapshot from Forms, open Responses, choose More, and download the responses as a .csv file. Keep its download time when comparing lists; a colleague’s older export will not update when the form changes.

Deleting a spreadsheet row is not a command to delete a Forms submission either. Decide whether you want to remove an unwanted submission altogether or exclude it from an operational report while retaining its history. A cancelled registration might need a cancellation status; a test submission might need deletion. Those are different reporting decisions.

Remove individual entries without mismatching answers

Match submissions by their contents, not by row position. Sorting or deleting rows changes where records appear in Sheets, and the header row is not a submission. A person can submit more than once, so a name or email address alone may not identify the entry you intended to remove.

Use the fields actually collected: submission time, email if available, event or session, and the answers themselves. If anonymous entries are indistinguishable, do not invent an identity or assume that the later row must be the duplicate. Resolve which records belong in the report before deleting them.

1. In the form editor, open Responses → Individual and locate the submission.
2. Find the corresponding entry in the linked sheet and compare its answers. Preserve a copy first if you still need that information.
3. Delete the individual response in Forms and confirm. Skip this step if it has already been deleted there.
4. Remove the matching sheet entry, then inspect both lists again.

Google’s response storage guide documents individual deletion and warns that Forms response deletion cannot be undone. In Sheets, right-click a row number and choose Delete row, following its row deletion instructions.

Deleting one cell and shifting values upward can pair an email with someone else’s answers. Deleting the whole row also affects notes or unrelated tables placed on that row. Choose the range according to the actual layout. Merely hiding a row does not remove its contents.

Rebuild the list in a new spreadsheet

If Forms contains the correct submissions but the old sheet is hard to reconcile, use a new response destination. The University of Tokyo’s Forms guide explains that connecting a sheet transfers responses already collected, as well as enabling subsequent collection. It also explicitly notes that deleting responses does not remove them from an existing linked spreadsheet.

Keep the old file address before changing the link. If you can briefly pause submissions, the current published-form controls are Published → Accepting responses → off → Save. Google describes them in View and manage form responses. If submissions must remain open, record the comparison time and separately check entries arriving afterward.

1. In Forms, open Responses → Summary → More → Unlink form and confirm.
2. Use Select destination for responses → Create a new spreadsheet. Give it a name distinguishable from the previous file.
3. Compare its entries with the responses still held in Forms, including examples you deliberately kept and entries you removed.

Unlinking leaves the old spreadsheet’s data intact and stops new responses being sent there. It does not erase the old list or turn everyone’s existing bookmark into the new file. A colleague opening the old address will still see that old file.

Choosing an existing spreadsheet is also possible. When several response tabs exist, verify the tab as well as the file. Stony Brook IT specifically points users toward tabs such as Form Responses 1 and Form Responses 2 when data appears missing. A spreadsheet filename alone does not tell you which response tab you are reading.

Move staff-added information by matching submissions, not by pasting a notes column into the same row numbers. Removed entries may have shifted the sequence. An existing unique application ID can help; an email shared across multiple registrations cannot always do the same job. Match the session and other relevant answers where needed, and leave ambiguous matches unresolved instead of assigning notes to the wrong person.

Also inspect report inputs. A formula or pivot table still reading the previous response range can continue reporting the old list even when the new sheet is correct. Decide whether to update the existing report’s input or rebuild the report alongside the new data. Reconnecting Forms does not perform that reporting work for you.

Find a registration you deleted by mistake

For a registration accidentally deleted in Forms, first look for the matching row in the linked spreadsheet. Check the session and answers before using it to contact the applicant or add a processing note. If the row is gone too, try a CSV saved before the deletion. You can continue working from those saved details, but Forms cannot undo the deletion: the registration will still be missing from its response list and summary. A fresh CSV downloaded afterward will omit it too.

If only a sheet row was deleted and the submission remains in Forms, rebuild the response list from the form instead. That can recover the submitted answers, but it cannot reconstruct processing notes that staff entered only in Sheets.

For those notes, inspect the spreadsheet’s version history. You need edit access to browse earlier versions. Open Last edit at the top right, locate a version from before the deletion, and use its More menu to make a copy. Google’s version history guide documents copying an earlier version separately from restoring it over the current file.

Use that copy to find the missing row and compare it with current work. Restoring the entire live sheet to an older state can also affect changes colleagues made after the accidental deletion. For recovering one record, inspecting a separate copy lets you identify the missing values before deciding what to move back.

Switch the team to the correct list

Replace the working link wherever the team uses it: a pinned message, an instruction document, or a saved report. If the old sheet remains as an archive, label it accordingly. Otherwise, the owner can work from the cleaned list while colleagues keep processing outdated entries.

Check access on the response file too. The response storage guide says form collaborators receive access when a new response spreadsheet is created, but later form permission changes do not automatically synchronize with the sheet. Removing someone from the form does not by itself remove their access to the old response spreadsheet.

If you paused collection, reopen it and check where the next submission lands. A clearly identifiable test submission can confirm that both Forms and the intended destination receive it. Afterward, remove that test entry from both places. The handover is complete when new responses reach the intended file and the team uses that same file.