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

# Post scheduling and calendar

> Schedule approved posts for future publishing and review timing from post and campaign workflows.

Scheduling lets you approve a post now and publish it later.

## Schedule from chat

Ask for a date, time, and target platform.

```text theme={null}
/post Schedule this LinkedIn and Instagram post for next Tuesday at 10 AM Eastern.
```

daoco prepares the post, shows a preview, and asks for approval before scheduling.

## Schedule from Create Posts

<Steps>
  <Step title="Prepare the post">
    Create or open the post you want to schedule.
  </Step>

  <Step title="Choose accounts">
    Confirm the connected accounts and platform variants.
  </Step>

  <Step title="Set date and time">
    Choose the schedule time in the workflow.
  </Step>

  <Step title="Approve">
    Confirm the scheduled publish action.
  </Step>
</Steps>

## Scheduling checks

* Use a specific timezone when timing matters.
* Check platform limits before scheduling mixed media, multi-account posts, or per-platform variants.
* Review scheduled posts in **Manage Posts**.
* Use campaign calendars for launch planning across multiple posts.
* Campaign and post calendars place published and scheduled items more consistently across day, week, and campaign views.
* On mobile, use the compact calendar pills to open the post details instead of relying on full post text inside each month cell.
* If a scheduled publish fails because a social connection expired, reconnect the account from **Connections** and review the post in **Manage Posts**. daoco keeps scheduled delivery state clearer after publish, failure, or reconnect.

## Mixed schedules

If a multi-platform post has variants scheduled for different times, review the schedule details in the inspector before approving. daoco groups related variants together, but each delivery can still have its own platform-specific requirements and timing.