{"id":"templates","type":"module","title":"Templates and Checklist Templates","status":"ga","audience":["org-admin","bid-manager"],"scope":"supplier","tier_min":"basic","aliases":["9","doc-templates","checklists"],"summary":"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.","keywords":["templates","sections","variables","checklist","proposals","jinja2","fork"],"body":{"what_it_is":"Two related template systems, both firm-owned reusable scaffolding:\n\n1. **Document templates**: a **section tree** (the\n   skeleton of an EOI, technical proposal, inception report, compliance pack,\n   comms letter) plus typed **variable slots** declaring *where* each piece\n   of firm context inserts at generation time. **Standard**\n   (platform-shipped, read-only, `org_id IS NULL`) and **Custom** (forked by\n   the firm). Persisted to the consolidated `doc_templates` substrate\n   (`doc_template_sections` flat parent_id tree, `doc_template_variables`\n   slots).\n2. **Checklist templates** (firm settings): a firm-wide, role-based checklist\n   whose items seed every new workspace with a starting task list. Each\n   carries a **scope**: `manual`, `issuer` (auto-suggest when a workspace's\n   issuer matches), or `staffing` (criteria-matching, matcher not yet wired).\n","what_it_helps_users_do":"Standardise proposal/EOI output (define the house structure once);\nfork-and-customise from platform defaults (preserving `meta.forked_from`\nprovenance); bind a template to a workspace and generate a DOCX/PDF; enforce\na consistent bid-readiness checklist; auto-suggest the right checklist per\nopportunity; and snapshot a good workspace into a reusable template (\"Save\nitems as template\", #1076).\n"},"engines":[],"integrations":[],"capabilities":[{"id":"document-section-tree","type":"capability","title":"Section tree and variable slots","summary":"A hierarchical section skeleton with per-section generation prompts and typed variable slots declaring where each piece of org context inserts at generation time.","status":"ga","scope":null,"keywords":["sections","slots","default-source","grounding"],"body":null},{"id":"template-fork-provenance","type":"capability","title":"Fork with provenance","summary":"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.","status":"ga","scope":null,"keywords":["fork","provenance","standard","custom"],"body":null},{"id":"checklist-seeding","type":"capability","title":"Checklist seeding and Apply template","summary":"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.","status":"ga","scope":null,"keywords":["seeding","relevance-buckets","idempotent"],"body":null},{"id":"staffing-scope","type":"capability","title":"Staffing-scope checklists","summary":"Checklist templates can declare a staffing scope for criteria matching. The scope is scaffolded and stored; the matcher behind it is not yet wired.","status":"planned","scope":null,"keywords":["staffing","scaffolded","pending"],"body":null}]}