> For the complete documentation index, see [llms.txt](https://oodlz-ai-studio.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://oodlz-ai-studio.gitbook.io/docs/outbound-agents/awareness/3-repurpose/intelligent-scheduling.md).

# Intelligent Scheduling

Approved articles auto-schedule to the next available Mon/Wed/Fri slot at 9am — never double-books, batch-approvals queue cleanly, WordPress and the workspace stay in sync.

> **Approve in the workspace, the article schedules itself — Mon/Wed/Fri at 9am, no double-booking, batch-approvals queue cleanly.**

Manual scheduling is where content pipelines break. The article gets written, the human approves, the human opens WordPress, the human picks a slot, the human checks if any other slot is taken, the human updates the workspace to match. Multiplied across 4 articles a week, that is hours of clerical work and constant double-booking risk. The Oodlz Repurpose producer schedules every approved article automatically.

## How It Works

When an article is marked as Approved in the workspace, the scheduling sequence fires. The producer queries WordPress for the most recent scheduled post and reads its publication slot. From that slot, it calculates the next available Mon/Wed/Fri at 9am — skipping any slot already taken.

The article's WordPress post is set to publish on the calculated date. The workspace article record is marked as Scheduled with the schedule date filled in. Both systems are now in sync.

When multiple articles are approved at once, each one runs the same lookup sequentially. The first approved article picks the next available slot; the second picks the slot after that; and so on. Batch approvals queue without conflict.

## What You Get

* Auto-scheduling on approval — no human picks slots, no double-booking, no clerical risk.
* Mon/Wed/Fri at 9am cadence — predictable publishing rhythm without manual maintenance.
* Existing schedule respected — the producer reads what's already queued before placing a new article.
* Batch approvals queue cleanly — approve 5 articles at once, they schedule into the next 5 available slots in order.
* Workspace and WordPress stay in sync — the scheduled date and status always match the actual WordPress queue.