Run Team Surveys With Collections, a QR Code, and a Responses Dashboard

An onboarding check, a safety quiz, a tooling survey — build them as HTML, group them behind one link, print the QR, and watch the answers pool in one dashboard.

The survey that never quite happens

Every team has a stack of questions it never gets around to asking. Did the new hire actually understand the onboarding? Does everyone remember the safety procedure? Which tool is quietly costing the team an hour a day? Is the training track landing, or is everyone nodding along?

These aren't hard questions. What's hard is the apparatus. Standing up a survey tool, wrangling seats, exporting a CSV that lands in someone's downloads folder — by the time the form is ready, the moment has passed. So the questions go unasked, and the team runs on hunches.

There's a lighter way, and it's made of parts you already have: an HTML page, a collection, a QR code, and a dashboard.

A survey is just HTML

Start with the thing itself. A survey or a quiz is a form with some questions and a submit button — which is to say, it's HTML. And these days you don't write that HTML by hand. You describe it to an agent and it builds it: "an onboarding check with five multiple-choice questions and a rating scale," "a safety quiz that scores itself," "a two-minute tooling survey."

The surveys page hands you the one prompt that makes this land: paste it before you build, and the agent wires the page so every answer is captured — named fields become the questions, option values become the answers, and the whole thing records itself when someone hits submit. A training quiz, an onboarding check, a risk assessment — same recipe, different questions.

That little questionnaire is the whole idea in miniature: a few questions, a submit, and answers that go somewhere. Build one, publish it, and you have a live survey at its own link. Build three and you have the beginning of a program.

Group the program into a collection

Here's where most survey setups sprawl. A real onboarding isn't one survey — it's a day-one check, a first-week pulse, a tooling questionnaire, a values read. That's four links. A compliance sweep is a quiz per policy. A training track is a check after every module. Send those one by one and you're back to pasting a wall of URLs into Slack and hoping people work through them in order.

A collection fixes that. It groups your published pages behind one public link at /c/your-name, in the order you choose, with a blurb on each. The whole program becomes a single front door — "here's onboarding," not "here are ten links, good luck." (The general how-to lives here.)

One link for the set. Now it just needs a way onto people's phones.

Share the QR — on a slide, a poster, a badge

Every page and every collection on host-html has a QR code. That matters more than it sounds, because a link is something you send and a QR is something you place.

Drop the collection's QR on the last slide of the onboarding deck and the room scans it before they leave. Print it on a poster in the break room for the safety refresh. Paste it into the kickoff Slack message. Put it on a conference badge for a session survey. Nobody types a URL, nobody hunts for the right message — they point a camera at the thing in front of them and they're taking the surveys. It works the same for a single page or the whole collection, so you can share one quiz or the entire program with the same gesture.

Async by design: people scan when they have a minute, not when you're standing over them. And they can answer anonymously or type their name — your call, their choice.

Watch the answers pool in the dashboard

This is the part that turns a stack of forms into something you can act on. Every response lands in the page's dashboard, visible only to you.

No separate survey tool, no spreadsheet to babysit. Each question gets its own card, typed automatically: rating scales become a mean with a distribution, multiple choice becomes ranked bars, free-text becomes a readable list of what people actually wrote — with their name attached if they gave one. You see how many answered, the scores on a self-grading quiz, and a CSV export for when you want the raw numbers in a sheet.

Scattered feedback — twenty phones, twenty minutes apart — becomes a single picture. That's the whole promise: you asked, and now you can see the answer instead of guessing at it. (More on why we think every page deserves this in why we added analytics.)

Why a survey program wants Pro

Here's the honest edge, because it's the one that matters for surveys specifically. A free account keeps a page live for a few days, and response collection is a paid feature — a free page can carry the form, but the answers land nowhere. That's the edge to know before you print the QR code.

A survey is the one kind of page you don't want expiring out from under you mid-collection — the whole point is that it keeps gathering answers while people trickle in. So this is exactly where Pro earns its keep:

Collections themselves live on every paid plan, from Pro ($12/mo) up — and on a plan with team seats a collection can belong to the whole team, so several people build and add surveys to the same program. Either way, the surveys underneath it are the pages that actually persist.

Upgrade to Pro — $12/mo → and your survey program stops being a thing that expires. Already signed in? Go straight to /account?upgrade=pro.

Start with one question worth asking

You don't need the whole program on day one. Pick the one question your team keeps guessing at, build the survey with an agent, publish it, and grab the QR. When it's collecting, add a second, group them into a collection, and share the one link.

Build your first survey → · then group them into a collection, or read why we built collections. Collecting sign-ups rather than answers? See how to make an event registration page.