Close a Google Form Automatically at a Deadline

To close a Google Form automatically on a deadline, set a closing date and time in the form’s response controls if that option is available. If it is not, use a form-closing add-on, then test the respondent link before you share it.

A closing date is the right setting for a deadline

To schedule a Google Form to stop accepting responses at a particular time, use a closing date rather than a response limit. A closing date is meant for a deadline, such as the end of an application window. A response limit closes the form after a chosen number of submissions, which could happen earlier or later than expected.

Start by deciding what “closed” must mean for your work. Usually, it means people can still open the form link but cannot submit a new response. Write down the intended date, time and time zone before changing any settings. If respondents work in different places, tell them which time zone the deadline uses rather than assuming they will interpret it the same way.

Google Forms also lets an owner stop accepting responses manually. That is useful if you are watching the form yourself, but it does not meet a deadline you might miss. For a scheduled close, look for a closing-date control in Google Forms. If your form does not offer one, a form-closing add-on is the no-code alternative. Neither option requires an AI tool.

The built-in closing date is the simplest option

A built-in closing date is enough when your Google Form offers a way to set when it stops accepting responses. Open the form as an editor and find its response-acceptance controls. Depending on the interface shown to your account, these may appear with the published form controls or in the Responses area. Look for an option to set a closing date or time, choose the deadline, and save it.

Check the form again after saving. The important detail is the stored deadline, not merely the fact that the form is accepting responses at the moment. Confirm the date, time and time zone shown by the control. Also check the message respondents will see after the form closes, if your interface lets you change it. A short message can say that submissions have ended and point people to an appropriate contact route without inviting them to send answers somewhere less secure.

Do not confuse turning off “Accepting responses” with scheduling it to turn off later. Turning it off manually closes the form immediately. If you cannot find a scheduling control, do not assume that a deadline written in the form description will enforce itself. Use an add-on or plan to close the form manually.

A form-closing add-on covers forms without a scheduler

A form-closing add-on can set an end date for a Google Form when the built-in scheduling option is unavailable. Install one through the form’s add-on controls, then use its date-and-time rule rather than a submission-count rule. Read the permissions request before granting access, especially if the form collects personal or confidential information. Your organisation may also restrict which add-ons staff can use.

Set the deadline in the add-on, save or enable its rule, and reopen its settings to confirm the rule remains active. Check which time zone it uses and whether it describes the deadline as an exact time or a time after which it checks the form. Do not promise respondents an exact cutoff unless the tool’s own documentation supports that expectation. An add-on may also depend on its author continuing to maintain it.

For a sensitive or strictly enforced deadline, ask the person responsible for your organisation’s Google Workspace settings whether the add-on is approved. If an add-on is not suitable, the honest fallback is a named person closing the form manually at the agreed time, with a reminder and a backup owner. A written deadline alone does not stop submissions.

A response limit does not enforce a closing time

A response limit answers “how many submissions?” while a closing date answers “until when?” Use the limit for a capacity-bound form, such as one with a fixed number of places. Use the date for an application or feedback deadline. If both conditions matter and your available controls support both, check how the form behaves when either condition is reached; do not assume one setting overrides the other.

A response limit counts submissions, not necessarily individual people. Someone may submit more than once unless you have separately set up restrictions that fit your audience. Conversely, requiring people to sign in can prevent some intended respondents from taking part. Review those access settings before treating a count as a reliable measure of participation.

Closing the form also has a different effect from stopping later work on responses you already collected. A PDF made from each Google Form response or a calendar event created from a form response depends on a submission arriving. Closing the form prevents new submissions; it does not undo files or events already created. Keep the deadline rule separate from any automation that processes accepted answers.

A respondent-side test catches the important mistakes

Test the form through its respondent link before sharing that link widely. First, open the link in a private browser window or another account that has the same access a real respondent will have. Confirm the form accepts a submission before the deadline and that its sign-in and organisation restrictions are appropriate. An editor’s view cannot tell you what an outside respondent will experience.

To test the closing rule without waiting for the real deadline, make a copy of the form and give the copy a near-term test deadline. Submit to the copy before it closes, then return after the test deadline and try to submit again. If the rule is managed by an add-on, check whether its settings and authorisation must be configured separately for the copy. Do not assume copying a form copies an active scheduled rule.

Finally, return to the real form and confirm its actual deadline, acceptance status and respondent link. Avoid sending a test submission to a live form connected to other workflows: it could create a real file, event or notification. A successful test of a copy shows how the setup behaves, but checking the real form’s saved settings is still necessary.

The shared form still needs an owner at the deadline

An automatic closing rule reduces routine work, but someone should verify that the form has closed. Before sharing, give respondents the deadline with its time zone and send the respondent link, not the editing link. Keep a note of who owns the form and where its closing rule is set, so another team member can check it if the owner is away.

Shortly after the deadline, open the respondent link as a respondent and confirm that a new submission cannot be sent. If the form is still accepting responses, turn off acceptance manually, record when you noticed the problem, and decide how to handle any submissions received after the intended cutoff. Avoid silently deleting responses when the deadline affects eligibility or a business decision.

If your workflow lets people revise answers, check that separately from new submissions. The guide to editing Google Form answers without submitting twice covers that choice. Closing a form should not be treated as proof that every possible way of changing an earlier answer is blocked. State your policy for late changes clearly, and test the behaviour your respondents will actually encounter.

Sources consulted

• Google Forms Help (support.google.com)

Start a free course