# Plan manual and automated social posts together

Keep community posts, newsletters and other manual destinations in the same Postdot calendar as your automated social publications.

URL: /features/manual-publishing

Some of the places you publish need a person to finish the job. A community may
expect you to submit a post yourself. A newsletter may have its own editor. You may
prefer to review a platform's final composer before sending anything.

Create a manual channel in Postdot and give that destination a place in your
publishing plan. It has content, media, a schedule and a completion state, alongside
the channels Postdot publishes to through an API.

## One announcement, several destinations [#one-announcement-several-destinations]

Suppose you are announcing a release. You want a LinkedIn post, a community submission
and a newsletter mention. Write the shared source post, then adapt the publication
for each destination. The community version can have its own explanation and link;
the newsletter can use different text and a later date.

Schedule the automated destination and the manual ones in the same calendar. You can
see what is planned and which publications still need your attention without keeping
a second spreadsheet for the destinations outside your API integrations.

## Finish the publication yourself [#finish-the-publication-yourself]

When a manual publication is due, open it in Postdot and use the prepared text and
media in the destination's own editor. After publishing, mark it complete in Postdot.
The queue then reflects the work you have done.

A manual channel sends nothing to the destination on its own. Its scheduled time
organizes the work you will carry out. That makes it useful both for destinations
without an integration and for places where you want to keep the final step manual.

## Use the same planning tools [#use-the-same-planning-tools]

Manual channels belong to the same project workflow as automated channels. You can
prepare their publications in Studio or have an agent create drafts through the
CLI, API or MCP. Review the content, adjust each destination and choose when it
should appear in your queue.

You decide whether a destination needs an automated connection. Adding it to your
plan does not require one.

## Try a manual channel [#try-a-manual-channel]

[Install Postdot](/docs/installation/), create a project and add a manual channel.
The [first-publication guide](/docs/first-publication/) walks through preparing,
reviewing and scheduling the content. For channel setup and project attachments,
see the [channel guide](/docs/channels/).

If you also prepare posts with an agent, read about
[agent publishing workflows](/features/agent-workflows/).

