Client consents (BBA, Listing, Agency)
A few documents are special because they bind the client to you, not to a property:
- Buyer Broker Agreement (BBA) — buyer side
- Listing Agreement — seller side
- Agency Disclosure — both sides
These are consents, and they're owned by the contact, not by any one transaction.
Why consents follow the contact
A buyer doesn't sign a new Buyer Broker Agreement for every house they look at — they sign one BBA that covers every home they view, across every transaction. So in Raven, the consent lives on the contact. Each transaction reads through to the contact's consent status rather than keeping its own separate copy.
The practical upshot:
- Collect a consent once, as soon as you start working a lead — you don't have to wait for a transaction to exist.
- Every transaction for that client shows the same, up-to-date consent status.
- A signed BBA shows as satisfied on all of that buyer's transactions at once — you won't be asked to collect it again on the next transaction.
Because the contact is the single source of truth, you can't have one transaction saying a consent is Missing while the client has actually signed it. Approve it once on the contact, and every transaction reflects it.
Collecting a consent
- Open the contact (from People) or any transaction where they're the Client.
- Find the consent on the checklist — BBA / Listing Agreement / Agency Disclosure.
- Send it for signature or upload the signed copy.
- Once signed and reviewed, it shows as satisfied everywhere that contact appears.
Broker review
Consents are part of what a broker can review. When a consent is signed, it can route for broker review, and that review is recorded as a permanent, append-only history — corrections add a new entry rather than changing the old one. See Broker review.