This is the same guide agents use inside REALM.Get REALMLog in
The Complete Guide

The REALM Guide

Everything Realm does, and how to use it. The full handbook: every feature, with step-by-step instructions. Use the contents on the left to jump to a chapter.

97Chapters
15Product areas

Broker review

When your brokerage owns compliance (native governance), documents on a transaction get reviewed and approved by a broker before the Realm 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 Realms in compliance mode). The queue lists Realms that aren't fully compliant yet, so you can triage at a glance:

  • A compact table of Realms with their property, agent, team, close date, a compliance percentage, and a simple status signal.
  • Clicking a Realm opens a side panel showing that Realm's document requirements, grouped by where they stand.

The document approval flow

In a Realm's review panel, requirements are grouped so the work in front of you is obvious:

  • Blocking — required documents that are holding the Realm up.
  • Pending — documents uploaded and waiting on your review.
  • Approved — already cleared.

For each document you can:

  1. View or Download it to check it.
  2. Approve it when it's good.
  3. 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 Realm link when you need the full context of the Realm.

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 EVE 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.