Make filing packet a stand-alone case-file task
Treat filing packet as a short list of facts to confirm, not a single yes-or-no impression. The correct complaint form and attachments goes on the first line; signatures and dates goes on the next, each with its own source noted.
This step usually falls before any deadline is running, which makes it the least costly point to fix a mistaken assumption. Use it to close out the right number of copies if paper filing before that assumption can travel into a filing or a service step.
Open the file note with the correct complaint form and attachments, and add signatures and dates right below, with its own citation.
Work from facts when reviewing this step
Round out the review by checking the right number of copies if paper filing, fee or fee-waiver material, and local cover sheets. None of the three should rest on memory alone — each needs a document or citation behind it.
One dated line per fact is enough, as long as it is sourced. Cite the source for fee or fee-waiver material, and connect local cover sheets to its supporting record.
Records that make filing packet traceable
Start the file with the core documents, and note the correct complaint form and attachments and local cover sheets as two separate, independently-checkable entries.
The scenario below illustrates a properly documented file. After the facts are confirmed, attach the right number of copies if paper filing to its source document and the applicable official guidance.
The example logs signatures and dates and fee or fee-waiver material as two independent facts. Note how each affects the outcome separately, since the scenario is meant to organize the facts, not replace the governing local rule.
State-specific checks and next steps for filing packet
The recurring error on filing packet is assuming a procedure from a different state carries over. Recheck the local instruction that actually controls this step before acting on it.