AEM Sites Playbook: Practical Worksheets
Twenty practical AEM Sites worksheets for architecture, content operations, governance, publishing, performance, releases, migration and recovery.
November 10, 2026
Copy the record needed for your task into the team's approved working system. The fields below are blank templates, not completed checks. Keep one record per decision/change when shared evidence is useful; link related records rather than enter conflicting copies. Return to the playbook index to find the relevant chapter.
Common record header
Scroll horizontally if needed.
| Field | Entry |
|---|---|
| Decision or change and accountable owner | [enter] |
| Business approver and technical owner | [enter] |
| Deployment, AEM release/service pack, editor and component/tool versions | [enter] |
| Scope, audience, brand/locale and relevant identity | [enter] |
| Current state, desired result and acceptance criteria | [enter] |
| Evidence location and collection time | [enter] |
| Open condition, owner and review date | [enter] |
| Decision, accepted limitation and failure response | [enter] |
Keep secrets, private customer information and sensitive logs in restricted systems. A worksheet should reference the approved evidence location and access owner.
W01 Strategy and adoption
Use with chapter 1. Agree what the investment should change before estimating a solution.
Scroll horizontally if needed.
| Record | Entry |
|---|---|
| Customer task and business outcome | [enter] |
| Current process, baseline and recurring failure | [enter] |
| Alternatives including a narrower repair | [enter] |
| Implementation, integration, content, training and operation assumptions | [enter] |
| Content/platform/support ownership and substitutes | [enter] |
| Representative author tasks, training and adoption check | [enter] |
| Benefit measure, observation method and review owner | [enter] |
W02 Architecture decision
Use with chapter 2. Record deployment and delivery/authoring choices separately.
Scroll horizontally if needed.
| Record | Entry |
|---|---|
| Current/target deployment, hosting and support arrangement | [enter] |
| Authoring, preview, frontend and delivery requirements | [enter] |
| Alternatives and reasons for selection/rejection | [enter] |
| Responsibilities for content, frontend, domains, security and operation | [enter] |
| Entitlements and contract assumptions needing confirmation | [enter] |
| Trial fixture, observed result and unresolved constraint | [enter] |
| Condition that would change the decision | [enter] |
W03 Engineering and customization inventory
Use with chapter 3. Give each dependency or extension a requirement and an owner.
Scroll horizontally if needed.
| Record | Entry |
|---|---|
| Module/component/service and requirement served | [enter] |
| Owner, dependency version and compatible target | [enter] |
| Extension point, configuration and content scope | [enter] |
| Service identity, input contract and secret mechanism by reference | [enter] |
| Request trace and valid/invalid/denied test cases | [enter] |
| Disable/uninstall/rollback approach and regression evidence | [enter] |
W04 Authoring acceptance
Use with chapter 4. Test real tasks using the intended author's authority.
Scroll horizontally if needed.
| Record | Entry |
|---|---|
| Template/component, intended use and permitted variants | [enter] |
| Content fixture including long/localized and missing optional values | [enter] |
| Create, edit, validation, reorder/copy/delete and save/reopen steps | [enter] |
| Responsive preview, references and approval handoff | [enter] |
| Intended author identity and observed task result | [enter] |
| Accessibility/regression record and remedy owner | [enter] |
W05 Structured content and consumer contract
Use with chapter 5. Make source ownership and API meaning explicit.
Scroll horizontally if needed.
| Record | Entry |
|---|---|
| Model/field meanings, identifiers and validation | [enter] |
| Source-owned and editor-owned fields with update/delete rules | [enter] |
| Locale/reference relationships and missing-reference behavior | [enter] |
| Management API and separate delivery API/consumer contract | [enter] |
| Model-change compatibility and transition plan | [enter] |
| Duplicate/re-import, withdrawal and consumer test evidence | [enter] |
W06 Brand and locale ownership
Use with chapter 6. Verify permitted local changes survive the intended central operation.
Scroll horizontally if needed.
| Record | Entry |
|---|---|
| Central/local owner by content object or field | [enter] |
| Blueprint/Live Copy/language relationships | [enter] |
| Inheritance/override rule and reason for exceptions | [enter] |
| Translation fields, custom references and asset alternatives | [enter] |
| Central edit, local edit, repeated rollout and move/delete test | [enter] |
| Locale URL mapping, search/discovery checks and regional sign-off | [enter] |
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] |
W08 Capability and data exposure
Use with chapter 8. Create a test entry for each meaningful identity/resource/action combination.
Scroll horizontally if needed.
| Record | Entry |
|---|---|
| Identity/groups/profiles and cumulative assigned authority | [enter] |
| Resource/path, action and approval requirement | [enter] |
| Authentication and backend authorization enforcement | [enter] |
| UI behavior and separate allowed/denied route tests | [enter] |
| Public/private fields, cache isolation and sensitive-data destinations | [enter] |
| Credential lifecycle and security/privacy escalation owners | [enter] |
W09 Media dependency and delivery
Use with chapter 9. Link the media record to its page/fragment release.
Scroll horizontally if needed.
| Record | Entry |
|---|---|
| Asset/reference, source owner and intended use | [enter] |
| Processing, metadata, rights/expiry responsibility and destination | [enter] |
| Delivery interface, supported parameters and target environment | [enter] |
| Required dimensions/crop, format, visual quality and observed bytes | [enter] |
| Alternative/decorative treatment, locale and override owner | [enter] |
| Replace/withdraw, cache and downstream-reference test | [enter] |
W10 Publication and withdrawal evidence
Use with chapter 10. Record the visitor-facing observation as well as the job result.
Scroll horizontally if needed.
| Record | Entry |
|---|---|
| Approved revision/code and dependency set | [enter] |
| Processing complete, scope approved and Preview result where applicable | [enter] |
| Destination, operation, schedule/business time zone and execution owner | [enter] |
| Operation result, failed items and queue state | [enter] |
| Delivered URL/API, identity, revision, time and deadline result | [enter] |
| Withdrawal behavior, observation and recovery/exception owner | [enter] |
W11 Request route and cache policy
Use with chapter 11. Compare the same request when investigating different layers.
Scroll horizontally if needed.
| Record | Entry |
|---|---|
| Domain/TLS, frontend/CDN/web-tier/origin route and owners | [enter] |
| Method, URL/parameters, identity and expected revision | [enter] |
| Intended status/redirect and actual Location/header evidence | [enter] |
| Browser/shared cache variation, expiry and invalidation policy | [enter] |
| Freshness/privacy requirement and measured delivered behavior | [enter] |
| Change hypothesis, scoped action, repeat result and rollback | [enter] |
W12 Performance comparison
Use with chapter 12. Keep the fixture and measurement method stable for the comparison.
Scroll horizontally if needed.
| Record | Entry |
|---|---|
| Failing task, affected users and required result | [enter] |
| Route, content/data fixture, workload and network/device conditions | [enter] |
| Baseline timings/errors/resource symptoms and observation method | [enter] |
| Query/parameters/plan or other layer-specific diagnostic evidence | [enter] |
| Proposed change and repeatable before/after comparison | [enter] |
| Regressions, tested range, accepted trade-off and retest trigger | [enter] |
W13 Search acceptance collection
Use with chapter 13. Keep an entry for each important query and access/locale scenario.
Scroll horizontally if needed.
| Record | Entry |
|---|---|
| Customer task, query and expected relevant result | [enter] |
| Locale/brand/identity and results that must be excluded | [enter] |
| Search route/service, ranking/filter owner and content source | [enter] |
| Zero-result, pagination, facets and snippet/access behavior | [enter] |
| Publication/update/delete timing and observed result | [enter] |
| Relevance judgment, error evidence and remediation owner | [enter] |
W14 API and integration contract
Use with chapter 14. Make replay and reconciliation part of the contract.
Scroll horizontally if needed.
| Record | Entry |
|---|---|
| Sending/receiving system, operation and business completion checkpoint | [enter] |
| Schema, stable identifier, version/order and field ownership | [enter] |
| Documented API family, environment, account/profile and permissions | [enter] |
| Credential mechanism/reference, rotation and denied/expired tests | [enter] |
| Duplicate, older event, timeout, partial success and replay behavior | [enter] |
| Reconciliation, failure retention and operator intervention | [enter] |
W15 Metadata and URL lifecycle
Use with chapter 15. Inspect the actual public response.
Scroll horizontally if needed.
| Record | Entry |
|---|---|
| Public URL, title/description/canonical and origin of each value | [enter] |
| Domain/protocol, locale alternates and corresponding URL map | [enter] |
| Robots/sitemap/structured-data/social metadata requirements | [enter] |
| Old/new URL, redirect approval and expected status/destination | [enter] |
| Initial/delivered markup, actual response and loop/chain tests | [enter] |
| Withdrawal/private-content behavior and metadata owner | [enter] |
W16 Accessibility task matrix
Use with chapter 16. Record full task completion, including any remaining barrier.
Scroll horizontally if needed.
| Record | Entry |
|---|---|
| Author/visitor task, population and required standard/criterion | [enter] |
| Content/component/environment and technology/input combination | [enter] |
| Expected interaction, observed barrier and task impact | [enter] |
| Automated finding and relevant manual/assistive-technology evidence | [enter] |
| Content/design/engineering remedy, owner and priority | [enter] |
| Retest, remaining condition and regression check | [enter] |
W17 Measurement and personalization
Use with chapter 17. Connect the collected event with the decision it should inform.
Scroll horizontally if needed.
| Record | Entry |
|---|---|
| Business question, metric and process/customer-outcome distinction | [enter] |
| Event trigger, field meaning, identifiers and intended destination | [enter] |
| Consent/identity dependencies and responsible owners | [enter] |
| Browser/rule/request/report observation and duplicate/missing tests | [enter] |
| Content variation/default, qualification and failure behavior | [enter] |
| Experiment hypothesis, analysis ownership and decision rule | [enter] |
W18 Release manifest and acceptance
Use with chapter 18. Set required results and hold conditions before the window.
Scroll horizontally if needed.
| Record | Entry |
|---|---|
| Source / code / configuration / dependency identity and affected content | [enter] |
| Target environment and intentional local/pipeline differences | [enter] |
| Required automated/human checks and fixture identities | [enter] |
| First failing check, diagnosis and regression evidence | [enter] |
| Business/technical approvers, hold condition and recovery authority | [enter] |
| Post-release observations, exception owner and handover | [enter] |
W19 Incident and recovery drill
Use with chapter 19. Distinguish observation, hypothesis and confirmed result.
Scroll horizontally if needed.
| Record | Entry |
|---|---|
| Impact, task, timeline, severity and service/communication owners | [enter] |
| Recent changes, sanitized evidence and cause status | [enter] |
| Containment, diagnosis, action and result | [enter] |
| Required recovery point/interruption and selected mechanism | [enter] |
| Overwritten work, current-code compatibility and authorization | [enter] |
| Restored tasks / references / permissions / delivery and follow-up owners | [enter] |
W20 Migration and improvement decision
Use with chapter 20. Retain the rehearsal and reconciliation that justify a date.
Scroll horizontally if needed.
| Record | Entry |
|---|---|
| Reason, alternatives and source/target compatibility inventory | [enter] |
| Representative transfer, code adaptation and identity tests | [enter] |
| References, content changes, URLs, analytics and integration reconciliation | [enter] |
| Freeze/top-up/cutover plan, owners and hold conditions | [enter] |
| Recovery/rollback conditions and handling of newer content | [enter] |
| Launch/limited launch/hold/redesign decision and accepted scope | [enter] |
| Retirement, benefit review and prioritized improvement backlog | [enter] |
Worked example of connected records
This example is hypothetical. A regional campaign owner needs an approved product statement and image to appear in two locales during an agreed launch window. The content owner records the intended result in W01. W06 assigns central ownership of the product fact and regional ownership of the translated copy. W07 retains the prior approved baseline and the review decision. W09 identifies the image and text-alternative owner. W10 records the dependency set and delivered observations for each locale. W11 explains a freshness exception if the response remains stale. W18 records the release decision; W19 is opened only if an incident needs investigation or recovery.
Reuse identifiers and evidence links between these records. Do not mark a field passed because another record exists; inspect the evidence for the actual task. An unresolved mandatory requirement belongs in the readiness decision with a named owner and explicit hold or accepted narrower scope.
