How to close a Google Form, and how to close it automatically at a set time

The deadline was midnight and the form is still open at nine the next morning. Four extra submissions came in overnight, two of them from people who genuinely did not know they were late, and now somebody has to decide whether to count them. Closing a Google Form takes one click, which is exactly why it gets forgotten: there is nothing in the form itself that remembers the deadline unless it has been told to.

There are now two different ways to close a Google Form, and they solve different problems. The manual switch stops responses the moment it is flipped. The close date and response limit settings, which Google added at the start of 2026, stop them at a time nobody has to be awake for. What follows covers both, what respondents actually see when a form is closed, the older workarounds and whether they are still worth using, and the part that closing does not solve.

What closing a Google Form actually means

Closing a form changes one thing: new submissions are refused. Everything else stays where it was. The responses already collected remain in the Responses tab and in any linked spreadsheet, the form itself is not deleted, the link still resolves, and anyone who opens it lands on a page saying the form is no longer taking answers rather than on a blank question.

That matters because several things that feel like closing are not the same operation:

• Deleting the form removes the responses with it.
• Unlinking the spreadsheet stops new rows arriving in the sheet while the form keeps accepting answers into its own response store.
• Removing the link from a page hides the form from new visitors while anyone who kept the URL can still submit.
• Unpublishing the form takes it out of the published state entirely, and Google's own documentation notes that a form that is not published cannot accept responses at all.

Closing is reversible. Turning the switch back on reopens the form at the same URL with the same responses attached, which is the main reason it is preferred to deleting and rebuilding when a deadline gets extended.

Closing the form by hand

In the current Forms interface, the control sits with the publish state rather than in the old Responses toolbar. Open the form, click Published at the top right, and turn off Accepting responses. Google's help page for managing responses describes the same path, and adds the caution that responses cannot be accepted in an unpublished form.

The Responses tab still shows the collected answers after the switch is off, and the summary charts still update if a collaborator deletes a record. Nothing about the data changes.

Two details are worth knowing before flipping it.

First, the switch is per form, not per section or per question. A form collecting three unrelated things closes all three at once. If two of them run on different deadlines, that is an argument for two forms rather than for clever section logic.

Second, closing does not notify anyone. People who were sent the link and have not answered get no message, and the first they hear of it is the closed page. Where a deadline matters, a reminder before closing does more for the response rate than any amount of form design afterwards.

Editing the message people see

When responses are switched off, Forms shows a default line stating that the form is no longer accepting responses. That text is editable: under the notice about what responders will see when the form is closed, click Edit and write something useful in its place.

This is the cheapest improvement available on this whole subject. The default message tells the reader that they are too late and nothing else. A replacement can say when the next round opens, where to write instead, or who to contact if they had a genuine reason for being late. For anything involving applications, registrations or support requests, a closed form with a dead-end message generates email to whoever is easiest to find, which is usually not the person handling the form.

Closing at a set time, without being there

Until recently, Google Forms had no scheduled close. Anyone who needed one used a script or an add-on. That changed in January 2026, when Google announced that form owners and editors could set a close date and time or a maximum number of responses, after which the form stops accepting new ones by itself.

The rollout details from that announcement are worth keeping in mind if the setting is not visible:

The setting lives alongside the manual switch. From the published form, the same panel that holds Accepting responses offers Set close date or response limit, which is the point of entry for both the scheduled time and the response cap.

The response limit is the more interesting half for anyone running capacity-bound signups. A workshop with twenty places, a shuttle bus with forty seats, a clinic with a fixed number of appointment slots: all of these previously needed a person watching the response count, or a script, or a policy of accepting overflow and apologising later. A cap closes the form on the submission that fills it.

Two limitations to plan around. The cap counts submissions, not confirmed attendance, so a form that allows editing or repeat answers will not produce a clean headcount. And a form that closes on a cap closes for everyone at once, including the person who was halfway through typing, so the closed message matters even more here than on a date-based close.

The older ways, and whether they still earn their place

Anyone who has run forms for a few years has one of these set up already. They are not obsolete, but the reason for using them has narrowed.

A time-driven Apps Script trigger. A few lines calling setAcceptingResponses(false) on a schedule, with setCustomClosedFormMessage() to set the text at the same time. Both methods are documented in the Apps Script reference for the Form class. This remains the right tool when the closing condition is not a clock or a count: close when a column in the sheet reaches a value, close when a linked event is cancelled, close on a rolling basis for each of thirty forms generated from a template.

