# Run a weekly content calendar (/use-cases/content/content-calendar)



Copy this prompt to start your first task:

<Prompt>
  Set up an automation that plans and drafts our recurring content calendar — spread topics and formats over the next few weeks so nothing clusters into one week, draft each piece when it's due, and post drafts to [channel] for review before anything goes further.
</Prompt>

<LivePreview component="NewThread" scenario="{ draft: &#x22;Set up an automation that plans and drafts our recurring content calendar — spread topics and formats over the next few weeks so nothing clusters into one week, draft each piece when it's due, and post drafts to [channel] for review before anything goes further.&#x22; }" />

## What is this workflow? [#what-is-this-workflow]

"Run a weekly content calendar" turns a recurring planning chore into something a content teammate owns end to end, instead of you asking fresh every week. Given your marketing goals, it builds a schedule of topics, formats, and target dates, spreading pieces so nothing clusters into one week, then drafts the first version of each piece when it's due and posts it to your channel for review. Over time it proposes memories about your voice and preferences, and applies the ones you accept to every new draft without being reminded.

**Nothing here needs your approval:** planning the calendar, drafting each piece, and posting drafts to your channel all happen inside Helio, so this automation runs on its own end to end. See [Control](/ai-teammates/control) for what does pause for sign-off.

## How to use this workflow [#how-to-use-this-workflow]

<Steps>
  <Step>
    ### Hire a content teammate [#hire-a-content-teammate]

    Open **AI Teammates** in the sidebar, click **Hire AI Teammate**, and pick the **Content Writer** template. The default bio is generic long-form writing. Replace it on the Profile step so it knows this job is owning a recurring content calendar end to end:

    <Prompt>
      You plan and draft a recurring content calendar end to end instead of being asked fresh each week. Given marketing goals, build a schedule of topics, formats, and target dates, spreading pieces so nothing clusters in one week, then draft the first version of each piece when it's due. Post drafts to #content for review before anything goes further, and apply the voice and preferences you've learned over time to every new draft.
    </Prompt>

    Confirm the name and click **Create teammate**. They land in their own channel, which is where you'll send everything below. The bio has drafts going to `#content`, and a teammate can only post in channels it's a member of — add this teammate to `#content` (create it if it doesn't exist yet) before the first calendar goes up. [More on hiring →](/ai-teammates/hire-an-ai-teammate)

    <LivePreview component="CreateAssistantPage" scenario="{ focus: &#x22;profile&#x22;, initialState: { start: &#x22;template&#x22;, templateRef: &#x22;@helio/content-writer&#x22;, name: &#x22;Content Writer&#x22;, bio: &#x22;You plan and draft a recurring content calendar end to end instead of being asked fresh each week. Given marketing goals, build a schedule of topics, formats, and target dates, spreading pieces so nothing clusters in one week, then draft the first version of each piece when it's due. Post drafts to #content for review before anything goes further, and apply the voice and preferences you've learned over time to every new draft.&#x22; } }" />
  </Step>

  <Step>
    ### Plan the first calendar together [#plan-the-first-calendar-together]

    <Prompt>
      Plan the next 4 weeks of content based on our marketing goals: [e.g., a few blog posts, a couple of customer case studies, a weekly recap]. Draft a calendar with topics, formats, and target dates, and post it to #content for review.
    </Prompt>

    <LivePreview
      component="AssistantChat"
      scenario="{ assistantName: &#x22;Content Writer&#x22;, messages: [
    { author: &#x22;user&#x22;, text: &#x22;Plan the next 4 weeks of content based on our marketing goals: 3 blog posts on the new API, 2 customer case studies, weekly changelog recaps. Draft a calendar with topics, formats, and target dates, and post it to #content for review.&#x22; },
    { author: &#x22;assistant&#x22;, text: &#x22;Got it. That's 3 blog posts, 2 case studies, and weekly changelog recaps across 4 weeks. I'll spread them so nothing clusters in one week, tag each with a target date and format, and post the draft to #content for review before anything goes further.&#x22; },
  ] }"
    />
  </Step>

  <Step>
    ### Turn the recurring parts into an automation [#turn-the-recurring-parts-into-an-automation]

    Once you're happy with the cadence, open **Automations** in the sidebar, click **Create via Chat**, and pick this teammate in the New Thread composer that opens instead of asking each week:

    <Prompt>
      Every Monday morning, check the content calendar for what's due this week, draft the first version of each piece, and post drafts to #content for review.
    </Prompt>

    <LivePreview component="NewThread" scenario="{ populated: false }" />
  </Step>

  <Step>
    ### Let memory carry your brand voice forward [#let-memory-carry-your-brand-voice-forward]

    As your teammate works through more pieces, it proposes memories about your voice and preferences. Accept the ones that are right and it applies them to every future draft without being reminded. [Memory →](/ai-teammates/memory)
  </Step>
</Steps>

## Tips for Better Results [#tips-for-better-results]

| Tip                                                         | Description                                                                                                                                            |
| ----------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Give clear marketing goals up front                         | The teammate spreads topics, formats, and dates across the schedule based on what you tell it — vague goals produce a generic calendar it has to redo. |
| Review the first calendar before automating it              | Confirm the cadence and topics you want in the one-off run, then turn the recurring check into an automation once you're happy with it.                |
| Add the teammate to #content before the first draft goes up | It can only post in channels it's a member of, so add it to #content (or wherever drafts should land) before the first calendar goes out.              |
| Accept the memory prompts that match your voice             | Confirming the right ones is what lets every future draft apply your voice and preferences without being reminded.                                     |

## Common Questions [#common-questions]

<Accordions type="single">
  <Accordion title="Does this replace me reviewing content?">
    No. Every draft posts to your channel for review before anything goes further — the automation drafts, it doesn't publish on your behalf.
  </Accordion>

  <Accordion title="Can the automation post drafts anywhere?">
    No. A teammate can only post in channels it's a member of. Add it to #content (or wherever you want drafts to land) before the first calendar goes up.
  </Accordion>

  <Accordion title="Does it apply my brand voice automatically?">
    It proposes memories about your voice and preferences as it works through more pieces. Accept the ones that are right and it applies them to every future draft without being reminded.
  </Accordion>

  <Accordion title="Does this need my approval to run each week?">
    No. Planning, drafting, and posting drafts to your channel all happen inside Helio, so the automation runs on its own once it's set up.
  </Accordion>
</Accordions>

<Cards>
  <Card title="Content" href="/use-cases/content" description="Back to the content use case overview." />

  <Card title="Translate content in bulk" href="/use-cases/content/translation-and-localization" description="Keep terminology consistent across a full translation batch." />
</Cards>