Broker review
When your brokerage owns compliance (native governance), documents on a transaction get reviewed and approved by a broker before it can move forward. The broker review queue is where that work happens.
The broker review queue
Open it from the Compliance entry point (it lives in the workspace shell, with transactions in compliance mode). The queue lists transactions that aren't fully compliant yet, so you can triage at a glance:
- A compact table of transactions with their property, agent, team, close date, a compliance percentage, and a simple status signal.
- Clicking a transaction opens a side panel showing that transaction's document requirements, grouped by where they stand.
The document approval flow
In a transaction's review panel, requirements are grouped so the work in front of you is obvious:
- Blocking — required documents that are holding the transaction up.
- Pending — documents uploaded and waiting on your review.
- Approved — already cleared.
For each document you can:
- View or Download it to check it.
- Approve it when it's good.
- Reject it (with a reason) when it needs to be redone.
There's also an Approve All Ready action to clear everything that's good in one pass, and an Open Full transaction link when you need the full context of the transaction.
Approvals and rejections are recorded as permanent history. A correction adds a new entry — it never quietly overwrites what happened before — so there's always a clear record of who reviewed what, and when.
Advisory checklist vs full enforcement
What broker review does depends on your Workspace's governance:
- Native — full enforcement. Blocking requirements gate stage changes and closing until a broker approves them. This is the queue described above.
- External — advisory checklist. The same requirements show as a checklist and Raven may nudge, but nothing hard-stops the transaction; the outside brokerage or system owns the sign-off.
- Self — minimal. Requirements are informational; there's no broker approval step.
So a brokerage running native compliance gets the review-and-approve flow; a team under external governance sees the advisory version of the same information. See Compliance overview for the full picture.