> 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/guides/deals/understand-your-transaction-checklist.md).

# Understand Your Transaction Checklist

Your transaction checklist is the roadmap for the documents and compliance requirements associated with a Deal. It helps you understand what is needed and organize completed documents.

<figure><img src="https://1031368632-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJZySovZjoLVT1XAonI%2Fuploads%2FAqpI6xctp579Wa0r8Dil%2F2026-08-19_13-58-38.png?alt=media&amp;token=fe7d81c0-43fe-4ab0-94d0-964bb932c4ef" alt=""><figcaption></figcaption></figure>

### Why checklists vary

Your checklist is generated using the Deal information and your brokerage’s configuration. Checklist sections and items may vary based on:

* Brokerage or office
* Property type
* Transaction type
* Side represented
* Listing or offer context
* State or market

{% hint style="warning" %}
The forms shown in Help Center examples may not be the forms available in your Deal.
{% endhint %}

### Understand checklist sections

A transaction may contain several sections:

<table data-header-hidden><thead><tr><th width="180.484375"></th><th></th></tr></thead><tbody><tr><td><strong>Section</strong></td><td><strong>Purpose</strong></td></tr><tr><td>Listing</td><td>Documents and requirements associated with securing and managing the listing</td></tr><tr><td>Offer</td><td>Contract documents, buyer information, dates, and requirements associated with an offer</td></tr><tr><td>Closing Documents</td><td>Documents needed to complete, reconcile, or retain the transaction</td></tr><tr><td>Unorganized Files</td><td>Files that have been uploaded or emailed but not assigned to a checklist item</td></tr></tbody></table>

Other sections may appear based on your brokerage’s process.

### Understand checklist items

Each row represents a form, document requirement, upload destination, or other checklist task. An item may allow you to:

* Prepare a form
* Upload a completed document
* View an existing document
* Send documents for signature
* Message the office
* Notify the office for review

Available actions depend on the checklist item and your brokerage’s setup.

### Understand checklist labels and review statuses

You may see labels such as:

* **Required**: Your brokerage requires the item for the transaction.
* **Private**: Access to the item is restricted to Admins.
* **Office Notified**: The office has been notified that the item is ready for attention.
* **Approved**: The office accepted the submitted document.
* **Declined**: The submitted document requires correction or additional attention.

### Add an item

Select **Add** at the bottom of an available checklist section to add an item when needed. Brokerage-required items should not be removed or replaced unless directed by your office.

### When an offer is added

Adding an offer to a listing Deal will create a separate Offer checklist while preserving the original Listing checklist. The Offer section contains the contract-specific documents and requirements for that offer.

### Related articles

* [Upload and Organize Documents](/guides/deals/upload-and-organize-documents.md)
* [Submit Documents for Office Review](/guides/deals/submit-documents-for-office-review.md)
* [Add and Manage an Offer on a Listing](/guides/deals/add-and-manage-an-offer-on-a-listing.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 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://help.rechat.com/guides/deals/understand-your-transaction-checklist.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.