Review submissions
Submission review is where a form becomes operational. A response is not only a row of data. It is a customer, client, applicant, or teammate asking the team to do something next.
What to check first
Section titled “What to check first”When reviewing a submission, check:
- who submitted it
- which form it came from
- which published version collected it
- whether required fields are complete
- whether the next owner is obvious
- whether supported follow-up delivery succeeded, failed, or needs attention
This helps the team respond without guessing what the submitter saw.
Preserve context
Section titled “Preserve context”Do not rewrite old submissions to match the newest version of a form. If a field changed after a response arrived, the original submission should still be understandable in its original context.
That is why version-aware submission review matters. It lets the team connect a response to the public form state that created it.
Decide the next action
Section titled “Decide the next action”Common next actions include:
- reply to the submitter
- assign the submission internally
- export a set of responses
- retry failed supported follow-up
- acknowledge a known delivery issue
- update the form because the same confusion keeps appearing
The best next action should be visible from the workflow, not hidden in a teammate’s inbox.
Review patterns
Section titled “Review patterns”For low-volume forms, review submissions as they arrive. For higher-volume workflows, set an operating cadence:
- daily review for active intake
- weekly review for trends and field quality
- immediate review for high-priority forms
- monthly export or audit for reporting
The goal is to keep submissions moving through a managed process.