> For the complete documentation index, see [llms.txt](https://docs.courtaid.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.courtaid.ai/getting-started/your-first-search.md).

# Your first search

The fastest way to get value from CourtAid is a plain-English search. You don't need Boolean operators or exact citations — describe the legal issue and let semantic search find relevant documents.

## Step 1 — Set your jurisdiction

Before searching, make sure you're on the right country:

1. Check the **flag** in the sidebar or header
2. Open **Filters** and confirm **Jurisdiction** and **Court** match your matter

See [Changing countries](https://docs.courtaid.ai/legal-research-and-search/changing-countries.md) and [Using filters](https://docs.courtaid.ai/legal-research-and-search/using-filters.md).

## Step 2 — Open Search

Click **Search** in the sidebar (marked **Free**). You'll see the search input, mode toggle, and filter panel.

![Search page with Smart mode selected](https://1143104512-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUoFACnrJdsxVDAKioc81%2Fuploads%2Fgit-blob-43f3a97ba6b29eb4c0ec4a3fb19480c0e1d5f7b6%2Fsearch-page.png?alt=media)

## Step 3 — Write a natural-language query

In **Smart** mode, describe what you're looking for as you would to a colleague:

```
employer liability for psychiatric injury from workplace bullying
whether silence can amount to misrepresentation in contract
recent unfair dismissal cases involving casual employees
```

**Tips:**

* Name the **legal issue**, not just a broad topic — *"constructive dismissal due to role change"* beats *"employment"*
* Include **jurisdiction context** in the query if you haven't set filters — e.g. *"NSW duty of care in schools"*
* Use **Boolean** mode if you know exact words that must appear — see [Semantic search](https://docs.courtaid.ai/legal-research-and-search/semantic-search.md)

## Step 4 — Narrow with filters (optional)

Open the filter panel to restrict results before or after searching:

* **Document Type** — Judgements, Legislation, or both
* **Jurisdiction** — e.g. Victoria, Federal
* **Court** — e.g. Supreme Court of Victoria
* **Categories** — legal topic areas

![Filters panel](https://1143104512-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUoFACnrJdsxVDAKioc81%2Fuploads%2Fgit-blob-fe8ff58311cd3ececfe5e24e98b60edabea571d0%2Ffilters-panel.png?alt=media)

## Step 5 — Review results

Each result shows a title, date, jurisdiction, summary blurb, and action buttons:

| Action            | Use it to…                                                                                 |
| ----------------- | ------------------------------------------------------------------------------------------ |
| **Title** (click) | Open [Chat PDF](https://docs.courtaid.ai/chat-and-documents/chat-pdf.md) for this document |
| **Summary**       | Read the full AI-generated case summary                                                    |
| **Chat PDF**      | Ask questions about this specific document                                                 |
| **Save**          | Add the case to a [matter](https://docs.courtaid.ai/matter-workspaces/matters.md)          |
| **Original**      | Open the published source on the court or legislation website                              |

![Search result card](https://1143104512-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUoFACnrJdsxVDAKioc81%2Fuploads%2Fgit-blob-dd48b471df397f70cf28661544a3c55b14d25dec%2Fsearch-result-card.png?alt=media)

## Step 6 — Explore further

Once you have a few promising results:

* Switch to **Map** view to see how cases cite each other — see [Citation map](https://docs.courtaid.ai/legal-research-and-search/citation-map.md)
* Click **Cites** or **Cited by** tags on a result to explore precedent relationships
* **Save** key authorities to a matter as you go
* Switch to **Chat** mode if you want a synthesised answer instead of a list

## Search vs Chat — which first?

| Start with **Search** if…                 | Start with **Chat** if…                         |
| ----------------------------------------- | ----------------------------------------------- |
| You want to browse and compare many cases | You want a direct answer to a specific question |
| You're building a reading list            | You need synthesis across multiple sources      |
| You don't want to use a query             | You're happy to use one of your AI queries      |

Search is free and unlimited. Chat uses your query allowance — see [Plans, trials & query limits](https://docs.courtaid.ai/account-and-billing/plans-and-queries.md).

## Related

* [Semantic search (Smart & Boolean)](https://docs.courtaid.ai/legal-research-and-search/semantic-search.md)
* [Document summaries](https://docs.courtaid.ai/legal-research-and-search/document-summaries.md)
* [Common use cases](https://docs.courtaid.ai/getting-started/common-use-cases.md)


---

# 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.courtaid.ai/getting-started/your-first-search.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.
