# Approval Level Scope Conflict

Find a mismatch between a documented review policy and the configured review levels.

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

## Inputs
Approved review policy, configured levels and rosters, content risk category and dated settings.

## Workflow
1. Extract required review categories from the supplied policy.
2. Map each category to a configured level and named authorized reviewer.
3. Keep policy intent distinct from tool configuration; missing mapping is not a passed review.
4. Return a private configuration question, not a new level or publication clearance.

## Output contract
policy_category | required_review | configured_level | mapping_source | gap

## Fictional acceptance test
Fictional policy requires separate brand and legal review; configured levels show only brand. Report legal mapping missing. A level labelled Final without a scope definition is not proof of legal review.

## 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/21715417710876-Multi-level-approvals

Checked October 10, 2026. Oct10 live AIS Search Console through Oct6: marketing Copilot 37 impressions, Planable/Claude 33, Planable/ChatGPT 23, campaign brief 12, investor agent 19. Social-review/reporting topics follow these parent-query leads. Other professions follow documented workflow needs, not measured exact search intent. Site impressions are not monthly volumes; exact topic volume is unmeasured.