Blocks

Create and maintain reusable checklist templates: kinds, items, per-language labels, and how edits affect future cases.

Blocks are reusable checklist templates. Instead of picking documents one by one for every case, you compose from blocks — "Core documents", "Salaried employee", "Rental investment" — and get a consistent, complete checklist in seconds.

The four kinds

When you compose a case, blocks behave according to their kind:

KindBehavior in the composer
CoreAlways included in every case
ProfileChoose exactly one, matching the client's situation
Add-onsAdd any number, as the case requires
CustomHolds one-off document types added to the registry

A typical setup: one Core block with the documents every file needs (ID, tax returns), one Profile block per client situation (salaried, self-employed, retired), and Add-on blocks for extras (rental investment, divorce, co-borrower).

Creating a block

On the Blocks tab of the Document library, create a block with:

FieldPurpose
Namee.g. "Salaried employee"
Profile tagOptional — marks the block as a Profile choice
DescriptionOptional context for your team
Intro video URLOptional — shown to the client at the top of this block's section

Managing items

Open a block's detail page to add, edit, or delete its items. Each item carries:

  • Key — the stable identifier from the registry
  • Label and description per language (EN/FR/PT) — clients see the version matching their preferred language
  • Helper video — an optional short explainer (e.g. "where to download your tax notice")
  • Required toggle — required items must be validated before a case can complete; optional items are nice-to-have

Note: Write labels from the client's point of view. "Last 3 payslips" beats "salary docs" — your clients are not mortgage professionals, and a clear label saves a follow-up call.

How edits affect cases

Blocks follow the library's frozen-labels rule:

  • Editing a block — renaming it, changing items, rewording labels — only affects cases composed after the change. Cases already sent keep the exact labels, descriptions, and videos they were composed with.
  • Deleting a block never touches already-composed cases either. Their checklists were frozen at compose time.

So you can iterate on your templates continuously: fix a confusing label today, and every case from tomorrow benefits, while nothing shifts under the feet of clients mid-collection.

Maintenance tips

  • Keep the Core block lean — every extra required document slows every single case down.
  • Use Profile blocks to capture situations, not exceptions. One-off needs belong in Add-ons or the Custom documents block.
  • Fill in all three languages as you go. A block with only French labels will read poorly for an English-speaking client.
  • Add helper videos for the documents clients most often get wrong — they pay for themselves in avoided rejections.