Glossary

The product words Realm uses, defined in plain language. When a term is fuzzy anywhere else in this runbook, look it up here. Entries are sorted alphabetically.

---

Access Role. An optional, named bundle of extra permissions layered on top of a member's Position: the agent who also runs the office, the coordinator who owns compliance. Built and edited under Brokerage Settings → Users & Roles. See Users & Roles.

Agency disclosure. A consent document that explains the agency relationship to a client. One of the client consents Realm tracks, owned by the contact. See Consent.

Autonomy mode (Suggest / Guided / Autopilot). How much EVE does on its own. Suggest — EVE proposes, you approve everything. Guided — EVE handles routine steps and checks in on the bigger ones. Autopilot — EVE runs approved routines on its own and keeps you informed. You set the mode; you can change it any time.

Broker review. The step where a broker (or whoever holds compliance authority) checks a REALM's documents and lets it proceed. Whether broker review is required, advisory, or off depends on your governance type. See Broker review.

Business calendar. The brokerage's timezone, set under Brokerage Settings → General. Close dates, automatic stage moves and the Vault seal read "today" in this zone, never the server's.

Capability. A specific permission to do something ("can manage teams", "can use broker review", "can manage billing"). Realm decides what you can do based on capabilities, not job titles — so the right people get the right access without bending roles to fit.

Clear Cooperation. The NAR policy requiring a listing to be filed with the MLS within one business day of any public marketing. Realm tracks the countdown on the listing REALM and nudges the agent and broker before the deadline, so a listing doesn't fall out of compliance. See Compliance overview.

Commission plan. The split, cap, and fees that define how a transaction's money is divided. Brokers build a library of plans and assign them to agents; Realm resolves the agent's plan, assignment, and any override into one effective commission. See Commission plans.

Compliance pack. The enforcement layer for a transaction type — the broker rules, stage gates, and automations applied across your agents and teams. A Compliance pack is about governance, not about listing required files. (Contrast with a Document pack, which is just the checklist of documents.) See Compliance packs.

Compliance provider. Where compliance is actually executed for your Workspace — for example Realm's own engine, or an outside platform. It's a separate axis from your governance type and your workspace type: none of the three implies the others.

Consent (BBA, Listing, Agency). A signed agreement between the client and the agent/broker — a Buyer Broker Agreement (BBA), Listing Agreement, or Agency Disclosure. A consent belongs to the person, not a property: a buyer signs one BBA that covers every home they look at across every REALM. Each REALM reads through to the contact's consent status, so it's never out of sync. See Client consents.

Coordinator (Operations desk). The transaction-coordinator workflow, reached from the Operations nav entry. A team lead, admin, or coordinator uses it to request missing documents from agents and to deliver each completed REALM file to compliance. It assists — it isn't a gate; the agent still owns the file.

Demo session. A read-only tour of Realm. You can click around and see how everything works, but writes are blocked — nothing you do in a demo session changes real data.

Document pack (requirement pack). A reusable checklist of the documents a REALM requires. You apply a pack to a REALM (Documents → Apply Pack) and it lists what's needed. It does not enforce broker rules — that's a Compliance pack. See Checklists.

EVE. Realm's intelligence layer — your operating partner. EVE is one thing that shows up across many surfaces (chat, Insights, banners, Finish with EVE, inline tips). EVE reasons and proposes; you approve. It never changes a REALM behind your back, and it always cites its source. See Meet EVE.

Finish with EVE. A one-tap way to have EVE prepare the remaining steps on a REALM — draft updates, line up documents, suggest next actions — for you to review and approve. See Finish with EVE.

