Free Survey Bias Checker
Paste your survey questions, one per line, and see which ones are leading, loaded, double-barrelled, absolute, or hard to read. Each flag explains why the wording skews answers and how to fix it, and you can download the whole check as Word or PDF. It is free, needs no sign-up, and every question is checked locally in your browser. If you want a neutral rewrite of a flagged question, you can ask for one; that is the only step that sends anything to our server, and only for the question you pick.
Your questions
0 questionsNothing you paste here leaves this page. The check itself makes no AI call: it matches known biased-wording patterns locally in your browser. Asking for a rewrite later is a separate, optional step.
SURVEY BIAS CHECK REPORT
Paste your survey questions on the left, one question per line, and the check runs as you type.
Nothing you paste leaves this page: every question is checked locally in your browser.
Generated by BlockSurvey
How the survey bias checker works
Paste your questions
Drop your survey questions into the box, one question per line. There is no limit, no sign-up, and the check starts as you type.
Read the flags
Each question is checked against nine biased-wording rules. Every flag names the pattern, its severity, why it skews answers, and how to fix it.
Download the report
Export the full check as a PDF or an editable Word file. The check runs locally in your browser, and the downloaded report is assembled on your device.
Free, private, and built for better research
Most question-review tools either paywall the result or upload your draft survey to someone else's server before you have decided to run it. This one does neither. The check is rule-based: nine documented patterns, matched against your text in the browser, with no model and no network call involved. Rewriting a flagged question is the one optional step that uses a server, and only ever for the single question you choose.
The check is in-browser
The matching is deterministic and there is no AI call behind it. Your questions are checked locally in your browser. Only the optional rewrite sends a question to our server, one at a time, and nothing is stored.
No account required
No sign-up, no email wall, and no record of the survey you are drafting.
Detection, honestly described
It flags biased wording and tells you how to fix each pattern. It does not rewrite your questions, because that needs a language model and this tool does not use one.
What it checks
Nine wording patterns, each with a severity and a fix:
- Double-barrelled (high). Two topics joined by "and" or "or" with only one answer allowed. Split it into two questions.
- Leading (high). Phrasing that signals the expected answer, such as "don't you agree" or "everyone knows". Ask neutrally and offer both directions.
- Loaded or charged wording (high). Emotive words such as "amazing", "terrible", or "useless". Replace them with neutral description.
- Assumptive or presupposing (high). Wording that assumes the experience happened or was enjoyed. Ask whether first, then how much, and add "not applicable".
- Absolute wording (medium). "Always", "never", "every", "nobody". Use a frequency scale instead of forcing a false choice.
- Double negative (medium). Two negations in one sentence. Rephrase positively so there is one possible reading.
- Jargon and reading load (medium). Over 25 words, or several very long words. Shorten it and use plain language.
- Possibly unbalanced scale (medium). Only positive anchors, such as "how satisfied" or "how good". Check the scale has a real negative end and a neutral midpoint.
- Vague quantifier (low). "Often", "regularly", "several". Use concrete ranges such as "1-2 times per week".
Accuracy note: this is a fast, structured starting point, not an authoritative verdict. The checker matches known wording patterns, so it will miss bias that depends on context, such as a skewed answer scale, a loaded topic, or an assumption carried by the questions around it. It will also flag wording that is perfectly fine in context. Human judgement decides what to change.
Worked examples: biased vs neutral
The tool flags the pattern; you write the replacement. These examples, written by our research team, show what each fix looks like in practice.
| Biased question | The problem | A neutral version |
|---|---|---|
| "Don't you agree that our friendly support team did a great job?" | Leading and loaded. It names the answer you want, twice. | "How would you rate our support team?" with a balanced scale from very poor to very good. |
| "How satisfied were you with the speed and price of delivery?" | Double-barrelled and assumptive. Fast but expensive has no answer, and it assumes satisfaction. | Two questions: "How would you rate delivery speed?" and "How would you rate delivery price?", each with a "did not use" option. |
| "How often do you use our amazing new dashboard?" | Loaded wording plus a vague quantifier. "Often" means different things to different people. | "In the last 30 days, how many days did you open the dashboard?" with the options 0, 1-3, 4-10, and 11 or more. |
| "Would you not be unwilling to recommend us to a colleague?" | Double negative. Answers measure reading comprehension, not intent. | "How likely are you to recommend us to a colleague?" on a 0 to 10 scale. |
| "Everyone knows remote work is better; do you always work from home?" | Leading premise plus an absolute. There is no honest answer for a hybrid worker. | "In a typical week, how many days do you work from home?" with the options 0 through 5. |
| "How much did you enjoy your favourite feature in our best-in-class platform?" | Assumptive and loaded. It presumes a favourite exists and that it was enjoyed. | "Which feature did you use most?" followed by "How would you rate that feature?", with "none of these" available. |
Built for every team writing survey questions
Wording problems cost almost nothing to fix before a survey goes out, and there is no fixing them once fieldwork closes. Run the draft through first, then pair it with an AI survey platform when the answers you collect are sensitive.
Researchers & data teams
Catch leading and double-barrelled items before they contaminate a dataset you cannot re-collect.
Product & UX teams
Stop writing questions that flatter the feature you just shipped.
Marketing & customer experience
Get NPS and satisfaction scores you can defend when someone asks how the question was worded.
HR & people teams
Keep engagement surveys neutral, so staff answer what they think rather than what is expected.
Academics & students
Run a wording pass before an ethics review or a supervisor does it for you.
Teams adopting AI drafting
AI-drafted questionnaires inherit the flattery in their prompts. Check the output before it ships.
Now protect the answers you collect.
BlockSurvey is an AI survey platform, encrypted end to end, so the responses you gather are never sold, mined, or used to train models.