Document packs
A Document pack is a reusable bundle of the documents a transaction requires. Apply one to a Realm and its checklist fills with the right requirements — the purchase contract, disclosures, inspection forms, closing documents, and so on — instead of you building the list by hand on every transaction.
You may also hear these called requirement packs: they define the requirements (documents) a transaction needs.
How they work
- A pack is matched to the transaction by its facts — side (buyer or seller), state, and property type — so a buyer-side Realm in your state gets the right buyer documents automatically.
- Some items are conditional: they only appear when they apply (for example, an HOA addendum only when the property has an HOA).
- Some items can be marked blocking, meaning the Realm can't advance past a stage until they're satisfied — where your brokerage enforces compliance.
Where packs come from
- Automatically — when a Realm is created, Realm resolves the best matching pack for the side, state, and your brokerage and applies it.
- From a Transaction Template — a Transaction Template attaches the document pack it needs as part of setting up the transaction.
- Built by your brokerage — brokers and admins can build org-specific packs, and EVE can draft a starter pack for you to refine.
Document packs vs. Compliance packs
This is the distinction to get right:
| Document pack | Compliance pack | |
|---|---|---|
| What it is | The list of documents a transaction needs | The rules and gates that govern it |
| Lives where | The Realm's document checklist | Your brokerage's compliance settings |
| Answers | "What do I have to collect and sign?" | "What's allowed, and what blocks progress?" |
They're related but separate systems. A Document pack tells you what documents to gather; a Compliance pack tells the platform what rules to enforce. For the rules side, see Compliance packs.