Third-party add-ons that limit responses. These predate the native cap and still offer conditions the built-in setting does not, such as closing on a cell value or reopening on a schedule. The trade-off is the one that applies to every add-on: another authorisation against the form data, and a dependency on a publisher outside the organisation.

Restricting who can respond. Since January 2026 all Google Forms have the same granular access controls as Docs and Sheets, which means responses can be limited to named people, groups or target audiences rather than to anyone with the link. That is access control rather than closing, and it is the correct fix for a different problem: not a deadline, but a form circulating beyond the group it was meant for.

Changing or removing the link. Effective against new arrivals, useless against anyone who bookmarked the URL, and it breaks every place the old link was published. Rarely the right answer.

Here is where each one belongs:

Reopening, and what happens to late submissions

Reopening is the same switch in reverse, and the response set survives it intact. Submissions made after reopening land in the same spreadsheet and the same response list as the earlier ones, with their own timestamps.

The timestamp is the thing to hold on to. When a deadline is extended, the honest way to tell the two groups apart is the submission time column in the linked sheet, not memory. Sorting by it before any selection or scoring begins avoids the argument about who was actually late.

One habit makes extensions cheaper: when the deadline moves, move the scheduled close with it rather than turning the schedule off and promising to close the form by hand later. A form that was closing itself on Friday and is now closing itself on the following Tuesday needs no reminder in anyone's calendar. A form whose schedule was disabled during an extension is the one that stays open for a month.

Submissions that arrive in the gap between the intended deadline and the actual close are a policy question rather than a technical one, but the technical setup decides how visible they are. A form closed by a scheduled date leaves no gap. A form closed by hand the next morning leaves one, and it is usually discovered by the person doing the review rather than the person who forgot to close it.

Closing the form does not close the work

A closed form is a tidy inbox with the lid shut. The submissions inside still need reading, assigning and answering, and that is the part that no close setting touches.

The pattern shows up clearly on anything where each response belongs to a person: applications, grant submissions, repair requests, event registrations that need confirming. The form closes on Friday, the spreadsheet has ninety rows, and by the following Wednesday nobody can say which of them have had a reply, because a spreadsheet has no idea what a reply is. Colour-coded columns get added, then get out of date, then get trusted anyway.

This is the gap that a form tool with response management is built to cover: each submission carries an owner and a state, the reply goes out from the same screen as the response, and closing the form becomes a genuine end point rather than the start of an untracked backlog. The situations where it pays off are the ones with a deadline on the front and a human answer on the back.

What to change first

Set a close date on the form that has a real deadline attached, and rewrite the closed message to say where late arrivals should go instead. Those two changes together remove both the overnight submissions and the email they generate. If the harder question is what happens to the responses after the form shuts, look at whether each one can carry an owner and a status, which is what Halict shows on its response screen.

Q1. Does closing a Google Form delete the responses already collected?

No. Closing stops new submissions and leaves everything already collected in place, both in the Responses tab and in any linked spreadsheet. Reopening the form later adds new responses to the same set. Deleting the form is the destructive operation, and that removes the responses with it.

Q2. Can a Google Form be set to close at a specific date and time?

Yes. Google added a close date and a response limit at the start of 2026, rolled out from January 12 for Rapid Release domains and January 29 for Scheduled Release domains, available to Workspace customers, Workspace Individual subscribers and personal accounts. The setting is off by default and is turned on after the form is published. If it does not appear, the form may still be waiting on the rollout, and an Apps Script trigger does the same job.

Q3. What do people see when they open a closed Google Form?

They see a page stating that the form is no longer accepting responses, not the questions. That text can be replaced with a custom message through the edit link beside the notice about what responders will see when the form is closed. Replacing it with the next opening date or an alternative contact saves a surprising amount of follow-up email.

Q4. Is there a way to close a form after a certain number of responses?

The response limit built into Forms does this natively, closing the form once the set number of submissions has been reached. Before that setting existed, the same result came from an Apps Script trigger or a third-party add-on, and those remain useful when the condition is more complicated than a count, such as closing based on a value in the linked spreadsheet.

Q5. Can one section of a Google Form be closed while the rest stays open?

No. Accepting responses is a property of the whole form, so it closes every question at once. Where two parts of an intake genuinely run on different deadlines, two separate forms are simpler than section logic, and they also keep the two sets of responses apart when the time comes to process them.