Google Forms registration link: where they quit

A registration form often asks for more than one person's details: each attendee's name, a date of birth, a medical note, an emergency contact and sometimes a parent or guardian. The visitor starts on the first page with what they know. When they reach a page asking for a doctor's name or a second adult's phone number, they have to stop, go and find it, and come back. Some never come back. The link stays in their inbox, and nothing on your side records that they left.

• Count the pages before the confirmation, and note which page asks for a second person's details.
• Open the link from an email on a phone, not from your laptop, and read the first screen as a stranger.
• Check that the link ends in /viewform, not /edit, and that the first screen is the form itself.
• Find the page after Submit. If it names no next step, a visitor can finish the form and still not be registered.
• Compare the Responses count with the seats you hold and the number of invitations you sent.

The wrong version puts every attendee's details on one long run of pages, with each field marked required because the class needs it eventually. A visitor registering two children meets the same block twice, and the second time they may not have the answers. The right version asks only what holds a seat: the attendee's name, an email and the session they want. Everything the class needs later, such as medical notes and pickup contacts, goes into a follow-up form that the visitor fills in once a seat is held.

Check the drop by walking the form as a stranger. The report names the step where each simulated visitor stopped, and the screenshot shows what that page asked. A stop on page three, with a screenshot of the medical block, tells you where to cut. Counting the pages in your own editor does not show this, because you already know the answers you would type.

Copy the link from the address bar while you edit, and it ends in /edit. A stranger who opens that address does not reach the form. They land on an access request, and they leave, because it looks private or broken. The link to send ends in /viewform. Get it from the Send button in the form itself, so the address you share is the one visitors can fill in.

Open the link in a private window, signed out of Google, on a phone, and check whether the first screen is the form. If it lands on anything other than the questions, the problem is the link, and no change to the questions will fix it. Walk the test through to the page after Submit as well, so you see the confirmation a stranger gets.

The confirmation can read as finished when the registration is not. A page that says thanks, we will be in touch, with no next step, leaves the visitor thinking they are signed up. If the seat is held only after a payment or a follow-up form that the confirmation never mentions, the visitor walks away with nothing, and your count shows a row that never became a place. The right version names the next step on the confirmation page and links to it.

A closed form has the same effect. When seats run out, stop the form from taking responses, then check the link from a private window. A visitor who arrives at a bare notice has no next step. Keep a waitlist or the next session on the page that links here, and take the link out of the emails once the form is closed.

Registration forms grow. A new session, a waiver or one more question for each attendee adds a page the last run never walked. After every change, run the same visitor through the link on a phone, all the way to the page after Submit, and check the Responses tab for a new row. Run it again whenever the link goes into a new email list.