> 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/judicial-staff.md).

# Judicial Staff

Judicial staff are the chambers team -- law clerks and assistants who prepare filings for a judge and finish them after signing. This page covers what judicial staff can do in the portal and how work flows between staff and judge.

{% hint style="info" %}
Judicial staff are **linked to judges by a court administrator** on the Users page. A staff member sees nothing in their inbox until they are linked to at least one judge.
{% endhint %}

## Your Inbox as Judicial Staff

As judicial staff, your inbox shows the filings of **every judge you are linked to**, combined into one list.

* The **For** column tells you which judge each filing is addressed to.
* The **"Your desk"** filter narrows the list to filings routed directly to you.

Clerks can route a filing either to a judge or directly to a staff member -- so some filings land on your desk first for preparation, while others go straight to the judge.

## What Judicial Staff Can Do

Before the judge sees a filing, you can prepare it:

* **Review** the filing -- the review screen is the same one the judge uses.
* **Mark up documents** -- use the **Edit** (beta) editor to add text and drawings, which are burned into the PDF on save.
* **Leave Chambers Notes** -- private sticky notes shared between you and the judge. The clerk and filer never see them.
* **Place signature boxes** -- mark exactly where the judge should sign on each document. When the judge opens the sign dialog, it starts at the boxes you placed.
* **Forward to the judge** -- click **Send to Judge** when the filing is ready for signature.

{% hint style="info" %}
**📹 GIF:** A judicial staff member preparing a filing -- opening it from the combined inbox, leaving a chambers note, placing a signature box on the order, and clicking "Send to Judge."
{% endhint %}

## After the Judge Signs

If the judge's signed filings are set to come to staff (their "After signing, send filings to" preference, or their choice on an individual filing), the signed filing returns to your inbox with the badge **"Signed — Pending Your Release."**

At this point you:

1. Finish any remaining edits to the documents.
2. Click **Send to Clerk** to release the filing to the clerk's office.

The filing then lands in the clerk's Returned by Judge queue at High priority, and the clerk records it.

## What Judicial Staff Cannot Do

Judicial staff can **never sign or deny** a filing. Signing and denial stamps always carry the judge's own signature and can only be applied by the judge.

| You can                              | You cannot                                         |
| ------------------------------------ | -------------------------------------------------- |
| See every linked judge's inbox       | Sign a filing                                      |
| Review and mark up documents         | Deny a filing or place DENIED stamps               |
| Leave chambers notes                 | Link yourself to a judge (a court admin does this) |
| Place signature boxes for the judge  |                                                    |
| Send a filing to the judge           |                                                    |
| Release a signed filing to the clerk |                                                    |


---

# 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/judicial-staff.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.