# Bulk Scheduling Slot Conflict Check

Review a bulk schedule for two posts placed in the same slot before it is confirmed.

## Scope
Preparation and review only. No account action or professional decision.

## Inputs
Post list with planned dates, times, timezones and platforms.

## Workflow
1. List every planned slot per platform.
2. Flag two posts assigned the same platform, date and time.
3. Separate same-slot conflicts from intentional cross-platform matching times.
4. Return the conflict list without scheduling or moving posts.

## Output contract
post | platform | slot | conflict_with | intentional_pair | schedule_unproved

## Fictional acceptance test
Fictional plan places posts A and B on the same platform at 09:00 Monday. One platform accepts one post per slot here, so confirming both would leave one unscheduled; the matching 09:00 on a second platform is intentional, not a conflict.

## Review gates
Keep original values, source IDs and version dates. Unknown facts stay held. Use qualified review for hiring, legal and accounting conclusions. No send, share, sign-in, scheduling, ledger change or payment. Fictional contract review is not a live account compatibility test.

## Method source
https://help.planable.io/hc/en-us/articles/21715370386844-Guidelines-for-Scheduling-Posts-Across-Multiple-Platforms-in-Planable

Checked October 17, 2026. Oct17 live AIS Search Console (sc-domain property, tej@groweasy.ai, Saturday audit): Oct 9-15 complete week 22 clicks, 937 impressions, 2.3% CTR, position 10.6, day-row verified. Top queries: Muse India 125i (3-month), Planable/Claude social agent 45i, marketing Copilot 37i, Planable/ChatGPT 24i, investor agents 19i, Copilot investment-committee 14i, cash flow forecasting 13i, campaign brief 12i. Google Trends verified Oct 17: muse glimmer/spark rising. Site impressions are query leads, not monthly volumes; exact topic volume is unmeasured.