# Duplicate Post Field Carryover Check

Check which fields a duplicated post carries over before the copy is treated as ready.

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

## Inputs
The original post’s fields and the fields the duplicate retained.

## Workflow
1. List the original post’s field groups: content, media, labels, approval state, schedule slot.
2. List the field groups the duplicate retained.
3. Flag carried-over state that should not transfer, such as approval or the slot.
4. Return the check without post changes.

## Output contract
original | duplicate | fields_carried | fields_dropped | unsafe_carries | verdict

## Fictional acceptance test
Fictional duplicate of a post carries caption, media and labels (3 field groups) but drops the approval state and schedule slot (2): a team treating the copy as approved would publish 1 unapproved post.

## 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/21715500906780-Duplicate-or-copy-posts

Checked October 22, 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.