# Approval Version Event Order

Keep a review event tied to the content version it actually reviewed.

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

## Inputs
Post version IDs, content hashes or supplied change log, ordered approval events, timezone and workflow lock policy.

## Workflow
1. Order events using exact times and timezone; hold missing ordering.
2. Bind each event to the documented version or flag missing version linkage.
3. Separate a changed image or caption from an unchanged scheduled time; use supplied policy for required re-review.
4. Return event-to-version gaps without assuming an old approval transfers.

## Output contract
event_id | reviewed_version | latest_version | change_kind | sequence_known | rereview_question

## Fictional acceptance test
Fictional A approved V1 at 09:00, caption became V2 at 09:20. Approval remains evidence for V1. No V2 event is supplied, so current approval is held, not silently inherited.

## 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 10, 2026. Oct10 live AIS Search Console through Oct6: marketing Copilot 37 impressions, Planable/Claude 33, Planable/ChatGPT 23, campaign brief 12, investor agent 19. Social-review/reporting topics follow these parent-query leads. Other professions follow documented workflow needs, not measured exact search intent. Site impressions are not monthly volumes; exact topic volume is unmeasured.