> ## 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.

# Content Requests

> Structured intake from stakeholders and clients before a generation is run against it.

**Content Requests**, under Intelligence in the sidebar, captures what a piece of content needs to accomplish — objective, audience, channel, deadline, and priority — as a structured record before anyone opens [Studio](/product/generation-workspace) against it.

<Note>
  A request is an intake and triage record. Approving a request does not itself start a generation — a team member still opens Studio to act on it.
</Note>

## Request Fields

Each request carries a title, an objective, an optional audience and channel, an optional deadline, a priority (`low`, `normal`, `high`, `urgent`), and who requested it.

## Status Flow

Requests move forward in order: `submitted` → `in_review` → `approved` → `in_progress` → `completed`. A request can be rejected from any state prior to completion instead of advancing. The queue sorts by priority within whatever status filter is active, and separately tracks:

* **Open** — submitted or in review
* **Active** — approved or in progress
* **Overdue** — past its deadline and not yet completed or rejected

<CardGroup cols={2}>
  <Card title="Studio" icon="sparkles" href="/product/generation-workspace">
    Where an approved request is actually turned into content.
  </Card>

  <Card title="Regulatory Radar" icon="radar" href="/product/regulatory-radar">
    Log a request to update content in response to a regulatory change.
  </Card>
</CardGroup>