Social Schedule Collision Review

How to use Social Schedule Collision Review

Inspect an entered multi-account content schedule before a human approves it. Compare actual UTC instants and explicit customer policies without publishing posts or inventing platform limits.

1. Enter the customer’s actual minimum posting gap, asset-reuse window and cross-account reuse scope.
2. List proposed posts with neutral platform/account IDs, explicit-offset timestamps, asset references and reviewed authorization states.
3. Resolve the named collision/reuse pairs and permission unknowns before manually approving the real schedule; export the full review.

Good to know

• A separation strictly shorter than the entered gap/window is flagged; an exact boundary is allowed. Same-account means both platform and account match.
• No platform calendar, legal restriction, audience outcome or actual account authorization is verified; no post or message is sent.
• Exact displayed CSV headers; at most100 data rows and8,000 UTF-16 characters per input. Plain decimals have at most9 fractional places; display rounds half-up to12 places. Unknown evidence stays unknown. CSV exports preserve summaries, settings, every calculated detail/finding, limitations and scoped input records; spreadsheet-like text is apostrophe-prefixed.
• Browser-local supplied-record review. No AI, network requests, provider connection, file upload, stored input or automatic delivery. Use neutral identifiers instead of personal information or secrets.