> For the complete documentation index, see [llms.txt](https://learn.mdjusticepassport.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.mdjusticepassport.org/attorney-referrals/conflict-check.md).

# Conflict Check

This article will show you how to conduct conflict checks for Attorney Referrals.

***

The first step in the Attorney Referrals process is to conduct a conflict check.

#### How to conduct a conflict check <a href="#how-to-conduct-a-conflict-check" id="how-to-conduct-a-conflict-check"></a>

1. When a case has been referred to you, you will receive an email with a link to conduct a conflict check. You can click the link in the email or go to the [Attorney Referrals page](https://app.mdjusticepassport.org/mjp20/attorney-referrals) and select the potential client's name.
2. The following information will be shown to conduct the conflict check:
   * County of the matter
   * Practice area (i.e., Consumer Law, Family Law)
   * Potential client's full name and address
   * Opposing party's full name, company name, and address
3. Click the "Conflict Check" button and select an option and click "Save".
4. If you have a conflict of interest, there is nothing further you need to do.
5. If you don't have a conflict of interest, you will be given read only access to the potential client's Passport to read about their case.


---

# 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://learn.mdjusticepassport.org/attorney-referrals/conflict-check.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.