Get the right link — this is where it goes wrong
Google Forms has two addresses and they are easy to confuse. Copying the wrong one is the single most damaging mistake on this page.
- The editing link ends in
/edit. It is what sits in your browser bar while you build the form. Anyone who opens it can rewrite your questions, read every response and delete the lot. - The response link ends in
/viewform, or looks likeforms.gle/…. This is the one to encode.
Get it from the Send button, then the chain-link tab. Do not copy from the address bar. Printing an edit link onto fifty handouts is a genuinely bad afternoon.
Shorten the URL before encoding
In that same Send dialog there is a Shorten URL checkbox. Tick it. A full Google Forms link runs to about 90 characters; the shortened forms.gle version is around 25.
That difference is visible in the code — roughly version 4 instead of version 8, which means chunkier modules and reliable scanning from a handout or a projected slide. This is Google's own shortener for your own form, not a third-party redirect, so it does not introduce a dependency you did not already have.
Pre-filled links give you context for free
This is the feature most people miss. In the form editor, open the three-dot menu and chooseGet pre-filled link. Fill in the fields you want set in advance, and Google generates a link carrying those answers.
Print a different code per location and each one arrives tagged:
- A feedback form where "Table number" is already filled in.
- An event sign-up where "Session" is set per room.
- A maintenance report where "Equipment ID" comes from the code on the machine.
You get clean data without asking anyone to type anything — and without a tracking service in the middle.
Check who has to sign in
Two settings decide whether scanning leads to a login prompt:
- Collect email addresses — forces a Google sign-in.
- Restrict to users in your organisation — blocks anyone outside your domain entirely.
Both are reasonable for internal use and fatal for a public code. Test by scanning on a phone that is signed out of Google, before anything goes to print.
Closing and reopening
Turning off "Accepting responses" does not break the code — visitors get a polite message saying the form is closed. Turn it back on and every printed code works again.
That makes one printed code viable for something recurring: a weekly class register, a monthly feedback round, an annual sign-up. The code is permanent; the form's availability is a switch.
Where to put it
On a slide at the end of a talk, while people are still in the room. On a table card, not just at the door. On a handout people take away — a code on paper outlives a link on a screen. Add two words saying what it is: "Scan to give feedback" converts far better than a bare square.