What is resubmission?
Resubmission is the return of a corrected submission after the first one was found deficient. Each loop carries a full cycle of cost, including the reviewer's second reading and the applicant's wait between the two. A resubmission is evidence about the form rather than about the applicant.
Why every resubmission is a form defect, counted late
Resubmission is usually recorded as a workflow state, which is why it is so rarely treated as a defect count. It is the clearest signal a form produces about its own design, since each loop names a field the applicant could not answer correctly with the information in front of them. Reviewers absorb the cost while the applicant absorbs the delay, so neither party is positioned to argue for the redesign that would remove it. Reading resubmission reasons as a defect register, field by field, is how the loop is closed rather than managed.
- A resubmission reason names the field that defeated the applicant.
- Each loop costs a second review as well as the applicant's elapsed waiting time.
- Resubmission rates concentrate in a small number of fields on most forms.
- Counting reasons per field converts a workflow state into a design input.
How resubmission works
- The reviewer records a deficiency against named fields rather than the submission.
- The applicant receives the specific fields requiring correction with a reason for each.
- Previously accepted fields are retained, so only the deficiency is re-entered.
- The corrected submission references the original and its reviewer.
- Review of the resubmission is limited to the fields that changed.
- Deficiency reasons are aggregated per field and returned to whoever owns the form.
How resubmission is evaluated
Resubmission is measured as a defect rate on the form rather than as throughput on the queue. Examine the following per form version:
- resubmission rate by deficiency reason
- concentration of deficiencies across fields
- elapsed time from deficiency notice to corrected submission
- share of applicants who never return after a deficiency notice
- second resubmission rate on the same field
Limitations, risks and common failure modes
- Deficiency notices cite a clause rather than naming the field to correct.
- Applicants re-enter the whole form, introducing errors in fields already accepted.
- Resubmission reasons are recorded as free text and therefore never aggregated.
- The reviewer who raised the deficiency is unavailable when the correction arrives.
- Applicants who abandon after a notice are absent from the completion statistics.