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

Building a Transaction Template

Building a Transaction Template is broker/admin work. You assemble the documents, milestones, communications, rules, and Vault policy a kind of transaction needs, then publish a version your team can apply.

Where to find it

Go to Brokerage Settings → Realm Settings → Transaction Templates. You'll see a list of your brokerage's Transaction Templates with their state, transaction type, side, status, and version.

Create a Transaction Template

  1. Click New Transaction Template.
  2. Give it a clear name (for example, "Standard Buyer Purchase" or "Arizona Listing").
  3. Optionally set the transaction type, side, state, county, city, financing type, and property type. These help Realm auto-match the Transaction Template to the right Realms later.
  4. Click Create Transaction Template. It starts as a draft.

You can also let EVE write a first draft for you — see Draft with EVE.

Add the pieces

Open the Transaction Template to build it out:

  • Compliance Packs — attach the Compliance Packs (built from your document packs) whose requirements this transaction needs. For each, choose Apply when: Always, or only when a condition is true (the property has a well, septic, an HOA, solar, or the transaction is a referral).
  • Milestones (Timeline) — add deadlines. Each anchors to a Realm date (Contract date, Acceptance date, Close of escrow, and so on) plus an offset in days. For example, Contract date +10 makes BINSR due ten days after contract. Leave the anchor on Manual for a date set per Realm. Mark Blocks progress for a milestone that should gate the stage (this only hard-blocks where compliance enforcement is on — see Compliance overview).
  • Communications — add reminders and messages. Each schedules relative to a Realm date (for example, a BINSR reminder at *BINSR due −3 days*). Choose a channel, an audience, and a send mode. Client-facing messages default to Draft for review — nothing auto-sends.
  • Vault Policy — choose when a Realm on this Transaction Template gets archived (on close, on broker approval, or when all required items are complete) and how long to retain it.

Publish a version

When the Transaction Template is ready, click Publish. Publishing:

  • Makes the Transaction Template active so your team can apply it to Realms.
  • Captures an immutable version of the whole blueprint. Realms that apply it keep that exact version.

Editing a published Transaction Template creates a new draft version. It never changes Realms that already applied an earlier version. Re-publish after editing so your team gets the update on new Realms.