# Building a questionnaire > Build a client questionnaire in CoreHue: add questions, split it into sections, choose what's required and keep it short enough that clients actually finish it. Source: https://help.corehue.co/docs/questionnaires/building-a-questionnaire/ The same builder writes reusable templates and the questions on a single request, so everything here applies wherever you're editing questions. A good questionnaire is short, clearly grouped and asks only what you'll actually use. ## Start a questionnaire - **For one client:** go to **Documents → Questionnaires** and choose **New questionnaire**. - **As a reusable template:** go to **Templates → Questionnaires** and choose **New template**. Either way, **Start from template** copies an existing set of questions in as a starting point. If you've already added questions, CoreHue asks **Replace current questions?** first. Your account comes with a few templates matched to your specialism, and **Add from CoreHue** on the templates page has a library of more. ## Write a title and description The **title** is what your client sees at the top of the form. "Wedding day details" tells them straight away what it's for. Use the **description** to say why you're asking and roughly how long it takes. "Ten minutes, and it means I won't have to chase you for addresses later" gets more forms finished than no explanation at all. ## Add questions 1. Choose **Add item** and pick a question type. 2. Type the **Question**, the label your client reads. 3. Add **Helper text** if a line of explanation would help, and a **Placeholder** on text questions if you like. 4. Turn **Required** on if they can't submit without answering. 5. Add **Display logic** if the question should only appear after a certain answer. Helper text is the most underused setting here. "The address we should arrive at, including any gate code" gets a far better answer than "Address". Every question type is described in [Question types](/docs/questionnaires/question-types), and display logic in [Showing questions based on answers](/docs/questionnaires/conditional-logic). ## Group questions into sections From **Add item**, choose **Section heading** to break the form into parts, and **Instruction text** to 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 one long list. ## Reorder and remove Drag a question by its handle, or use **Move up** and **Move down** in its menu. **Delete** removes it. Order matters more than you'd think. Display logic can only depend on a question that sits above it, so put the deciding question first. ## Required or optional? Required means your client can't submit without answering. It's a trade: better answers against more people giving up. A good rule is to require only what you'd otherwise have to chase. Leave 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 tells you what's missing when you try to save. A questionnaire can hold up to 100 items, counting headings and instruction text. ## Keep it short It's tempting to ask everything you might want to know, rather than what you need. - **Drop anything you already have.** If it's on the booking, don't ask. - **Drop anything you'll discuss on a call.** Open-ended planning is better in conversation. - **Split it.** A short form after booking and a detailed one closer to the date both get finished. One giant form often doesn't. - **Cut questions you never read.** If you never look at the answer, the question can go. For a full list of what to ask, see [Writing questionnaires clients actually answer](/docs/guides/questionnaires-that-get-answered). ## Save it as a template On a request you're building, choose **Save as template** at the top of the composer, give it a title and an optional description, and it's ready for next time. ## What your client sees Your client sees your title and description, then your questions in order, grouped under your section headings. Required questions are marked, and questions behind display logic appear only when their answers make them relevant. ## Frequently asked questions ### Can I edit a template without affecting questionnaires already sent? Yes. Each questionnaire request keeps its own copy of the questions, so template changes only apply to requests you create afterwards. ### Can I change the questions after I've sent it? Yes. You can change the questions on a sent questionnaire until your client submits or the close date passes. Open the request and choose **Edit**. If they're partway through, their answers to the questions you didn't change are kept. See [Sending a questionnaire](/docs/questionnaires/sending-a-questionnaire). ### Is there a limit on how many questions I can add? Yes. A CoreHue questionnaire can hold up to 100 items, including section headings and instruction text. A form anywhere near that is too long to finish, so aim for far fewer.