Templates lifecycle

A template is reusable report structure for your workspace — Markdown body, field definitions, and placeholders for operational writeups.

Templates hold methodology and layout. They are not live client evidence by default.

WorkCheats stores and displays template content. It does not execute commands or scripts referenced in template bodies.

Active templates

Active templates appear in the Templates list and can be:

• Created and edited (Markdown source is the editor source of truth)
• Used as the starting point when you create a new report
• Exported as JSON, Markdown, or a WorkCheats Package (report_template item kind) where export policy allows
• Favorited for quick navigation — see Favorites

Template Studio supports Markdown editing with structure panels and preview. Preview helps you validate layout — it is not a separate WYSIWYG document editor.

Creating reports from templates

When you create a report from a template, WorkCheats snapshots the template structure at that moment:

• Existing reports keep their snapshotted structure even if you later edit the template
• Archived templates are not listed when creating a new report from template
• Reports retain source template provenance — a reference to the template they were created from

Source template provenance on reports

Reports created from a template may show where they came from:

Archiving a template does not archive or delete reports that already reference it. Those reports remain editable and exportable according to report rules unless the report itself is archived.

WorkCheats does not document template deletion cascade behaviour in user docs — treat archive as the supported retirement path.

Archive a template

When a template is no longer active:

1. Open the template.
2. Choose Archive.
3. The template is hidden from active template lists (archived_at soft archive).

After archive:

• The template cannot be edited like an active template — archive returns not found for update actions
• The template cannot be used to start new reports from the active template picker
• Existing reports that reference it remain available with non-link provenance labels
• Exports are blocked for archived templates (JSON, Markdown, and Package export paths)
• A template favorite shows Archived on the Favorites page and cannot be opened from there

Whether an archived template definition can be viewed outside active lists may vary — use report provenance labels for historical context.

Template fields and placeholders

Templates may define fields and {{placeholder}} tokens in Markdown. Fields compile into report structure when you create a report.

• Placeholder and field values you enter are user content — treat as untrusted until reviewed
• Do not store secrets (passwords, API keys, tokens) in template bodies unless your organisation explicitly allows it

Export behaviour

Template exports may contain sensitive operational structure. Share only with people cleared to receive them.

Export eligibility follows server policy and content provenance. Some Marketplace-installed template lineage may be export-restricted even after you edit content.

Related docs

• Templates & Reports — overview
• Reports lifecycle — report status, export, and evidence
• Security & Responsible Use — untrusted content and safe export