Audit Questions
Audit questions help Feedbacked tell the difference between someone who used a product and someone who submitted answers without trying it.
What is an audit question?
An audit question is a verification check based on a specific detail inside your product. It might ask what appeared on a screen, which option was selected by default, or what happened after the reviewer completed a certain step.
After the survey is published, the audit question appears to reviewers like any other question in the form. Reviewers are not told which questions are being used for verification. Feedbacked uses the reviewer's answers to help verify whether they genuinely used your product or not. Audit questions should not be used as memory tests or to penalize a reviewer for a single honest mistake.
Turning a question into an audit
When building a form, select the shield icon on a question to make it an audit question. Once selected, Feedbacked will prompt you to provide the correct answer used to verify reviewer responses.
Free-response questions do not have one exact correct answer, so they require a different setup. See the free-response audits section below before creating one.
In plain terms
A normal survey question tells you what a person thinks when using your product. An audit question helps confirm that the reviewer actually used the product before sharing their opinion.
How verification works
- 01
Choose a product detail
The developer selects something a reviewer would encounter while using the product, such as a label, a default setting, a step in the setup flow, or what happens after a specific action.
- 02
Mark the question as an audit
While building the form, the developer selects the shield icon on the question. Feedbacked then prompts them to provide the correct answer. Free-response audits are configured differently, as explained in the dedicated section below.
- 03
The reviewer tries the product
Upon seeing the survey as part of a product review, the question appears as part of the survey without being identified as an audit. Someone who completed the requested action should be able to answer it naturally.
- 04
Feedbacked verifies the response
Feedbacked looks at the audit answers together with the rest of the submission. If the answers suggest that the reviewer did not use the product, the response is not counted. We keep collecting until the campaign reaches the number of verified responses purchased.
What makes a good audit question?
A good audit question is simple for a genuine reviewer to answer, but difficult to answer if the reviewer never tried the product.
- Ask about something a reviewer must actually see or do.
- Keep the wording clear and the expected answer unambiguous.
- Use details that are unlikely to change during the campaign.
- Avoid opinions, obscure trivia, or questions designed to trip people up.
Too broad
Did you look at the dashboard?
Better
Which tab opened first when you entered the dashboard?
Free-response audits
Free-response audits are more nuanced because several answers may be valid even when they use different wording. Instead of providing one exact correct answer, describe what a valid response must show. When creating a free-response audit, you will be prompted for the following fields:
Required action
State what the reviewer needed to do in the product before answering. This keeps the audit tied to the task they were asked to complete.
Required knowledge
State the product-specific detail a valid answer should demonstrate. It should be something the reviewer would reasonably know after completing the required action.
Additional information (optional)
Add any optional notes that might help distinguish a valid answer from a vague or unrelated one, without requiring the reviewer to use an exact phrase. Use this field for extra context that could help Feedbacked distinguish a valid answer from a vague, incomplete, or unrelated one. For example, you might note acceptable variations in how the answer may be worded, or clarify that shorter responses should pass if they mention a specific word or phrase.
Example
Suppose the audit question asks, “What happens after you archive a project?” The required action would be archiving a project. The required knowledge would be that the project is removed from the active project list and appears in the Archived section.
In the additional information field, you could explain that answers such as “it moves to Archived,” “it disappears from my active projects,” or “I can find it under archived projects” should all be accepted. You could also note that the reviewer does not need to mention the confirmation message for the answer to pass.
The goal is to judge whether the response demonstrates the required experience and knowledge, not whether it matches a single sentence word for word.
What this means for reviewers
Audit questions are not meant to be tricky. Use the product as instructed, pay attention to the experience, and answer honestly. As a reviewer, if you genuinely try the product and complete the survey, you will likely pass on your first try. A response may be rejected and will not be eligible for payment when the answers show that the product was not actually used.
Why Feedbacked uses them
Developers should receive feedback from people who actually tried what they built. Reviewers should be rewarded for doing real work. Audit questions help protect both sides, so developers pay for completed reviews rather than guesses.