# Plan the next shift

Prepare a visible sequence of content before the operator goes offline.

State: Private pilot · Updated September 18, 2026

## Add a content commitment

1. **Open the content plan.** Choose a saved project and find Keep the next shift covered. Expand Add a content commitment.

2. **Set the content and time.** Enter a title, a planned time in your browser’s timezone, and a draft caption.

3. **Attach a finished image.** Select a delivered image from the same project. A complete commitment has both a caption and an image.

4. **Save and inspect.** Save the commitment, then open Preview investor view to inspect its visible preparation state.

[Open the content plan](/operations#content-plan)

## A plan is a sequence of states

| State | Evidence |
| --- | --- |
| Planned | A saved commitment; the asset or caption may be missing. |
| Asset prepared | A finished image and caption are attached to a future commitment. |
| Time passed · unposted | The planned time passed without a verified publication. |
| Cancelled | The commitment is retained but no longer counted as upcoming. |
| Scheduled / Published | Require a publishing integration and confirmation. Unavailable in this pilot. |

> **Preparation is not publication.** A future time is a commitment, not a queued social post. Saving an image or a caption does not authorize or perform external posting.

## Check coverage before going offline

The next-eight-hours count includes future, uncancelled commitments with a caption and a finished image. If there are none, the studio shows an in-app preparation warning.

This is a count of prepared items, not a promise of continuous posting coverage. There are no push notifications or email reminders. Check the planned timezone and review each item before relying on the plan.

## Change a commitment

Use Cancel to retire an existing commitment, then add a replacement with the corrected time or content. The cancelled record stays visible. Refresh plan to load current records after working in another tab.

[Set a fallback policy](/docs/continuity)
