How it all fits together
Raven gives a brokerage several building blocks — Intake, Document Packs, Task Lists, Transaction Templates, and Compliance Rules. On their own they each look like a separate settings tab. Together they're one system: the broker sets it up once, and every agent gets it automatically on every transaction.
Here's the whole picture in one sentence:
Packs are the ingredients, a Transaction Template is the recipe, Intake picks the variations, and Compliance Rules are the health code.
The build-a-Transaction chain
Intake → Document Packs + Task Lists → Template ⇒ Applied to a REALM
(questions) (the paperwork) (the to-dos) (the bundle) (set up in one click)
- Intake — the yes/no questions Raven asks when a transaction starts (well? septic? HOA? listing or buyer side?). The answers drive conditions — they decide which documents and tasks actually apply to this Transaction.
- Checklists: the lists of paperwork a transaction needs (disclosures, addenda, agreements).
- Task Lists: the to-do plan that's created automatically once a transaction goes under contract (your TC-grade plan, editable per side).
- Transaction Templates — the blueprint that bundles the document packs, task lists, milestones, and reminders together and applies them to a Transaction in one click — consistent across every agent, every transaction.
When an agent opens a transaction and answers the Intake questions, the Transaction Template applies: the right documents are required, the right tasks are created, and the key dates are set — all conditioned on those answers.
The governance layer
┌─────────────────────────────┐
Every REALM ─►│ Compliance Rules (org-wide) │──► gated until close
└─────────────────────────────┘
Compliance Rules sit underneath everything. They're the broker's governance — required documents, stage gates, and automations — enforced on every Transaction regardless of which Transaction Template applied. Where a Transaction Template says "this transaction needs an HOA addendum," a Compliance Rule says "no transaction closes with an unsigned agency disclosure."
Packs ≠ the same thing. A Document Pack is a checklist of paperwork attached to one transaction. Compliance Rules (sometimes shown as rule packs) are org-wide governance enforced on every transaction. Different jobs — that's why they're separate tabs.
Where leads fit in
Setting up who works the transactions is a parallel track:
Lead Sources → Routing Rules → Teams / Agents
(where leads (which source (who receives
come from) goes where) the lead)
- Lead Sources — your inbound connectors (Zillow, a website form, Follow Up Boss…). Set them up in Lead Sources.
- Routing Rules — map each source to the right Team or agent (and set conditions/priority). This lives in **Brokerage Settings → Routing Rules**.
- Teams — a team's own Routing tab controls whether it's eligible to receive leads (and round-robin, fallback). The actual source→team mapping is set in Routing Rules.
The short version
- Build your packs (documents + tasks) and your Intake questions.
- Bundle them into a Transaction Template (or have Raven draft one).
- Set your Compliance Rules once — they apply everywhere.
- Connect Lead Sources and route them to Teams.
- Agents just work their transactions — Raven sets each one up for them.
You don't have to build all of this by hand. Raven can draft a Transaction Template from a plain-English description of your transaction — a fast way to get a working setup you can then refine.