> 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-deal-workspace.md).

# Understand Your Deal Workspace

Every Deal brings the people, property information, dates, documents, tasks, notes, and marketing connected to a transaction into one organized workspace.

The information and checklist available in your Deal may vary based on the transaction and your brokerage’s requirements.

<figure><img src="https://1031368632-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJZySovZjoLVT1XAonI%2Fuploads%2FwyCxaJgYh4aJlygcSyht%2F2026-08-19_13-58-38.png?alt=media&amp;token=3b2811da-af56-4d9b-aae6-641123c0dbd1" alt=""><figcaption></figcaption></figure>

### Deal header

The header identifies the property and provides the primary actions available for the Deal. Depending on the transaction, it may include:

* Property address and image
* Deal participants
* **Make Visible To Office** to take the Deal out of draft mode
* **Add Offer** for a listing without an offer
* **Email**
* Current status or **Change Status**

### Workspace tabs

Use the tabs beneath the header to manage different parts of the Deal:

* **Checklists** contains the brokerage-configured document and compliance requirements.
* **Photos** stores property photos available for the transaction and marketing.
* **Tasks** helps you track work associated with the Deal.
* **Notes** keeps transaction notes connected to the Deal.
* **Marketing** provides access to available marketing workflows using Deal information.

### Deal information

The information panel may include:

* **Timeline** with important listing, contract, and closing dates
* **Details** such as the MLS number, side represented, and property type
* **Contacts** and their roles in the transaction
* **CDA Information** when available
* **Listing Information** or buyer-related transaction information

{% hint style="warning" %}
The exact sections and fields depend on the Deal and brokerage configuration.
{% endhint %}

### Transaction checklist

The checklist organizes the documents and requirements associated with the Deal. It may contain separate sections for the listing, an offer, closing documents, or other transaction contexts.

### Unorganized Files

Unorganized Files holds uploaded or emailed documents that have not yet been assigned to a checklist item. From here, you can upload, drag and drop, or email files using the Deal’s unique email address.

### Deal controls

Depending on your permissions, the information panel may also include options to:

* Download a Deal summary
* Download a Deal history
* Download a Full Deal Archive
* Delete the Deal

### Related articles

* [Manage Deal Information, Dates, and Contacts](/guides/deals/manage-deal-information.md)
* [Understand Your Transaction Checklist](/guides/deals/understand-your-transaction-checklist.md)
* [Upload and Organize Documents](/guides/deals/upload-and-organize-documents.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-deal-workspace.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.
