# Archived Post Retention Plan Register

Tie a recovery question to the documented plan and archive date, not an unlimited-storage assumption.

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

## Inputs
Post IDs, archive timestamps, plan evidence at archive time, current help policy and reviewer cutoff.

## Workflow
1. Record the archive event separately from permanent deletion.
2. Compare the documented Basic/Pro 30-day and Enterprise 1-year retention windows with the actual plan.
3. Keep unknown plan or timezone evidence held; do not promise recovery from a calculated deadline.
4. Return at-risk records and owner questions without restoring or deleting content.

## Output contract
post | archived_at | plan_source | documented_window | cutoff | recovery_unverified

## Fictional acceptance test
Fictional A is archived 31 days ago on Pro; B 10 days ago on Enterprise. A exceeds the documented 30-day window; B is within the 1-year window. Neither calculation proves a current restore button exists. Unknown plan is held.

## 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/21865781725340-Delete-archive-restore-a-post

Checked October 12, 2026. Oct12 live AIS Search Console: marketing Copilot37 impressions, Planable/Claude38, Planable/ChatGPT24, campaignbrief12, investoragent19, MuseIndia100. 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.