Skip to main content
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 against it.
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.

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: submittedin_reviewapprovedin_progresscompleted. 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

Studio

Where an approved request is actually turned into content.

Regulatory Radar

Log a request to update content in response to a regulatory change.
Last modified on August 30, 2026