Forms can route respondents to different sections depending on their answers. A repeated section may therefore come from the form's branching setup rather than your browser. Note the answer and section that trigger the loop, then contact the owner if it prevents completion. Repeatedly refreshing will not repair their routing rules.
Use a Checkboxes question, open its three-dot menu, and choose Response validation. Select the rule for an exact number of choices and enter 2. Add a short error message explaining the requirement. Preview the form and try one, two and three selections. Mark the question Required if everyone must answer rather than leave it blank.
Open the short-answer or paragraph question, choose Response validation from its menu, and set a maximum character count under Length. Tell respondents the limit before they type, then add a useful error message. This setting counts characters, not words. Test a short answer and an over-limit answer in Preview before publishing the revised form.
Place the follow-up questions in their own section. On a multiple-choice or dropdown question, choose Go to section based on answer and assign each option its destination. Also check where every destination section continues afterward. Preview every possible branch, including the path that should skip the follow-up, so nobody reaches an irrelevant required question.
Use a multiple-choice or dropdown routing question and enable Go to section based on answer. For the option that should end the form, choose Submit form as its destination. Keep any questions everyone must answer before that routing point. Test both the shorter and longer paths; an early ending should still feel intentional and explain what happens next.
Use a multiple-choice or checkboxes question, select an answer option, and choose its Add image control. Upload or select an image, then repeat for the other relevant options. Keep a clear text label with each picture so the choices remain understandable without relying on the image alone. Preview on a phone to check cropping and readability.
Open the individual multiple-choice, checkbox or dropdown question. In its three-dot menu, select Shuffle option order. This is separate from the form-level setting that shuffles questions. Avoid using it for choices that need a meaningful sequence, such as low-to-high ratings, and remove references like the option above. Preview the question before sharing the form.
In the form editor, open the top-right More menu and choose Pre-fill form. Enter the event name in its answer field, select Get link, and copy that generated link. Open it as a respondent to check the result. Treat prefilled information as a convenience, not a hidden or trusted identifier, and avoid putting private details in a shared link.
Open Settings, expand Presentation, and edit the Confirmation message. Write what the respondent should expect next, such as a review timeframe or where to find event details, then save it. Submit a test response to see the actual message. Avoid promising an email, booking or payment confirmation unless your process really performs that separate action.
In the published form, open Published and find Set close date or response limit under Accepting responses. Choose the date-and-time option, set the deadline, and save. Customize the message people see after closure so they know the next step. Reopen the publishing controls to verify the setting before sharing the registration link with others.
Google notes that submissions arriving at the same time can be accepted even when the form reaches its limit. A response cap therefore should not be treated as a guaranteed reservation counter for the last seat. Review the collected submissions, apply a clear confirmation process, and tell respondents when a submission still needs approval before a place is secured.
Source checks for these answers: September 21, 2026 – September 23, 2026. Product instructions and local requirements can vary.