# Content Export Page and Post Count Tieout

Tie an export manifest to its selected pages and filtered posts before calling it a complete client archive.

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

## Inputs
Selected page IDs, filters, modal page/post counts and exported row IDs.

## Workflow
1. Record selected pages and filters at export time.
2. Compare modal counts with unique post/page IDs in the file.
3. Keep unknown selection or duplicate IDs as coverage gaps.
4. Return a manifest, not a whole-account completeness claim.

## Output contract
export | selected_pages | selected_posts | file_unique_ids | count_gap | hold

## Fictional acceptance test
Fictional modal says 12 posts on 2 pages; file has 11 unique post IDs on 2 pages. Flag 1 missing ID, not a complete 12-post archive. Equal row counts alone would not prove ID coverage.

## 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/21715418572828-Export-content

Checked October 14, 2026. Oct14 live AIS Search Console: marketing Copilot37 impressions, Planable/Claude43, Planable/ChatGPT24, campaignbrief12, investoragent19, MuseIndia107, cashflowforecasting13. Social calendar/reporting topics follow parent-query leads; other professions follow documented workflow needs, not measured exact intent. Site impressions are not monthly volumes; exact topic volume is unmeasured.