# Approval Level Coverage Gap Check

Check that every required multi-level approval level is recorded before a post is scheduled.

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

## Inputs
Post approval policy, required approval levels and recorded approvals for each post.

## Workflow
1. List the approval levels the workflow requires for the post.
2. Match each required level to a recorded approval.
3. Separate covered levels from missing levels.
4. Return the coverage map without changing any post status.

## Output contract
post | required_levels | recorded_levels | missing_levels | blocked

## Fictional acceptance test
Fictional post needs 2 approval levels and only level 1 is recorded: 2 required minus 1 recorded leaves 1 missing level, so the post stays blocked.

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