Content lifecycle and review log
================================
Source: https://yenra.com/content-lifecycle-management/
Prepared October 4, 2026.

Use one record per content item; add a dated line for each decision.
Content ID: __________________  Public URL: __________________
Owner/contact: _______________  Content purpose: ______________
Current public revision: _____  Proposed revision: ____________
Current state: _______________  Next action and responsible person: __________
Reviewer: ____________________  Exact revision approved: ______
Approval evidence/time: ______  Planned publication: __________
Dependencies (downloads, translations, shared facts): _______________________
Public verification result and person: ____________________________________
Review trigger/date: _________  Facts and links checked: ___________________
Review outcome (no change, revise, retire): ________________________________
Replacement route if retired: _____________________________________________
Records/retention decision and authority: __________________________________

Fictional example: LOAN-01 revision 4 remains public while revision 5 changes
the collection location. Operations checks the new location and map. The owner
approves revision 5. The publisher releases the guide/map/email and checks the
public route. Record the exact released version and subsequent review trigger.

Suggested states: draft, in review, approved, published, due for review,
superseded/retired. Due for review may be a flag on a published item.
New consequential changes after approval require the relevant review again.
Review example: https://www.drupal.org/docs/8/core/modules/content-moderation/overview