Applying a Transaction Template
Applying a Transaction Template to a transaction is what turns the blueprint into a working transaction: the right document requirements appear, the timeline fills in, reminders get scheduled, and Raven starts watching for gaps.
How to apply a Transaction Template
- Open the transaction.
- Find the Transaction Template Timeline panel next to Key Dates. If no Transaction Template is applied yet, you'll see an Apply Transaction Template picker (brokers and admins) listing your brokerage's published Transaction Templates.
- Pick the Transaction Template that matches the transaction (state, side, financing, property type) and apply it.
Raven also matches a Transaction Template automatically when you create a transaction or confirm its plan — it picks the best fit for the transaction and falls back to your brokerage default if nothing matches exactly.
What gets materialized
When a Transaction Template applies, it builds real things in the transaction:
- Document requirements — the requirements from each attached Compliance Pack, including any conditional ones (well, septic, HOA, solar, cash, and so on) that match the transaction's intake answers.
- Milestones and key dates — deadlines computed from anchor dates plus offsets (for example, BINSR due ten days after contract). They appear on the Transaction Template Timeline.
- Scheduled communications — reminders and messages land in a collapsed "Scheduled by Raven" group. Nothing auto-sends to clients unless your brokerage allows it; they're drafted for your review.
- Vault policy — when and how this transaction will be archived once it's complete.
Future reminders never crowd your "Needs You" list. They sit quietly under "Scheduled by Raven" and on the timeline until they're due.
The immutable snapshot
When you apply a Transaction Template, the transaction keeps a snapshot of exactly what was applied — the version, the packs, the milestones, the rules. If your broker later edits or republishes that Transaction Template, your transaction doesn't change. Active and closed transactions stay locked to the version they were created with. Upgrading a transaction to a newer Transaction Template version is always a deliberate choice, never automatic.
What you'll see afterward
- The Transaction Template chip in the transaction header (for example, "Arizona Buyer · v1").
- The Transaction Template Timeline with milestone status (complete, current, at risk, upcoming, overdue).
- Each document requirement shows the Compliance Pack it came from.
- Transaction Health reflects how complete the transaction is against the plan.
Applying, upgrading, or removing a Transaction Template is recorded in a permanent history — who did it, which Transaction Template and version, and when. Like every audit trail in Raven, it's append-only: nothing is quietly overwritten, so you can always answer "how did this transaction come to be set up this way."