Read it as the person answering.
Your internal field names are not necessarily good questions. Replace shorthand with plain language, explain unfamiliar terms, and make it clear why personal information is needed.
- Does the introduction explain the purpose?
- Are required questions truly essential?
- Does the completion message explain the next step?
Test the paths, not just the happy path.
Preview is useful, but a published test submission checks a different boundary. Try each conditional path, an empty required answer, a long answer, and a small screen. Then confirm that the received response matches what you entered.
- Try every conditional visibility choice.
- Check keyboard navigation and visible focus.
- Confirm your live link still shows the published form while you edit a draft.
Follow one answer all the way through.
Look at the inbox record, open the CSV export, and check any configured webhook receiver. A form is ready only when the person who needs the information can actually use it. During launch preview, use sample data and evaluate the stated limitations before involving clients.
- Check field labels and values in the exported file.
- Verify delivery and downstream automation separately.
- Decide who reviews responses and how often.