Governance type (self / external / native). Who holds compliance authority over your Workspace. Self — you govern yourself (a solo independent agent); no enforced broker review. External — your compliance authority lives outside Realm (e.g. a franchise's own system); advisory checklists. Native — Realm-managed compliance with full broker review and enforcement. It's a separate axis from compliance provider and workspace type.

Insights. EVE's read on what's happening — surfaced inline next to the work it's about (dashboard health, per-REALM panels, banners). Insights are ambient: they sit beside your data, not in a separate "AI" app. See Insights, banners & alerts.

Intake. The questions Realm asks about a property (well, septic, propane, HOA, solar, and so on). The answers drive conditional documents and tasks — answer "yes, there's a well" and Realm adds the well-related requirements automatically. Brokers configure the question list in Brokerage Settings.

Key date. A specific date that matters on a REALM — inspection deadline, financing contingency, appraisal, closing. Key dates power reminders and show up on your milestones and calendar.

Lead. A potential client who hasn't yet become a transaction. A lead starts as a contact, moves through your pipeline, and becomes a REALM when it goes under contract. See Leads.

Lead bucket. A named group of leads with agents or teams assigned to it, used to organize and route leads (for example, "Zillow buyers" routed to a specific team). See Leads.

Marketplace. Where you browse and add ready-made Modules — Transaction Templates, packs, and other building blocks you can drop into your Workspace instead of building from scratch. See Modules & the Marketplace.

Milestone. A meaningful stage or checkpoint in a transaction (e.g. under contract, inspection complete, clear to close). Milestones and key dates give a REALM its timeline. See Milestones & key dates.

MLS connection. The link between Realm and your Multiple Listing Service, set up per agent under Settings → MLS. You sign in through the MLS's own login (Spark / Flexmls) — Realm never stores your MLS password. Connecting lets Realm search the market and surface From your MLS feed (the listings your MLS attributes to you). See Connecting your MLS.

Module. A reusable building block you can add to your Workspace — a Transaction Template, a pack, or similar — often sourced from the Marketplace. See Modules & the Marketplace.

Office. A branch/location of a brokerage, each with a designated broker and its own agents and REALMS. Offices are a coarser grouping above teams — one office can contain several teams — and let brokers filter compliance and reporting by location. See Offices.

People / Contact. A person in your address book — a client, a lead, a co-op agent, a vendor. Contacts own their own consents, which is why a buyer's BBA follows them across every REALM. See People.

Pipeline. Your view of leads and transactions as they move from first contact toward closing. The pipeline is the People → Leads → REALM lifecycle made visible. See Pipeline.

Position. A member's job in the brokerage — Agent, Team Lead, Broker, Transaction Coordinator, Assistant. One per member. It sets the ordinary surfaces they see and how far across the brokerage they can look. Extra access comes from an Access Role, never from stretching the Position.

Properties. The surface for working with homes on the market — search the MLS, build a working list, share homes with clients (Listings), and track favorited/watched homes (Saved). Fed by your MLS connection. See Properties overview.

REALM. The container — one piece of business, end to end. It holds your client, the property once there is one, the documents and signatures, the compliance file, the milestones and key dates, the tasks, and the Room the other side is invited into. It is the object you have many of. A REALM may start as a placeholder with no property yet, named for your client, with the address added later — which is the clearest reason it is not called a "transaction": there is no transaction in it yet. A REALM is not a Workspace (your org) — see Workspace — and it is not the transaction itself, which is the process that happens inside it. See REALMS.

Room. The shared space inside a REALM: your client, the co-op agent, the lender, and title or escrow, in one conversation over one set of facts — plus video, audio and screen share. Guests need no account and never pay. A REALM can run for weeks without a Room, and opening one is a deliberate step, so the Rooms list is shorter than your REALMS list by design. The Room is a feature inside the container, not a second object. See Meetings in the Room.

Stage gate. A rule that blocks a REALM from advancing to the next stage until certain conditions are met (e.g. required documents present, broker review cleared). Stage gates are part of the governance layer. See Compliance overview.

Starter role. One of the four Access Roles Realm builds into a new brokerage (Full Admin, Office Manager, Compliance Coordinator, Marketing Coordinator). Yours to rename, edit or delete; a deleted starter does not come back.

Task list (task pack). The set of tasks Realm creates automatically once a REALM goes under contract: a transaction-coordinator-grade plan, editable per side you represent. Stored as a task pack. Often bundled into a Transaction Template.

Team. A named group of agents under a team lead, used for routing, reporting, and commission defaults. A team role describes someone's place on the team and is separate from their Workspace role and their role in any one REALM. See Teams.

Transaction. Lowercase, and a common noun, not an object: the process that happens inside a REALM — the offer, the contract, the inspection, the close. You say "this transaction is under contract" about the work and "open the REALM" about the thing that holds it. The word is still capitalized as a modifier in the names of real surfaces: Transaction Template, Transaction Coordinator, Transaction Settings. See REALMS.

Transaction Template. A reusable transaction blueprint that bundles the documents a REALM requires (Document packs), the tasks it creates (Task lists), the intake questions it asks, and the compliance rules it enforces (Compliance packs) — all in one thing you apply to a REALM. See What is a Transaction Template.

Vault. The secure, tamper-evident archive for completed REALMS. When a REALM is done and review-cleared, you vault it — sealing its documents and communications into a permanent, verifiable record. See Vault overview.

Working list. Your running shortlist of listings for a buyer, built as you search Properties. It's saved in your browser so it survives closing the tab, and you can share the whole set with a client. See Searching listings.

Workspace. Your organization container — Personal, Team, or Brokerage. A Workspace holds your members, billing, integrations, and settings, and it contains many REALMS. You can belong to several Workspaces and switch between them. A Workspace is not a REALM: the Workspace is the org; a REALM is one property, one buyer or seller, inside it. See Workspaces & switching.

Workspace type (Personal / Team / Brokerage). What kind of collaboration your Workspace is built for. Personal — a solo agent. Team — a small group sharing a pipeline. Brokerage — a brokerage with multiple agents, offices, and broker oversight. It's a separate axis from your governance type and compliance provider.