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

# Beat Autopilot

> Set Beat to automatically draft content on a schedule.

Beat Autopilot is a background drafting engine. Enable it, configure your schedule, and Beat will generate article drafts on the days you've chosen — no prompting required. You review every draft before anything goes live.

## The most important thing to know

**Autopilot drafts. It never publishes.**

Every piece of content Autopilot generates lands in your Content Planner → Drafting column and waits for your review. Nothing goes live without your explicit approval. You stay in control of what publishes and when.

## How to enable Autopilot

<Steps>
  <Step title="Open Settings">
    Navigate to [/app/settings](https://useupbeat.com/app/settings) and click **Beat autopilot** in the section list.
  </Step>

  <Step title="Toggle Autopilot on">
    Flip the Autopilot switch to the enabled position.
  </Step>

  <Step title="Choose your days">
    Pick which of the three available days you want Beat to draft content. Pro picks any combination of **Monday, Wednesday, and/or Friday** — up to 3 days per week.
  </Step>

  <Step title="Save your settings">
    Click Save. Autopilot will run on its next scheduled day.
  </Step>
</Steps>

<Note>
  Autopilot is a **Pro-only** feature. Free and Starter accounts can't enable it. Pro picks up to 3 days per week from Mon / Wed / Fri.
</Note>

## Configuring your days

Pick the day(s) that align with your content calendar. A common pattern is Monday only — you start your week with a fresh draft to review. Picking all three (Mon / Wed / Fri) keeps a steady flow of drafts coming through without overwhelming your review queue.

## What gets drafted

On each Autopilot run, Beat drafts one article. It picks the topic by analyzing:

* Which content pillar is most underserved right now
* Open keyword opportunities from your SEO data (if GSC is connected)
* Your content calendar (Beat avoids topics you've recently covered)
* Your Brand Beat pillars, audience, and publishing frequency target

You don't set the topic manually — Beat selects it based on what will have the most strategic impact. If you want control over the topic, create content manually from Content Studio instead.

## Where drafts appear

When Autopilot runs, the new draft appears in:

* **Content Planner** at `/app/content` → **Drafting** column
* **Slack** (if you have Slack connected) — Beat sends a notification with the article title and a link to review it

Check your Content Planner on the days after your scheduled Autopilot days to review new drafts.

## How to review and approve an auto-draft

<Steps>
  <Step title="Open the draft">
    Go to `/app/content` and find the draft in the Drafting column. Click to open it in the article editor.
  </Step>

  <Step title="Review and edit">
    Read through the draft. Edit anything that needs to change — headline, sections, specific facts, or tone. Use Beat in the editor sidebar if you want help revising sections.
  </Step>

  <Step title="Move to Approved">
    When you're happy with the draft, change its status to Approved using the status picker in the editor sidebar.
  </Step>

  <Step title="Publish when ready">
    When you're ready to publish, click Publish and choose your destination (WordPress, save to pipeline, etc.).
  </Step>
</Steps>

## Turning Autopilot off

Go to Settings, scroll to the **Beat autopilot** section, and toggle Autopilot off. Beat will stop drafting on its next scheduled run. Any drafts already in your pipeline remain — turning off Autopilot doesn't delete anything.

## What's next?

<CardGroup cols={2}>
  <Card title="Content Pipeline" icon="kanban" href="/content/pipeline">
    Manage your auto-drafted content through review and approval stages.
  </Card>

  <Card title="Slack Integration" icon="slack" href="/integrations/slack">
    Get notified in Slack when Autopilot generates a new draft.
  </Card>
</CardGroup>