> 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 from the filings themselves.

## Opening the Case View

From the review screen, two paths lead to the case view:

* Click the **case name** in the breadcrumb at the top of the review screen.
* Open the **Filings in this case** popover and click **View full case**.

Note that the **Review** link on a Processed row opens the filing in the review screen, not the case view -- open the case from there.

## What the Case View Shows

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. It does not show a full court 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. 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 case. 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, open the filing in the review screen while it is under review. There you can edit the **Case Type**, **Filing Type**, and **Parties** (via **Edit parties**, **Add Party**, and **Save Parties**) in the Filing Info section -- which also shows **Submitted**, **Filer**, **Case #**, **Division**, and **Judge**. The court itself is not editable -- a filing submitted to the wrong court must be rejected so the filer can refile in the right parish. See [Reviewing a Filing](/clerk-guide/reviewing-a-filing.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/clerk-guide/case-lookup.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.