> 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/clerk-guide/case-lookup.md).

# Case View

There is no dedicated "Case Lookup" search box in the clerk console -- the sidebar has no lookup or search feature. Instead, you reach a read-only case view directly from filings you have already processed.

## Opening the Case View

From the queue, go to the **Processed** tab and open the **Accepted** (or **Rejected**) sub-tab. Each row groups filings by case. Expand a case and use the **Review** link on a filing to open the read-only case view for that filing's case.

The case view lives at a per-filing URL and is built from the filing record itself. The Verdict CMS mirror tables were removed, so this view does not pull a live docket from Verdict -- it shows what the e-filing system holds for that filing.

## Case View

The case view header displays:

* **Case title** (e.g., "Smith v. Jones")
* **Case number** (or the filing number if no case number has been assigned)
* **Court name**
* **Case type** and subtype
* **Filed date**
* **Status badge**

A **Send to Printer** button in the header adds all non-rejected documents on the case to your print queue. See [Printing](/clerk-guide/printing.md).

Below the header, four tabs organize the data:

### Timeline

A chronological view derived from the filing -- the case-opened event and the filing's own submitted / accepted / rejected events. Because the CMS mirror was removed, it does not show a full Verdict docket; richer docket data is a planned follow-up. If there is nothing to show, the tab reads "No timeline events yet."

### Parties

The parties on the filing, showing each party's name and role (Plaintiff, Defendant, Petitioner, Respondent, etc.) and active/inactive status.

### Documents

This tab is currently an empty placeholder -- case-level documents are not populated here while the CMS mirror is absent. To view a filing's documents, open the filing in the review screen instead (the **Filings** tab links straight to it).

### Filings

The e-filings tied to this view. Each row shows the filer, the filing status, the submission date, and a document count, with a **Review** link that opens the filing in the review screen.

{% hint style="info" %}
The case view is read-only. To make changes -- party information, case type, or the linked CMS case -- edit the filing on the review screen while it is under review. See [Reviewing a Filing](/clerk-guide/reviewing-a-filing.md).
{% endhint %}

## Linking a Filing to an Existing Case

If a filer submits a new-case filing that should be on an existing case (or links to the wrong case), you can correct this from the review screen, not the case view:

1. Open the filing in the review screen.
2. In the filing details section, click the CMS case field.
3. Search for the correct case by number or title.
4. Select it. The filing is now linked to that case and will be recorded there when accepted.

{% hint style="info" %}
**📹 GIF:** Linking a filing to an existing case -- clicking the CMS case field in the review panel, typing a case number in the search box, selecting the correct case from the results, and seeing the case context update.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cottfile.com/clerk-guide/case-lookup.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.