Skip to content

Understanding Templates

This section is for administrators who set up and maintain templates. If you just use Certum Draft to generate documents, see Generating Documents.

A template in Certum Draft has two parts:

  1. Matter configuration (matter.json) — Defines the fields to collect from users
  2. Document templates (Word files) — The actual documents with placeholders

When someone creates a matter and generates documents, Certum Draft:

  • Collects information using the fields you define
  • Replaces placeholders in documents with that information

Each template type lives in its own folder within your Templates directory:

  • DirectoryTemplates/
    • DirectoryEstates/
      • matter.json
      • DirectoryPrecedents/
        • DirectoryLetters/
          • Letter to Beneficiary.docx
          • Letter to Bank.docx
        • DirectoryCourt/
          • Probate Application.docx
    • DirectoryConveyancing/
      • matter.json
      • DirectoryPrecedents/

This file defines:

  • What information to collect (fields)
  • How fields are organised (blocks/sections)
  • Which fields are required vs optional
  • The folder structure for new matters
  • Starter files to copy into new matters

Word documents (.docx) containing placeholders like {{ client.full_name }} that get replaced with actual values.

When a user creates a new matter:

  1. They see a list of all folders in your Templates directory
  2. Each folder with a valid matter.json appears as an option
  3. Selecting a template loads its fields and folder structure

Templates can share common fields. The matter.json file can include blocks for:

  • client — Standard client information (name, address, contact)
  • matter — Common matter fields (reference, dates)
  • Custom blocks — Specific to that practice area

This means you define client fields once and reuse them across all templates.