Duplicate Post Field Carryover Check

Check which fields a duplicated post carries over before the copy is treated as ready. Preparation only, not an account action.

What to provide

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

How it works

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.

The output

original | duplicate | fields_carried | fields_dropped | unsafe_carries | verdict

Worked fictional example

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.

Checks and limits

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.

More marketing workflows · How-to guides

Method: reviewed source. Demand lead: Oct17 live AIS Search Console: marketing Copilot 37 impressions, Planable/Claude 45, Planable/ChatGPT 24, campaign brief 12, Muse India 125. Analytics and reporting topics follow parent-query leads plus documented marketing operations needs, not measured exact intent. Site impressions are not monthly volumes; exact topic volume is unmeasured. Checked October 22, 2026.