AEM Sites Playbook, Chapter 7: Governance, workflows, approvals and content lifecycle
What does approval mean, and how is content corrected or retired?
November 10, 2026
Define the state of the content
Use this chapter when approval is unclear, changes wait in queues or content remains live after its useful life. Identify what drafting, reviewed, approved, scheduled, published, expired, archived and deleted mean for the organization. Assign the person who can move content between those states and the evidence required.
Keep the content decision separate from the tool action. Publishing may require an approval, but clicking a particular toolbar control should not be the only expression of that policy. The Quick Publish versus Manage Publication discussion does not confirm a solution to identifying the initiating UI action. Define the intended operation and select the supported workflow/publication mechanism for the actual editor and release. Publication customization
The business owner decides which changes require review and who may approve them. Practitioners implement the workflow and explain failures in language the reviewer can act on. Include emergency corrections, absence of an approver, rejected changes and a withdrawn approval. Avoid a process that works only when every participant is available.
Give reviewers a meaningful baseline
An approver needs to understand the proposed change relative to the previously approved content. In the page-comparison workflow discussion, follow-up exposes the problem with creating a version only after editing: it can capture the proposal instead of the baseline needed for comparison.
Agree when the approved baseline is recorded, how the reviewer finds it, what evidence accompanies approval and how the next change uses it. Test the policy with an actual edit, rejection and subsequent revision. Adobe's page-version guidance supports content snapshots and comparison; content versions do not restore application code, CSS or JavaScript. Retain the code-release identity beside the content decision when rendering behavior matters.
For a hypothetical campaign correction, the record should show the old approved claim, proposed wording, approving person, affected locales and publication deadline. If a shared fragment changes other pages, the reviewer needs those consequences before approval.
Operate the lifecycle after approval
Record a review/expiry owner when publishing. Decide whether withdrawal removes the content, replaces it, redirects its URL or retains an approved archive. Different customer needs justify different outcomes. Coordinate references, search, caches and connected channels before deleting shared content.
Inspect stalled work by state and cause: missing assignee, failed service operation, unresolved dependency or rejected content. Assign a queue owner who can distinguish editorial delay from technical failure. Retrying everything without understanding the state can duplicate work or obscure the original failure.
Treat retention and maintenance as deployment-specific operations. The maintenance discussion mixes a Cloud Service title with a 6.5 body and gives no confirmed purge result. Use the actual platform's current maintenance guidance and protect the history needed for approval and recovery. Coordinate technical purge policies with content and operational owners.
Define what an approval must establish
Community discussions highlight two workflow decisions: which approved content forms the comparison baseline, and which business operation should initiate publication. The examples do not establish a universal implementation or a reliable distinction based only on the initiating UI control. Start with the business operation and the evidence reviewers need.
Scroll horizontally if needed.
| Change | Decision needed | Reviewer evidence |
|---|---|---|
| Correct a factual statement | Who owns the fact and affected channels? | Previous approved value, proposed value and scope |
| Change a shared fragment | Which dependent experiences require review? | Reference/consumer inventory and representative output |
| Change locale-specific wording | Who approves the local variation? | Source/local differences and applicable ownership policy |
| Urgent correction | Who may authorize the exceptional path? | Impact, reason, limited scope and subsequent review |
| Expire or delete content | What should replace it and what depends on it? | URLs, references, search/delivery consequences and recovery |
Establish the baseline before the reviewer receives the task. Record how the first approval works when no earlier approved version exists. If code or a template change affects presentation, identify that release beside the content comparison. Page-version documentation distinguishes content snapshots from code/CSS/JavaScript.
Worked scenario of a corrected offer
This hypothetical scenario concerns a shared offer used on several pages in two locales. An author corrects its wording, and the review team requires comparison with the previous approved offer before release. One reviewer is absent during the launch window.
The editorial owner defines a primary reviewer and substitute. The workflow owner records states and transitions explicitly:
Scroll horizontally if needed.
| State | Responsible action | Required condition |
|---|---|---|
| Draft | Author prepares the proposed revision | Required content and references are present |
| Ready for review | Workflow presents the proposal and baseline | Reviewer can distinguish old and new content |
| Rejected | Author revises against feedback | Rejection reason and unchanged baseline are retained |
| Approved | Authorized reviewer accepts the defined scope | Approval identifies the exact proposed content |
| Scheduled or released | Publisher performs the authorized operation | Approved revision/dependencies and destination are checked |
| Corrected or withdrawn | Content owner chooses the next operation | New scope and delivery consequences are explicit |
The team tests an edit, rejection, second edit, substitute approval and attempted later modification. It checks the actual implementation's behavior when content changes after approval; that behavior must be governed rather than assumed.
Suppose the trial finds that the comparison shows the new offer on both sides because the baseline was created after editing. It also finds that the substitute can approve but cannot inspect a required referenced fragment. Those are separate failures: baseline policy/configuration and reviewer access. Extending a task's due date would repair neither.
The owner chooses to preserve the earlier approved content as the comparison baseline and correct the substitute's intended read authority. The same fixture is repeated. If access can only be obtained through an overbroad administrator role, the team keeps the approval task open instead of accepting that shortcut as the operating design.
Handle concurrency, rejection and exceptions
Scroll horizontally if needed.
| Condition | Explicit policy to choose | What to verify |
|---|---|---|
| Two authors change the same shared item | Conflict/review ownership and proposal identification | Reviewer accepts the intended revision |
| Content changes after approval | Invalidate approval, require reapproval or another controlled rule | Unreviewed changes cannot silently use old authorization |
| Review is rejected | Preserve baseline, reason and assigned rework | The next comparison reflects the intended proposal |
| Approver is unavailable | Named substitute and escalation | Required access and decision authority both work |
| Emergency publication | Bounded authority and retrospective follow-up | Scope, reason and customer-visible result are retained |
| Workflow operation fails | Distinguish editorial state from technical error | Retry/recovery does not duplicate or erase the decision |
These are policy questions to implement and test on the actual release. They are not claims that every default workflow already enforces the chosen rule.
Evaluate throughput without weakening review
Measure active review effort, waiting time, rejection/rework and failed operations separately. A shorter queue achieved by removing required context is not equivalent to a better approval process. Inspect why reviewers wait: unclear ownership, incomplete proposals, missing references or unavailable systems call for different interventions.
The pilot decision should state which mandatory conditions passed, which remain open and whether an explicitly limited path is acceptable. Assign ownership of retained history and scheduled maintenance so the evidence needed for future review or recovery is not unintentionally purged. The approved lifecycle continues after the initial publication window.
Keep the approval defensible
Complete W07 with states, actors, comparison baseline, dependencies, decision, deadline and withdrawal plan. Accept the process only after a representative author and reviewer complete approval, rejection/rework and withdrawal using ordinary identities. Test restore separately in chapter 19; the restore discussion shows that preceding custom changes can matter even when the visible symptom appears to be versioning.
W07 Lifecycle and approval baseline
Use with chapter 7. Retain enough evidence to explain what was approved.
Scroll horizontally if needed.
| Record | Entry |
|---|---|
| Lifecycle states and authorized transitions | [enter] |
| Previous approved version and proposed content version | [enter] |
| Relevant code release and affected shared content/locales | [enter] |
| Comparison evidence, reviewer, decision and decision time | [enter] |
| Rejection/rework, absent approver and emergency-correction process | [enter] |
| Review/expiry, withdrawal and retention responsibilities | [enter] |
