Building a questionnaire
The same builder writes a reusable template and the questions on a single request. So this page applies wherever you're editing questions.
Starting one
New questionnaire from the Questionnaires page builds a request for one person. Templates → Questionnaires → New template builds a reusable set.
Either way, Start from template copies an existing set in as a starting point. If you've already built questions, CoreHue asks Replace current questions? first.
Title and description
Title is what the client sees. "Wedding day details" tells them what it's for.
Use the description to say why you're asking and roughly how long it'll take. People finish forms they can see the end of.
Adding questions
Add item opens a menu of every question type, with Section heading and Instruction text at the bottom for the two that don't ask anything.
Each question has:
- Question, the label the client reads
- Helper text, an optional line underneath
- Placeholder, the grey text inside the box, on the free-text types
- Required, off by default
- Display logic, if you only want it shown sometimes
Helper text is underused. "The address we should arrive at, including any gate code" gets you a better answer than "Address".
The full list of types is in Question types.
Reordering
Drag a question by its handle, or use Move up and Move down in its menu. Delete removes it.
Order matters more than it looks. Display logic can only test a question that sits above the one it controls.
Structuring it
Section heading breaks the form into parts. Instruction text lets you explain something without asking a question.
A wedding questionnaire split into Getting ready, Ceremony, Reception and Group photos is much easier to finish than forty questions in a row.
Up to 100 items in total, counting headings and instruction text as well as questions. A form anywhere near that is a form nobody finishes.
Required or optional
Required means they can't submit without it. That's the trade: better answers against people giving up.
Require only what you'd have to chase anyway. Everything else optional.
Before you can save
Every questionnaire needs a title, a label on every item, and at least one item that actually asks something. Choice questions need at least two options. CoreHue names whichever of those is missing when you try to save.
Keeping it short
The most common mistake is asking everything you might want to know rather than what you need.
A few ways to cut it down:
Take out anything you could look up. If it's on the booking, don't ask.
Take out anything you'll discuss anyway. If you're having a call, that's a better place for open-ended questions.
Ask later. Split into a short form now and a detailed one nearer the date. Two short forms get finished. One long one doesn't.
Cut anything you've never actually used. Most questionnaires carry a question somebody added once, and nobody has read since.
Saving it as a template
Save as template, beside Start from template at the top of the composer, keeps what you've built for next time. Give it a title and an optional description. See Questionnaire templates.