# Multi-Level Approval Step Evidence

Check each review level separately before calling a social post fully approved.

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

## Inputs
Post ID and version, ordered levels, designated approvers, approval events, dated workflow settings and plan evidence.

## Workflow
1. Match every event to the same post version and workspace.
2. For each level, identify whether a designated approver has supplied approval evidence.
3. Keep a completed level separate from completion of all required levels; flag ambiguous vendor wording for account verification.
4. Return missing levels without approving, scheduling or publishing.

## Output contract
post_version | level | approver_evidence | complete_or_unknown | missing_level | account_check

## Fictional acceptance test
Fictional post V2 has level 1 approval by A, level 2 pending. Another level 1 approver B has not replied. Level 1 has evidence under the one-approver rule; the whole workflow is still incomplete.

## 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.
