Klarum

Templates and Checklist Templates

Generally available
Supplier
From basic

Two org-owned template systems: a document section tree with typed variable slots that drives generation, and role-based checklist templates that seed every new workspace with a starting task list.

Catalogue id
templates

Description

What it is

Two related template systems, both firm-owned reusable scaffolding:

  1. Document templates: a section tree (the skeleton of an EOI, technical proposal, inception report, compliance pack, comms letter) plus typed variable slots declaring where each piece of firm context inserts at generation time. Standard (platform-shipped, read-only, org_id IS NULL) and Custom (forked by the firm). Persisted to the consolidated doc_templates substrate (doc_template_sections flat parent_id tree, doc_template_variables slots).
  2. Checklist templates (firm settings): a firm-wide, role-based checklist whose items seed every new workspace with a starting task list. Each carries a scope: manual, issuer (auto-suggest when a workspace's issuer matches), or staffing (criteria-matching, matcher not yet wired).

What it helps users do

Standardise proposal/EOI output (define the house structure once); fork-and-customise from platform defaults (preserving meta.forked_from provenance); bind a template to a workspace and generate a DOCX/PDF; enforce a consistent bid-readiness checklist; auto-suggest the right checklist per opportunity; and snapshot a good workspace into a reusable template ("Save items as template", #1076).

Capabilities

  • Section tree and variable slots

    Generally available

    A hierarchical section skeleton with per-section generation prompts and typed variable slots declaring where each piece of org context inserts at generation time.

  • Fork with provenance

    Generally available

    An org forks a platform-shipped Standard template into a Custom one and the fork records meta.forked_from, so a customisation can always be traced back to its origin.

  • Checklist seeding and Apply template

    Generally available

    A default checklist is provisioned idempotently per org and copied once into each new workspace; the Apply picker is one relevance-ranked SQL query over issuer-matched, default and manual buckets.

  • Staffing-scope checklists

    Planned

    Checklist templates can declare a staffing scope for criteria matching. The scope is scaffolded and stored; the matcher behind it is not yet wired.

Keywords

templates, sections, variables, checklist, proposals, jinja2, fork

Provenance

This page renders a published artifact. Read the same records as JSON if you would rather check the source than the page.