Where form codes work hardest
On tables and receipts for feedback ('how was everything?'), on event signage for registration, on classroom handouts for quizzes, on packaging for warranty sign-ups. In every case the pattern that works is: one question where the person is, and a code that gets them answering in under ten seconds.
Keep the form itself brutally short on mobile — a code that opens a 20-field form teaches people not to scan your codes.
Pre-filling answers
Forms support pre-filled links (Send → link → 'Get pre-filled link'). Combined with the bulk generator, you can produce a different code per table, room or product, each pre-filling a hidden field with its location — so responses arrive already sorted, from a single form.
Counting and analysing scans
The form's response count is your scan count — that's usually the metric that matters. If you also want scan-without-submit numbers, route through a short URL on your own site with analytics, and point the code there.
Mistakes to avoid
- Test the link signed out — the organiser's signed-in browser hides permission problems.
- Long form URLs make dense codes; always use the shortened share link.
- Don't collect personal data on a public code without a privacy note on the form.
Common questions
Can respondents stay anonymous?
That depends on your form settings (don't collect email addresses), not on the code.
Do I need a Google Workspace account?
No — any free Google account can create forms, and respondents don't need any account if the form is unrestricted.
Can I change the form after printing the code?
Yes — the code points at the form, not its questions. Edit questions freely; only deleting the form breaks it.
Can one form have different codes per location?
Yes — use pre-filled links with a hidden field and the bulk generator.