Templates

Standardize the starting point

flowchart LR
    Template[Template] --> Draft[Draft structure]
    Draft --> Reuse[Repeated reuse]

Templates give teams a controlled starting structure for repeated content and review-heavy workflows.

Separate the blueprint from the output

The value of a template is not finished content. It is the reusable structure, guidance, and ordering that helps downstream work start in a better place.

Use it where repeatability matters

Templates are most useful when:

• the same document or evidence shape appears repeatedly
• the team wants hydration or drafting to start from an approved pattern
• administrators want a small governed set of reusable structures instead of ad hoc setup

On the page

Section	Purpose	Typical content
Details	Classify the template	Title, type, category, applicability
Sections	Define the reusable structure	Ordered section groups, instructions, examples, writing guardrails
History and reuse	Keep downstream impact visible	Clone, update, compare, restore, downstream consumption

What teams maintain

Templates are structured authoring blueprints. The team usually maintains:

• template identity and applicability
• ordered section groups
• instructions and examples that shape downstream writing

Reorder and nest sections safely

When section dragging is enabled, drag a section row to reorder it or drop it onto another row to make it that section’s last child. A move always carries the complete subtree, keeps sibling numbering contiguous, and is rejected when it would create a cycle or exceed the template’s nesting limit.

The section action menu provides the same move, indent, and outdent controls without requiring pointer dragging. This is the keyboard-accessible fallback and remains available when dragging is disabled.

Deleting a section with descendants requires confirmation. The confirmation reports how many nested sections will also be removed, and cancellation leaves the complete hierarchy unchanged.

Import templates without creating sprawl

Each uploaded template file represents one template:

• A complete template JSON export keeps its template details and section hierarchy.
• A JSON export of sectionGroups creates one document template, names it from the file, and places every exported group under that template’s Sections.
• Multiple JSON or Word files create one template per file.
• Importing JSON from inside an existing template replaces that template’s section groups instead of creating more templates.

Keep the set governed

The main failure mode is template sprawl. Teams should prefer a deliberate, reusable set of templates rather than many near-duplicates that dilute consistency.