> 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/administering-transactions/review-transactions-and-documents.md).

# Review Transactions and Documents

Authorized transaction staff can review Deal information, monitor submitted items, communicate with agents, and approve or decline documents according to the brokerage’s process.

### Open a transaction that requires attention

1. Open **Transactions Admin**.
2. Select the appropriate operational inbox or use Search.
3. Locate the Deal using its address, MLS number, agent, office, status, or other available filters.
4. Select the Deal to open its workspace.

<figure><img src="https://1031368632-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJZySovZjoLVT1XAonI%2Fuploads%2Flk9v1pfpPqueCAvvLto7%2F2026-08-19_15-13-24.png?alt=media&amp;token=6a6dd3f6-26d6-493c-9d51-0def99083aa8" alt=""><figcaption></figcaption></figure>

### Review the Deal information

Before reviewing documents, confirm the available transaction information, including:

* Property and transaction type
* Side represented
* Primary Agent
* Buyer, seller, and other contacts
* Important dates
* Listing or sales price
* Applicable office or brokerage information

### Review a submitted document

1. Open the appropriate checklist item.
2. Open and review the submitted document.
3. Review any available Deal or checklist-item messages.
4. Approve the document when it satisfies the brokerage’s requirements, or decline it when correction is needed.

<figure><img src="https://1031368632-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJZySovZjoLVT1XAonI%2Fuploads%2FimnLmBli8RT7AD2FzGTA%2F2026-08-19_15-30-09.png?alt=media&amp;token=73a5345a-a5a6-421f-b384-4248b85618f9" alt=""><figcaption></figcaption></figure>

### Decline a document

When declining a document, provide clear feedback explaining what needs to be corrected or supplied. The agent can review the feedback, replace or correct the document, and notify the office again.

### Communicate with the agent

Use the available Deal or checklist messaging controls to provide transaction-specific guidance. Keep the communication connected to the Deal so the appropriate participants can understand the review history.

### Continue through closing

Monitor missing, awaiting-review, declined, and approved items according to the brokerage’s process. Review final dates, closing documents, CDA information, commission information, and final statuses when included in your responsibilities.

Some final statuses may be restricted to authorized administrative users.

### Related articles

* [Navigate the Transactions Admin Dashboard](/guides/deals/administering-transactions/navigate-the-transactions-admin-dashboard.md)
* [Submit Documents for Office Review](/guides/deals/submit-documents-for-office-review.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 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/administering-transactions/review-transactions-and-documents.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.
