> ## Documentation Index
> Fetch the complete documentation index at: https://docs.writerzroom.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Templates

> Schema-driven production workflows that define inputs, structure, and validation.

A WriterzRoom template is an executable content contract. It defines structured inputs, section order, writer instructions, research requirements, validation rules, and output policy for the agent pipeline.

<Info>
  The catalog count is loaded from the active backend configuration. Documentation does not hard-code a template total because YAML templates can be deployed independently.
</Info>

## Using the template catalog

<CardGroup cols={2}>
  <Card title="Use in Studio" icon="zap">
    Opens Studio with the selected template preloaded, then retrieves the full parameter schema before execution.
  </Card>

  <Card title="Preview" icon="eye">
    Shows the template purpose, complexity, estimated execution time, and available structured inputs.
  </Card>

  <Card title="Category filters" icon="filter">
    Separate Content, Marketing, Business, Technical, Academic, Entertainment, Communications, Financial, Legal, Compliance, Operations, and General workflows.
  </Card>

  <Card title="Responsive catalog" icon="layout-grid">
    Cards use one to four columns based on available width so titles, descriptions, and actions remain readable.
  </Card>
</CardGroup>

## Template schema

Each template can define:

| Contract area       | Purpose                                                    |
| ------------------- | ---------------------------------------------------------- |
| Inputs              | Required and optional production-brief fields              |
| Sections            | Ordered output structure and required deliverables         |
| Writer instructions | Template-specific drafting rules                           |
| Research policy     | Evidence, citation, and source requirements                |
| Validation rules    | Structural, quality, and compliance checks                 |
| Tier limits         | Whether Quick, Standard, or Premium execution is permitted |
| Output policy       | Formatting, length, and publication constraints            |

Supported field types include text, textarea, select, multiselect, checkbox, number, range, date, combobox, and file upload.

## Major workflow groups

### Content and communications

Blog articles, email newsletters, press releases, op-eds, investigative articles, social campaigns, and crisis communications.

### Business and operations

Business proposals, strategic briefs, executive decision briefs, quarterly business reviews, standard operating procedures, product requirements, onboarding guides, and change-management plans.

### Technical and analytical

API documentation, technical documentation, data-driven reports, market analysis, data-quality assessments, incident postmortems, and risk assessments.

### Academic, healthcare, legal, and compliance

Research papers, grant applications, clinical case studies, legal analysis, HIPAA briefs, healthcare regulatory risk memos, clinical AI governance policies, and FDA strategy memos.

### Creative and campaign production

Feature screenplays, television pilots, series bibles, short-form video scripts, campaign briefs, song lyrics, poetry collections, and resumes.

## Template and style compatibility

Templates and style profiles are separate controls. The template defines **what must be produced**; the style profile defines **how it should read**.

Studio provides three match scopes:

| Scope       | Meaning                                                          |
| ----------- | ---------------------------------------------------------------- |
| Recommended | Highest-scoring combinations defined by the compatibility matrix |
| Compatible  | Additional combinations approved for the template                |
| All         | Every style profile permitted by the selected vertical           |

When a template identifier has no explicit recommendation entry, Studio should still expose the permitted style catalog instead of presenting a false configuration failure.

## Vertical filtering

Selecting an industry vertical can restrict both templates and style profiles. These restrictions come from the active vertical configuration, not client-side assumptions.

<Warning>
  WriterzRoom fails closed when a vertical's constraints cannot be validated. It does not silently bypass a missing template or style restriction.
</Warning>

## File upload support

Templates that expose a file-upload field can accept PDF, DOCX, XLSX, CSV, JSON, TXT, and Markdown inputs up to the configured size limit. The parsing workflow extracts reference text into the generation context.

<Info>
  Uploaded source material is treated as grounding context and is not reproduced verbatim by default.
</Info>

## Choosing the correct template

<Steps>
  <Step title="Identify the deliverable">
    Choose the final format, not merely the topic. A press release, executive brief, and article about the same announcement are separate workflows.
  </Step>

  <Step title="Review required inputs">
    Preview the template to confirm that its structured fields match the information available.
  </Step>

  <Step title="Select the execution depth">
    Confirm that the intended Quick, Standard, or Premium tier is permitted by the template.
  </Step>

  <Step title="Choose a compatible style">
    Use Recommended for the highest-confidence match, Compatible for more flexibility, or All when broader voice options are appropriate.
  </Step>
</Steps>