> 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/judge-guide/reviewing-a-filing.md).

# Reviewing a Filing

When you click a filing row in your inbox, the review screen opens. This is a split-panel layout with the document viewer on the left and the filing details panel on the right.

## The Review Layout

* **Left side** -- a PDF viewer showing the filing's documents
* **Right side** -- a details panel with filing information, document list, and action buttons
* **Drag handle** -- the divider between the two panels can be dragged to resize. Double-click it to collapse or expand the details panel.

A breadcrumb bar at the top shows your path: **Inbox > Court > Case > Filing Number**. The filing number appears in a tab with a status badge that tells you where the filing stands:

| Badge                             | Meaning                                                                                   |
| --------------------------------- | ----------------------------------------------------------------------------------------- |
| **Pending Signature**             | The filing is waiting for your signature                                                  |
| **Signed — Pending Your Release** | The judge has signed; judicial staff are finishing edits before releasing it to the clerk |
| **Signed**                        | You signed the filing                                                                     |
| **Returned**                      | You returned the filing to the clerk                                                      |
| **Denied**                        | You denied the filing                                                                     |

Click "Inbox" to return to your inbox at any time.

When the details panel is fully collapsed, a floating action bar appears at the bottom of the screen with a **Sign Filing** button and an **Expand Panel** button so you can quickly act without re-expanding.

Once you have acted on a filing, it becomes read-only. The footer tells you why:

* "You've already signed this filing. It's read-only now."
* "You returned this filing to the clerk. It's read-only now."
* "You denied this filing. It's read-only now."

{% hint style="info" %}
**📹 GIF:** The judge review screen layout -- the PDF viewer on the left showing a document, the details panel on the right with filing info, dragging the divider to resize, and collapsing the panel to show the floating action bar.
{% endhint %}

## Filing Details Panel

The details panel is organized into numbered workflow steps: **Filing Info**, **Documents**, and **Chambers Notes**, followed by the return panel.

### Step 1: Filing Info

This section shows key details at a glance:

* **Case Number** -- the case number, or **NEW** for a new-case filing
* **Received** -- how long ago the filing arrived
* **Filer** -- who submitted the filing
* **Court** -- the court name (abbreviated for long names)
* **Case Type** -- the case type, with **Filing Type** showing the subtype
* **Case #** -- the case number (shown again when filed on an existing case)
* **Clerk** -- the clerk who routed the filing to you

### Parties

If the case has parties on file, you can expand the **Parties** section to see each party's name and role (Plaintiff, Defendant, Petitioner, Respondent, etc.).

### Clerk Routing Note

If the clerk included a note when routing the filing to you, it appears in a highlighted box below the filing info. Read this carefully -- it often contains context about why the filing needs your attention or what action the clerk expects.

{% hint style="info" %}
The routing note is set by the clerk when they send the filing to you. It cannot be edited from the judge portal.
{% endhint %}

### Step 2: Documents

The document list shows all documents in the filing. Each document displays:

* **Title** and document type
* **File size**
* A **Lead** badge on the primary document
* A **seal icon** if the document is sealed

Click any document in the list to view it in the PDF viewer on the left. The selected document is highlighted with a ring outline.

### Step 3: Chambers Notes

**Chambers Notes** are private sticky notes on the filing, shared between you and your judicial staff. Use them to flag things to look at, record your reasoning, or leave instructions for staff -- and read notes your staff left for you. The step heading shows a count of notes on the filing.

{% hint style="info" %}
Chambers notes stay inside chambers. The clerk and the filer never see them.
{% endhint %}

## Reading Documents

The PDF viewer displays the selected document. You can scroll through pages and switch between documents by clicking them in the details panel.

## Editing a Document

If a document needs changes before you sign -- fixing a date in a proposed order, striking a line, adding a short note -- use the inline editor:

1. Select the document you want to change in the document list. The editor works on whichever document is selected, not just the lead document.
2. Click the **Edit** button (marked "beta"). The document opens in the **Edit document** editor.
3. The editor has two tabs:
   * **Markup** -- add text and draw directly on the pages. New text defaults to a comfortable reading size, and text boxes are transparent so they sit cleanly on the page.
   * **Signature boxes** -- place boxes marking where a signature should go.
4. Click **Save** to apply your changes. Your markup is burned into the PDF -- it prints with the document and flows into the signed version. Click **Cancel** (**Close** on the Signature boxes tab) to leave without saving.

If you try to leave with unsaved changes, a dialog asks **"Discard edits?"** -- "You have unsaved changes to this document. If you leave the editor, your edits will be lost." Choose **Keep Editing** or **Discard Edits**.

{% hint style="info" %}
**📹 GIF:** Editing a document -- selecting a document, clicking "Edit," adding a text markup on the Markup tab, switching to the Signature boxes tab, and clicking Save to burn the changes into the PDF.
{% endhint %}

{% hint style="warning" %}
The **Sign** button is disabled while the editor is open. Save or discard your edits first, then sign.
{% endhint %}

After saving, the PDF viewer updates to show the modified version. When you sign, your edits are included in the signed document.

## PDF Tools

Below the document list, you have access to PDF tools for:

* **Margins** -- toggle margin guidelines on the document
* **Redact** -- coming soon. The button is currently disabled
* **Deny** -- place red "DENIED" stamps when you are denying all or part of the filing rather than signing it as-is (see [Signing and Returning](/judge-guide/signing-and-returning.md))
* **Organize** -- rearrange or split documents if needed


---

# 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/judge-guide/reviewing-a-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.
