# Cross-Workspace Approval Queue Routing

Sort a combined social approval queue by client, reviewer and evidence without merging independent workspace rules.

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

## Inputs
Queue export; workspace IDs; client IDs; reviewer roster and stage permissions; status timestamps.

## Workflow
1. Group by stable workspace/client IDs before joining reviewer names.
2. Keep each workspace's required stages and permissions separate.
3. Map queued items to the current responsible reviewer; unknown permissions block assignment.
4. Report duplicate export rows separately from the same person reviewing two different workspaces.

## Output contract
queue_id | workspace_id | client_id | approval_stage | reviewer_id | source_time | unresolved_route

## Fictional acceptance test
Fictional reviewer X appears in workspaces A and B. Produce two routes, not one combined client. Duplicate row A/P 1 is counted once only after its stable ID and version match.

## 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://planable.io/guides/content-approvals-in-planable/

Checked October 8, 2026. Oct8 live GSC through Oct5: marketing copilot 37 impressions, Planable/Claude 33 and Planable/ChatGPT 23, campaign brief 12 and reports 11. Marketing/social topics follow these parent-query leads; other professions follow method-source workflow needs, not exact query measurements. Exact monthly volume is unmeasured.