> 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/filer-guide/tracking-your-filings.md). # Tracking Your Filings After you submit a filing, you can track its progress from the dashboard or the case detail page. ## The Filings Table The **My Filings** table on the dashboard organizes everything into three tabs, each with a count badge: * **Pending** -- Every filing still waiting on a final outcome, including rejected and payment-failed filings. Columns: Case # (a green "NEW" badge for a case without a number yet), Court, Parties, Documents, Fees, Status, and Submitted (newest first). Search by case number, court, case type, or party; filter by Status, Court, Parties, or Document Type. * **Approved** -- Accepted filings grouped by case, one row per case, sorted by approval date. Expand a case to see its filings and documents. * **Drafts** -- Filings you started but have not yet submitted. Clicking a row on the Pending tab opens the full case detail page. {% hint style="info" %} **📹 GIF:** The My Filings table -- switching between the Pending, Approved, and Drafts tabs, then clicking a Pending row to open the case detail page. {% endhint %} ## Filing Statuses Your filing moves through these statuses as it is processed: | Status | Meaning | | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Submitted** | Your filing has been received and is waiting in the clerk's queue. | | **Under Review** | A clerk has picked up your filing and is reviewing the documents. | | **With Judge** | The filing has been routed to a judge for approval (required for certain filing types). | | **Judge Signed** | The judge has signed, and the filing is heading back for recording. | | **Returned to Clerk** | The judge sent the filing back to the clerk for further handling. | | **Accepted** | The filing has been accepted and is being recorded with the court. | | **Partial Accept** | Some documents were accepted and others were rejected. Check the document details to see which ones need correction. | | **Payment Failed** | The clerk accepted the filing but the card charge failed, so nothing is on the court record yet. Pay from the **Payments due** page to send it back for recording. | | **Rejected** | The filing was rejected by the clerk. See [Correcting a Rejected Filing](/filer-guide/correcting-a-rejected-filing.md) for next steps. | | **Recorded** | The filing has been fully processed and recorded with the court. This is the final state for a successful filing. | Rejected and payment-failed filings stay on the **Pending** tab until resolved, so nothing that needs your attention is hidden. ## The Case Detail Page Click any Pending row to open the case detail page. It shows: * **Header** -- The case number (or your filing number if no case number has been assigned yet), the current status badge, the case title (masked as "Sealed" or "Secured" on protected cases), a back arrow, and an **Edit & Resubmit** button when the filing was rejected. * **Four summary cards** -- Court, Filing Type, Filed Date (or "Not submitted"), and Filing Category (new or existing case). * **Rejection Details** -- If the filing was rejected, a highlighted card shows the reason, the clerk's notes, and when it was rejected. * **Note from the Clerk** -- If the clerk left you a note when accepting or rejecting, it appears in its own card. The same note is included in the acceptance or rejection email. * **Payment history** -- Charges related to this case appear below the tabs. ### Tabs * **Filings (N)** -- Your filings on this case, each with its case number (or "NEW"), status, court and type, lead document, and date. * **Parties (N)** -- All parties on the case. * **Documents (N)** -- Every document with its Lead, Sealed, or Redacted badge, document type, file size, status badge, and a single **Download** button. Download always serves the best available version of the document -- the signed copy if a judge signed it, otherwise the edited, stamped, or original file. {% hint style="info" %} **📹 GIF:** The case detail page -- the header with the status badge, the four summary cards, the Note from the Clerk card, and switching between the Filings, Parties, and Documents tabs, then clicking Download on a document. {% endhint %} ## Failed Payments If a filing's charge fails at acceptance, the filing moves to **Payment Failed** -- it is not stamped or recorded until it's paid. A **Payments due** banner on the dashboard shows how many filings are waiting and the total due; click **Review & pay** to pick a card and pay one or all of them at once. Once paid, the filing returns to the clerk's queue for recording, and the clerk's acceptance never charges you a second time. See [Payments, Deposits & Receipts](/filer-guide/wallet-and-payments.md) for the full flow. {% hint style="info" %} You will receive a notification and an email whenever your filing status changes. Check the Notifications page to see all updates -- see [Notifications and Email Preferences](/filer-guide/notifications.md). {% 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/filer-guide/tracking-your-filings.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.