> 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/correcting-a-rejected-filing.md).

# Correcting a Rejected Filing

When a clerk rejects your filing, you receive a notification and an email explaining the reason. You can correct the issues and resubmit without starting from scratch.

## Understanding the Rejection

Rejected filings stay on the **Pending** tab of your dashboard, so they are easy to spot. Open the filing to see its case detail page, where a **Rejection Details** card shows:

* **Reason** -- Why the filing was rejected.
* **Notes** -- A free-text explanation from the reviewing clerk describing what needs to be fixed.
* **Rejected on** -- The date and time of the rejection.

If the clerk left a separate **Note from the Clerk**, it appears in its own card and is also included in the rejection email.

The rejection email is titled **"Filing Rejected"** and includes the reason and notes, plus a **Correct and Resubmit** button that takes you straight to the case page.

{% hint style="info" %}
**📹 GIF:** Opening a rejected filing from the Pending tab, showing the Rejection Details card with the reason, clerk notes, and rejection date.
{% endhint %}

## Resubmitting

1. Open the rejected filing's detail page.
2. Click **Edit & Resubmit** in the top-right corner.
3. The filing wizard opens with your original data pre-filled -- court, case type, case link, parties, documents, deposits, fee waiver, and internal reference. Per-document notes to the clerk are not carried over, so re-enter any you still need.
4. A red alert at the top of the wizard summarizes the rejection: **"This filing was rejected"**, when it was rejected, the reason and notes, and -- if the clerk set a cure deadline -- **"Please resubmit by {date}"**. The deadline turns amber when it is within three days, and shows "Cure deadline passed" in red once it has expired.
5. Make the corrections -- re-upload fixed documents, change document types, or update party information -- then walk through the remaining steps and submit.

The resubmission creates a **new filing linked to the original**. Both remain in your history -- the original stays rejected, and the new one begins its own review cycle.

{% hint style="warning" %}
If a cure deadline is shown, resubmit before it expires. After the deadline passes, you may need to contact the Clerk's Office or start a new filing.
{% endhint %}

{% hint style="info" %}
**📹 GIF:** Clicking "Edit & Resubmit" on a rejected filing, the wizard opening pre-filled with the red rejection alert and cure deadline at the top, re-uploading a corrected document, and clicking Submit.
{% 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/correcting-a-rejected-filing.md?ask=<question>&goal=<user_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.