> 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, send to judge, reassign, add notes. Filer: view status. | | **Accepting** | Acceptance is in progress -- the card is being charged and the documents stamped and recorded. | Clerk, Admin | Wait for it to finish. | | **With Judge** | The clerk has sent the filing to a judge (or judicial staff) for review or signature. | Filer, Clerk, Judge, Admin | Judge: sign, return, or deny. Clerk: view status. Filer: view status. | | **Judge Signed** | The judge signed the filing. It is back in the clerk's Returned by Judge tab -- signing does not charge, stamp, or record anything. | Clerk, Judge, Admin | Clerk: accept (or record the signed version if already accepted). | | **Returned to Clerk** | A judge returned or denied the filing, with notes or DENIED stamps. | Clerk, Judge, Admin | Clerk: accept it directly, or reject. | | **Emailed to Judge** | The clerk emailed the documents to a judge who works outside the system (paper workflow). | Clerk, Admin | Clerk: await the judge's answer, then decide the filing. | | **Accepted** | The filing was accepted, charged, stamped, and recorded. | Filer, Clerk, Admin | Filer: download stamped documents. Clerk: view details, send to a judge if a signature is still needed. | | **Accepted · awaiting judge** | An accepted filing (e.g., a proposed order) was sent to a judge for signature. | Filer, Clerk, Judge, Admin | Judge: sign or return. Clerk: view status. | | **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, Edit & Resubmit the rejected portions. Clerk: view details. | | **Rejected** | The filing did not meet requirements. The clerk provided a rejection reason and optional notes. Final. | Filer, Clerk, Admin | Filer: view rejection details, Edit & Resubmit (creates a new filing). Clerk: view details. | | **Payment Failed** | The filer's card was declined at acceptance. Nothing was stamped or recorded. | Filer, Clerk, Admin | Filer: pay from the Payments due page. Clerk: wait, or reject once the payment window closes. | | **Submitted to CMS** | The accepted filing is being handed to the court's case management system. | Clerk, Admin | Wait for recording to finish. | | **Sent to Print Queue** | The filing's documents were added to a clerk's print queue. | Clerk, Admin | Clerk: print from the Printing page. | | **Printed** | The queued documents have been printed. | Clerk, Admin | View only. | | **Recorded** | Terminal state -- the filing is fully recorded with the court. In the clerk and filer views it simply displays as **Accepted**. | Filer, Clerk, Admin | View only. Filer: download stamped documents. | {% 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 sent the filing to a judge (or the judge's staff) for review or signature. The filing appears in the judge's inbox. The judge signs it, returns it, or denies it -- in every case it comes back to the **clerk**, who makes the final accept/reject decision. The filer is not notified at any judge step. ### Judge Signed and Returned to Clerk **Judge Signed** means the judge signed the filing; **Returned to Clerk** means the judge sent it back or denied it, with notes or DENIED stamps explaining why. Both land in the clerk's **Returned by Judge** tab, and the clerk can accept either one directly. A judge's signature on its own never charges the filer, stamps the documents, or records anything. ### Accepted The clerk accepted the filing. The filer's card was charged, each accepted PDF was stamped with the court stamp, and the records were created. If a signature is still needed (a proposed order, for example), the clerk can send the accepted filing to a judge -- it then shows **Accepted · awaiting judge** until the judge signs, and the clerk records the signed version. No second charge is made. ### Rejected The filing did not pass review. The clerk selected a rejection reason code (e.g., "Incomplete Filing", "Incorrect Form", "Missing Signature") and may have included explanatory notes and a cure deadline. {% hint style="warning" %} Rejection is final -- a rejected filing never re-enters the clerk's queue. To fix the problem, use **Edit & Resubmit**: it creates a **new** filing, pre-filled from the rejected one and linked back to it, which the clerk reviews fresh. {% 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. ### Payment Failed The filer's card was declined when the clerk accepted. Nothing was stamped or recorded with the court. The filer pays from their **Payments due** page; once paid, the filing returns to the clerk's queue with a **Payment collected** banner, and the clerk's acceptance will not charge again. ### Recorded The accepted filing has been fully recorded with the court -- docket entries exist and the stamped documents are available for download. This is the final state; in the clerk and filer views it displays simply as **Accepted**. {% 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 Accepted. {% 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.cottfile.com/reference/filing-statuses.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.