> 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/manage-a-buyer-deal.md).
# Manage a Buyer Deal
A buyer Deal organizes the buyer, property, contract information, dates, documents, tasks, and office-review requirements associated with a purchase.
### Buyer workflow
1. Create the Deal and select the buyer side.
2. Add the buyer, Buyer Agent, and other requested contacts.
3. Add or confirm the property information.
4. Review the transaction dates and details.
5. Review the brokerage-provided checklist.
6. Prepare, upload, or send the required documents for signature.
7. Submit completed documents to the office for review.
8. Track contract deadlines and resolve office feedback.
9. Manage the transaction through closing.
### Buyer Deal information
Depending on the transaction and brokerage, the Deal may include:
* Buyer and Buyer Agent
* Property address
* Executed date
* Closing date
* Financing and inspection deadlines
* Sales price
* Title or escrow contacts
* Buyer-side checklist requirements
### Buyer Deal statuses
Buyer Deals do not follow the same MLS status-locking behavior as MLS-connected listing Deals. Available statuses still depend on the brokerage and user permissions.
### Related articles
* [Create a Deal](/guides/deals/create-a-deal.md)
* [Understand Your Deal Workspace](/guides/deals/understand-your-deal-workspace.md)
* [Manage a Deal Through Closing](/guides/deals/manage-a-deal-through-closing.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://help.rechat.com/guides/deals/manage-a-buyer-deal.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.
