Audit questions

When a startup runs a review on Feedbacked, they build a survey with their own questions. Things like how intuitive the onboarding felt, what confused them, what they liked. But a survey alone can't tell you whether the person actually used the app. Anyone can guess.

Audit questions solve that. They're a set of hidden verification questions that only someone who genuinely went through the app can answer correctly. A startup picks a few specific moments in their product, like a screen, a default value, or a specific step in the flow, and turns those into questions. Testers who fail them are filtered out automatically and don't get paid.

The questions are invisible to testers in the sense that they look identical to the rest of the survey. There's no label that says “this is a check.” Someone skimming through without actually trying the app will fail them naturally. Someone who genuinely used it will answer them without thinking twice.

When you create a review, you'll write your audit questions the same way you write any other question, just mark them as audits. You set the correct answer, and Feedbacked handles the rest. You can add as many as you want, though a small number of well-chosen ones is usually enough. Keep in mind that if too high a percent of testers fail your audit questions, your survey will be taken down. Try not to make the audits too difficult. When free response questions are made into audits, only very similar tester responses will pass. Make sure that your free response audit questions are not ambiguous, or this may lead to your surveys being taken down.

If you're a tester, audit questions aren't something to worry about. If you actually try the app before completing the survey, you should pass. There is no penalty for failing a single audit question. They're not designed to be tricky, they're designed to catch people who didn't try the app at all.