A public form supports a workflow that starts before submission and continues afterward. Staff need to receive the information in a usable way, while visitors need clear instructions and a meaningful confirmation of what happens next.
Check the path around the form
Use fictional information to review how a visitor finds the correct form, understands the requested fields, corrects a mistake, and completes submission. Ask the organization's accessibility specialists to define the necessary evaluation. GSA's accessibility testing resources cover methods for reviewing websites, software, and electronic documents; a successful submission by one tester does not settle every user need.
Review the receiving task
Ask the staff owner where submissions arrive, how they are assigned, and how incomplete or duplicate entries are handled. Confirm who maintains the public instructions when the internal process changes. Keep sensitive records within approved systems and do not use actual citizen data in informal demonstrations. Test the confirmation message against the process staff are prepared to deliver. Review the next-step wording with the staff member who normally answers submission questions.
Practical takeaway
Review both sides of the form. The public experience and the receiving team's workflow need to agree about what was submitted and what happens next.