A QR code for Google Forms is the fastest way to move a survey from a link someone will never click to a form already open on their phone. The mechanics take a minute: build the form, copy the responder link, generate the code. The part that fails is sharing. A form that looks public in the editor can still ask respondents to sign in, request permission, or refuse responses, and the printed code cannot explain any of that. This guide fixes the permissions before the ink dries.
Part of the free QR code generator guide.
Build the form, then copy the responder link
Create the form and add only the questions you will act on. A form with 15 fields gets abandoned; four questions and an optional comment get finished. Decide whether to collect email addresses, limit responses per person or allow edits after submitting; each choice affects who can open the form.
When the form is ready, click Send and choose the link tab. If the dialog offers Shorten URL, enable it; a forms.gle/... address produces a sparser pattern than the full docs.google.com/forms/d/e/.../viewform URL. The short version scans more easily when printed small. Do not copy the browser URL while editing: the editor link ends in /edit and opens the design view, not the respondent form.
- Responder link: ends in /viewform or uses forms.gle. Encode this one.
- Editor link: ends in /edit. It asks for a login and must never be printed.
- Embed code: HTML for an iframe, not a URL.
- Prefilled link: a long URL with answers filled. Useful, but dense.
Set sharing so anyone with the link can respond
Open the responder link in a private window while signed out of every Google account. This is the only test that matches what a customer will experience. The form should load and accept an answer without a login prompt. If it asks you to sign in or says you need permission, it is not open to everyone with the link, and a QR code will not fix that.
Forms links are normally open to anyone with the URL, but there are three common exceptions. A Workspace administrator can restrict sharing so only domain accounts respond. A file upload question requires sign-in because the file needs an owner. Limit to 1 response also requires sign-in so Google can identify each respondent. Turn those off if anonymous answers matter more.
Confirm the form is still accepting responses. A closed form shows a message saying it is no longer accepting responses, which looks like a broken code from the customer’s side. Reopen the existing form for a new round rather than creating a new one, so the printed code keeps working. In Workspace, ask the admin to confirm link sharing is allowed before printing cards.
Turn the link into a QR code
Paste the responder link into the generator, preview the pattern, and export at the size your placement needs. Google Forms URLs are long, especially the full viewform address, so the pattern is denser than a short menu link. That is the main reason to enable the short link and print larger. A 40-character forms.gle link at 5 cm is comfortable; a 150-character prefilled link at 3 cm is not.
Use black on white, keep the quiet zone clear and choose matte stock. Do not put the code on a glossy poster behind glass or tint it to match a brand palette. Print at the size the room demands: 15–20 cm for an exit poster read from two metres, 5–6 cm for a desk card. The distance tables are in the QR code size and print guide.
Placement and print sizes
Put the code where the respondent is already holding a phone and has a reason to answer. An exit poster catches people before they leave; a desk card catches a student before class; a counter card catches a patient at check-in. A code in a newsletter or slide competes with every other link, so print it on the handout too if the room is physical.
| Use case | Example form | Print size | Placement |
|---|---|---|---|
| Event feedback | Four questions and one comment | 15–20 cm | Exit poster at 1.5–2 m, with a handout |
| Classroom exit ticket | Three quick questions | 5 cm | Desk card or printed worksheet corner |
| Clinic intake | Contact details and history | 8 cm | Reception counter at 80 cm |
| Maintenance request | Location, issue, photo upload | 4–5 cm | Laminated label on the equipment |
| Restaurant feedback | Rating and one comment | 3–4 cm | Bill folder at 30–40 cm |
Label the code with the action and time cost: “30-second feedback” or “Report a fault.” A bare square is easy to ignore. If the form asks for personal data, say so on the card and link to a privacy notice; the code is a shortcut, not a consent mechanism.
Prefilled links and long URLs
Google Forms can prefill answers through the three-dot menu and Get pre-filled link. Fill the fields, click Get link, and copy the result. This is useful for a session, location or cohort without asking the respondent to choose. The values are visible in the URL and can usually be changed, so do not treat them as secure data.
Prefilled URLs are much longer than the plain responder link. A 200-character URL creates a dense pattern that needs a larger print and a better camera. For a table tent, use the plain link and ask the question inside the form. For attribution, a short forms.gle link to a separate form per channel scans more easily. Fewer characters is the cheapest scanability upgrade.
Test like a respondent, not an editor
Scan the printed code with a phone signed out of Google, over mobile data. Confirm four things: the form loads, the questions are readable without zooming, submit works, and the confirmation appears. Then check the Responses tab for the test answer. Delete it if it would distort your data, or use a duplicate form for testing.
Repeat at the real distance and lighting. A poster code that works at arm’s length may fail at two metres; a laminated card may glare under a fluorescent tube. Test an older Android as well as an iPhone, because a long forms.gle URL is the kind of dense pattern budget cameras struggle with. If it will not scan, the not-scanning fixes start with size and contrast.
Re-test after every edit. Changing a question, closing the form or toggling a setting changes what the respondent sees while the printed code stays the same. Write the test date on the back of one card.
Two worked setups
Example 1 — conference session feedback, Hyderabad. The organiser builds a five-question form with a session code, two rating scales and a comment box, then leaves email collection off so respondents can answer anonymously. The responder link is shortened to forms.gle, encoded at 2048px and printed at 18 cm on a poster beside the exit, with a 6 cm version on the handout. The poster is tested from two metres in the venue’s afternoon light, and the first test submission is checked in the Responses tab. The form stays open for a week, so late scans still work.
Example 2 — dental clinic intake, Kochi. A two-chair clinic creates a form for name, contact number, reason for visit and preferred appointment time. Because it does not need file uploads or one-response limits, the link opens without a Google sign-in. The code is printed at 8 cm on a matte counter card at reception, 80 cm from a seated patient, with the line “Complete intake before your appointment.” The receptionist tests it signed out, submits one dummy response, deletes it, and repeats the test whenever the questions change.
What you can and cannot track
Google Forms counts responses, not scans. A static QR code has no analytics, so you cannot tell how many people pointed a camera and walked away. You can see completed responses and arrival times. To compare channels, use a separate form or prefilled field and compare response counts. Do not put a tracking redirect in front of the form unless you accept that service as a dependency for every printed code.
Judge the response count against the room, not a made-up benchmark. If 100 people attended and 12 responded, the problem may be placement, wording or form length. Move the poster closer to the exit, shorten the form, or have the host mention it once. A QR code removes friction; it cannot create motivation.