> For the complete documentation index, see [llms.txt](https://help.rechat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rechat.com/appendix/brokerage-set-up/transaction-management-deals/setting-up-deals/creating-checklists.md).
# Creating Checklists
Checklists are the foundation of Deals in Rechat. They define the tasks and documents required for agents to remain compliant.
**Step 1:** From **Deals Settings**, select **Checklists**.
**Step 2:** Click **Create Checklist**.
**Step 3:** Enter a **Checklist** **Name**.
**Step 4:** Add **forms**, **tasks,** **splitters**, and **general** **comments** line by line.
{% hint style="warning" %}
**Checklist Item Types**
#### **Form**
* A digitized form that must be completed (e.g., Listing Agreement, Disclosure).
* Can be marked **Required** or **Optional**.
* Can be routed to specific **Inboxes** for admin review.
* Best for contracts and compliance documents.
#### **Generic Task**
* A folder for agents or admins to upload documents to.
* Does not require a file upload, but one is possible.
* Best for action items that help keep the transaction moving forward.
#### **Splitter**
* A section divider that visually separates checklist items.
* Helps organize longer checklists into logical phases (e.g., “Pre-Listing,” “Under Contract,” “Closing”).
* No action or upload required, purely organizational.
#### **General Comments**
* Behaves similarly to Generic Tasks.
* Appears in the checklist but doesn’t require action.
{% endhint %}
**Examples:** Listing Agreement, Seller’s Disclosure, Inspection Report(s).
---
# 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://help.rechat.com/appendix/brokerage-set-up/transaction-management-deals/setting-up-deals/creating-checklists.md?ask=&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.
