This is the same guide agents use inside Raven.Get RavenLog in
The Complete Guide

The Raven Guide

Everything Raven 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.

99Chapters
15Product areas

Checklists

A checklist is a reusable list of the documents a transaction requires. Add one to a REALM and its documents fill in 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 see older material call these Document Packs, doc packs or requirement packs. It is the same thing: the product name changed to "Checklist" on 2026-10-02, because that is the word brokers use and the word SkySlope, Lone Wolf Transact, Brokermint and KW Command use. The code and the database still call them packs (requirement_packs).

Where you find them

  • Brokerage Settings, Transaction Settings, Checklists is where a broker builds and edits the checklist templates (+ New checklist, Build with EVE, Set as default).
  • On a REALM, the Checklists control on the Documents card lists the checklists that match the transaction. Pick one to add its documents to the REALM; Create custom checklist lets you pick documents by hand and save the selection as your own checklist.
  • The REALM's own Checklist tab is the list of documents that one transaction needs. The checklists above are where its rows come from.

How they work

  • A checklist 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 checklists come from

  • Automatically: when a REALM is created, Realm resolves the best matching default checklist for the side, state, and your brokerage and adds it.
  • From a REALM Template: a REALM Template attaches the checklists it needs as part of setting up the transaction.
  • Built by your brokerage: brokers and admins can build org-specific checklists, and EVE can draft a starter checklist for you to refine.

Checklists vs. Compliance packs

This is the distinction to get right:

ChecklistCompliance pack
What it isThe list of documents a transaction needsThe rules and gates that govern it
Lives whereThe REALM's Documents cardYour 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 checklist tells you what documents to gather; a Compliance pack tells the platform what rules to enforce. For the rules side, see Compliance packs.