Autopilot and work controls
Choose your level of control without losing the research and quality checks.
Autopilot is a publishing policy layered on top of research, monitoring and writing. You can automate the work while keeping final publication under your control.
Review first or autopilot
| Policy | What happens |
|---|---|
| Review first | Articles are prepared for you to review and approve |
| Autopilot | Eligible, checked articles can be delivered on schedule under your saved publishing policy |
| No publishing destination | Articles stay as drafts in your workspace |
The destination mode is a separate setting. Draft saves a draft in the connected CMS. Publish makes eligible content live through that destination.
Turn it on deliberately
- Connect and test your publishing destination.
- Open Plan → Schedule and publishing.
- Confirm the destination, draft/live mode, posting pace and timezone.
- Choose review-first or automatic publishing.
- Check the first delivery and its receipt before relying on the schedule.
Autopilot does not skip source checks, approve unsupported claims or override a pause.
Separate work controls
Research finds and reassesses opportunities. Monitoring refreshes visibility. Preparation researches and writes scheduled articles. Publishing delivers eligible articles.
These channels have separate controls. A global pause takes precedence over them. Pausing publishing does not remove pages already live. A request that has already been sent may still finish.
What continues over time
Research revisits the business's opportunities and existing coverage. Preparation fills eligible upcoming slots. Monitoring preserves a stable comparison baseline while exploring relevant new prompts. Available search and publication evidence can influence future priorities.
The system is designed to keep working without a manual refresh routine. It is not a promise of a new topic every day, immediate results for every prompt or uninterrupted availability from every outside website.
What needs your attention
Review held claims, reconnect expired integrations and resolve ambiguous deliveries before trying again. When a CMS may already have received an article, repeated clicks can create duplicates outside outwrite.ai. Follow the saved delivery state instead.
