An “Other” option can make a form more accurate and more welcoming. It gives people a way to answer when your list does not fit. But if you add it without a plan, you may end up with a pile of vague write-ins, inconsistent labels, and answers your team cannot route or analyze.
The goal is not to avoid free-text responses. It is to collect them where they add value, give respondents enough direction to answer, and preserve the original wording when you organize the data. This guide explains how to use the other option in survey questions and everyday business forms without turning useful detail into cleanup work.
What an “Other” option is for
“Other” is a response choice that lets someone provide an answer outside the options you listed. It is most useful when your options cover common cases but you cannot confidently predict every valid answer.
For example, a software company asking, “How did you hear about us?” might list a search engine, a colleague, an event, and social media. A respondent may have found the company through a podcast. If there is no suitable choice, they may select the closest option, skip the question, or leave the form. An “Other” choice with a short text field gives them a more accurate path.
That does not mean every question needs one. If the answer must come from a fixed set—such as a list of regions your service covers—“Other” may create an answer your team cannot act on. In that case, explain the available choices or provide a separate route for exceptions.
Decide whether the question needs “Other”
Use it when the answer space is genuinely open
Include “Other” when all of these are true: there are several reasonable answers, your listed choices are not exhaustive, and an unlisted answer could still be valid or useful. Common examples include referral sources, job roles, event types, reasons for contacting a team, and tools used in a workflow.
It is particularly helpful when respondents know their answer but are unlikely to recognize it in your wording. A vendor asking customers which department they work in might list Sales, Marketing, Operations, and Finance. A respondent in Customer Success should not have to mislabel their role just to proceed.
Do not use it to cover up an unclear question
Sometimes people choose “Other” because the question or its choices are hard to understand, not because their answer is unusual. If several write-ins say things like “not sure what you mean” or repeat a listed option in different words, revisit the question before adding more choices.
Check whether the question asks for one idea at a time. “Which product and service do you use?” combines two topics; an “Other” field will not fix the ambiguity. Splitting questions or clarifying the wording may improve the data. For more on separating related prompts, see our guide to when to use matrix questions—and when to avoid them.
Consider whether the answer can lead to an action
For operational forms, ask what your team will do with an unlisted response. A contact form might include “Other request” because a support team can review and route it. A required dropdown for a tightly controlled process may not need “Other” if every valid case already has a clear destination.
If the answer matters for lead routing, make sure the write-in reaches the person who can interpret it. A useful “Other” choice that disappears in a notification or export is not useful in practice. Our guide to designing a contact form for reliable lead routing covers how question choices affect handoffs.
Write the option and follow-up field clearly
Use a specific prompt, not a bare “Other”
Pair the option with a short instruction that tells people what to enter. For example:
- How did you hear about us? Other (please specify)
- Which department best describes your role? Another department (please name it)
- What type of request do you have? Something else (briefly describe)
Choose wording that fits the question. “Please specify” is compact, but “please name the department” is clearer when you need a department name. If examples will help, include one or two, but avoid steering respondents toward answers you prefer.
Show the text field when it is relevant
When someone selects “Other,” display a text field beside or immediately below that choice. Label the field with a direct instruction, such as “What source?” or “Name the department.” Keep the relationship visually clear so respondents know which option the field belongs to.
For a form builder that cannot reveal a field conditionally, you can show a separate optional text field and explain when to use it. For example: “If you selected Other, tell us which department.” This is less tidy, but it is better than an unexplained box that everyone assumes they must fill in.
Make sure the text field has a programmatic label as well as a visible one. Labels help people using assistive technology identify a field and its purpose. The W3C guidance on labeling form controls explains how to associate labels with fields. Do not rely on placeholder text alone: it can disappear as someone types and may not work as a durable label.
Keep the response burden proportionate
A short label or phrase is often enough. Do not require a paragraph when you only need a category name. If context is important, set expectations: “In one sentence, describe the request.” A useful field is not necessarily a long field.
Also decide whether the write-in should be required. If a respondent can select “Other” and continue without adding detail, your data may contain unhelpful entries. But forcing an explanation can frustrate someone who is unsure what to write or cannot safely share it. Make the field required only when the information is necessary to complete the task. This is the same trade-off covered in our practical guide to deciding when a form field should be optional.
Choose the right response format
Single choice or multiple choice?
Use a single-choice question when one answer best describes the person or situation. Use checkboxes when respondents can select several answers. In a multiple-choice question, “Other” should usually allow a write-in just like the other selections.
Be explicit about whether people may choose one answer or several. A respondent who uses three tools should not have to guess whether you want their main tool or every tool. If you need a primary answer, ask for it directly; if you need all applicable answers, say “Select all that apply.”
Use a separate “None of these” when it means something different
“None of these” and “Other” are not interchangeable. “None of these” means no listed answer applies, while “Other” means an unlisted answer does apply. If both situations are possible and matter to your decision, offer both. For example, a list of current services might include “I do not use any of these” as a separate option from “A different service (please name it).”
If you include “Prefer not to say” or “Not sure,” keep those separate too. They describe a respondent’s preference or knowledge, not an answer outside your categories. Demographic questions need particular care with these distinctions; see our advice on asking demographic questions without confusing or alienating respondents.
Preserve write-ins so they remain useful
Store the selection and text separately
Where your form tool allows it, record the selected option and the write-in in separate fields. For example, store “Other” in a response-category field and “Podcast interview” in a follow-up text field. This makes it easier to filter responses, identify write-ins, and review them without confusing the text with a predefined choice.
Keep the original text as submitted. If you later standardize “pod cast,” “Podcast,” and “podcast episode” into one reporting category, do that in a separate cleaned or coded field. Do not overwrite the source response. Keeping both versions lets you check how a coding decision was made and revisit it if your categories change.
Do not silently drop detail in exports and integrations
Before publishing, submit a test response using “Other.” Check the confirmation screen, email notification, spreadsheet export, CRM record, and any connected workflow where the answer should appear. A form can capture the text correctly while a downstream mapping sends only the selected value.
Test at least one realistic write-in and confirm that it is readable where a staff member will act on it. Check that line breaks, punctuation, and longer answers do not get cut off. If the response triggers an automation, make sure the rule handles “Other” deliberately rather than assigning it to an unrelated default category.
Review and code responses without flattening them
When enough write-ins accumulate to reveal a pattern, you can decide whether to add a new listed answer. Do not promote a choice just because one response is unusual. Ask whether it represents a real, recurring category and whether respondents can identify it consistently.
- Review the raw responses. Read the full write-ins before grouping them. Keep their original wording available.
- Group only equivalent answers. “Podcast,” “podcast episode,” and a named podcast may fit one reporting category if your purpose is to measure the channel. They may need separate labels if you are planning specific partnerships.
- Write down the coding rule. State what belongs in each new category and how to handle unclear answers. A short note is enough for a small project.
- Keep ambiguous answers visible. Use a category such as “Unclear write-in” or flag it for review rather than guessing.
- Update the form if the pattern is stable. Add a new option when it will help future respondents and make reporting more consistent. Keep “Other” if new valid answers can still arise.
For example, a nonprofit might ask how a volunteer heard about an opportunity. Write-ins include “my neighbor,” “a coworker,” and “someone at my church.” If the team only needs broad acquisition channels, it may code these as “Personal referral.” If it is deciding which community organizations to approach, the distinctions may be valuable and should not be collapsed.
There is no universal response count at which a write-in deserves its own option. The right decision depends on what you need to learn, the cost of adding another choice, and whether people can reliably tell the choices apart. Review the question again after you have enough responses to assess its purpose—not simply to make the list longer.
Common “Other” mistakes to avoid
- Adding it to every question: It can make a concise list harder to scan and may invite answers that are outside the process.
- Making the write-in field mandatory by default: Require it only when the detail is needed, and explain what belongs there.
- Using it as a substitute for “Not applicable” or “I don’t know”: Those answers mean something different and deserve their own choices when relevant.
- Making the field too vague: “Please specify” may not tell a respondent whether you need a name, reason, or explanation.
- Ignoring the answers after collection: If no one reviews the write-ins, the option may add effort without improving a decision.
- Replacing original text with a category: Preserve the submitted answer and store any standardized interpretation separately.
A quick pre-launch checklist
- Could a valid respondent answer fall outside the choices?
- Will the team use or review an unlisted answer?
- Does the option say what kind of write-in is wanted?
- Is the text field clearly labeled and easy to find?
- Is the field required only if the answer is necessary?
- Can the response be seen in exports, notifications, and connected systems?
- Do you have a plan to review, code, and preserve the original text?
“Other” works best as a deliberate exception path, not a catch-all. Give respondents a clear way to explain an unlisted answer, keep the write-in attached to the right question, and decide in advance how your team will use it. That small amount of planning makes the form more flexible while keeping the resulting data understandable.
Frequently asked questions
Should “Other” be the last option?
Usually, yes. Placing it after the named choices makes the available categories easier to scan first. The more important point is to use a consistent order and keep the write-in field visually connected to the option.
Should the “Other” text field be required?
Only when a description is necessary to process the response. If the form can still be completed without the detail, make the field optional and say what information would help. Avoid requiring text just to prevent blank entries if those entries do not affect your next step.
How long should an “Other” answer be?
Set the limit based on what you need. A category name may need only a few words; a request description may need a sentence. State the expected length in the label or helper text, and do not set an unnecessarily tight character limit.
When should I turn a write-in into a new answer choice?
Consider adding it when write-ins show a recurring, meaningful category that respondents can distinguish from the existing choices. Keep the original responses and document how you grouped them. A rare but important answer may still deserve a listed choice if it affects safety, eligibility, or routing.
Is “Other” appropriate for sensitive questions?
It can be, but consider whether asking for an explanation could pressure someone to disclose more than they want. Offer a clear “Prefer not to say” choice when appropriate, explain why information is requested, and make any write-in optional unless it is essential. Collect only the detail your process needs.