> For the complete documentation index, see [llms.txt](https://docs.cottfile.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cottfile.com/reference/filing-statuses.md). # Filing Statuses Explained Every filing in Cott E-Filing has a status that tells you where it is in the review process. This page explains what each status means, who can see it, and what actions are available. *** ## Status Reference Table | Status | Description | Visible to | Available actions | | --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | -------------------------- | ----------------------------------------------------------------------------------------------- | | **Draft** | Saved but not yet submitted. The filing is incomplete or the filer chose to finish later. | Filer only | Edit, resume wizard, delete | | **Submitted** | The filer has submitted the filing. It is in the clerk queue waiting to be picked up. | Filer, Clerk, Admin | Filer: view status. Clerk: pick up for review. | | **Under Review** | A clerk has been assigned and is actively reviewing the documents. | Filer, Clerk, Admin | Clerk: accept, reject, partial accept, route to judge, reassign, add notes. Filer: view status. | | **With Judge** | The clerk has routed the filing to a judge for review or signature. | Filer, Clerk, Judge, Admin | Judge: accept, return to clerk. Clerk: view status. Filer: view status. | | **Accepted** | All documents have been accepted by the clerk (or judge). PDFs are being stamped and CMS records are being created. | Filer, Clerk, Admin | Filer: download stamped documents. Clerk: view details. | | **Rejected** | The filing did not meet requirements. The clerk provided a rejection reason and optional notes. | Filer, Clerk, Admin | Filer: view rejection details, resubmit with corrections. Clerk: view details. | | **Partial Accept** | Some documents were accepted and some were rejected. Accepted documents are stamped and recorded; rejected documents require correction. | Filer, Clerk, Admin | Filer: view per-document decisions, resubmit rejected documents. Clerk: view details. | | **Returned to Clerk** | A judge has sent the filing back to the clerk queue with notes. The clerk needs to take further action. | Clerk, Judge, Admin | Clerk: pick up and re-review. Judge: view status. | | **Recorded** | The filing has been recorded in the Verdict CMS. Docket entries have been created and parties synced. | Filer, Clerk, Admin | View only. Filer: download stamped documents. | | **Submitted to CMS** | Terminal state. The filing and all associated records are fully committed to the Verdict CMS. | Filer, Clerk, Admin | View only. | {% hint style="info" %} **📹 GIF:** The status badges on the filer dashboard -- showing a filing row with status changing from Submitted to Under Review, then expanding the row to see document-level status badges (Pending, Accepted, Rejected). {% endhint %} *** ## Status Details ### Draft The filer has started the filing wizard but has not yet submitted. Drafts are private to the filer and do not appear in any clerk queue. You can resume a draft from the **Drafts** page in the filer portal. {% hint style="info" %} Drafts are auto-saved as you progress through the wizard. If you close the browser mid-filing, your work is preserved. {% endhint %} ### Submitted The filing has left the filer's hands. It is now in the clerk queue at the selected court, waiting to be assigned to a reviewer. The filer receives a filing number and a confirmation email. No further edits are possible by the filer at this point. If you realize you made an error, contact the court before the filing is picked up for review. ### Under Review A clerk is actively reviewing the filing. The clerk examines each document, checks party information, verifies fees, and decides whether to accept or reject. The assigned clerk's name is visible on the filing. ### With Judge The clerk determined that the filing requires judicial review (for example, a proposed order needing a judge's signature). The filing appears in the judge's inbox. The judge can accept the filing or return it to the clerk with notes. ### Accepted The clerk (or judge) has approved the filing. The system stamps each accepted PDF with the court seal, recording number, date, and clerk name. CMS records are created automatically. ### Rejected The filing did not pass review. The clerk selected a rejection reason code (e.g., "Incomplete filing", "Wrong case type", "Missing required document") and may have included explanatory notes. A cure deadline may be set. {% hint style="warning" %} A rejected filing is not deleted. You can view the full rejection details on the case page and resubmit a corrected version at any time before the cure deadline. {% endhint %} ### Partial Accept Some documents in the filing were accepted and others were rejected. This happens when a filing envelope contains multiple documents and only some meet requirements. Accepted documents are stamped and recorded. The filer should review the per-document decisions and resubmit the rejected documents. ### Returned to Clerk A judge reviewed the filing and sent it back to the clerk queue. The judge's notes explain what needs to happen next. The clerk picks up the filing again to take the appropriate action. ### Recorded The accepted filing has been recorded in the Verdict CMS. This means docket entries exist, parties are synced, and financial records are created. Stamped documents are available for download. ### Submitted to CMS The final state. All data associated with the filing is fully committed to the Verdict CMS. No further status changes occur. {% hint style="info" %} **📹 GIF:** Following a filing through its status history on the case detail page -- scrolling through the timeline showing each status transition with timestamps, from Submitted through Recorded. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.cottfile.com/reference/filing-statuses.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.