Finish
After the build
Phases 6–9 · QA/UAT → Go-live → Hypercare → Closure
The same gates apply to every tool: QC checklist executed and UAT signed off, production cutover, a hypercare window, then a handoff pack.
6. QA / UAT
Gate: QC checklist executed — UAT sign-off
| Tool | What to do | |
|---|---|---|
| AEP | Row-count reconciliation, null/duplicate SQL, identity spot-checks, blocked-activation test | |
| Adobe Analytics | SDR validation; reconciliation with source systems | |
| Launch (Tags) | Debugger/Assurance, cross-browser, opt-out test, performance | |
| Marketo | Test-lead walkthrough, rendering, two-way sync | |
| RTCDP | Precedence tests, consent exclusion, blocked activation, small-audience export | |
| AEM | Accessibility, SEO, performance, cache, broken links | |
| Target | Flicker, metric on every variant, audience bucketing | |
| AJO | Test mode on every branch, proofs, dry run, consent and cap tests | |
| CJA | Reconcile with Analytics/source; stitching spot-check; access test |

screenshots/phases/phase-6.png7. Go-live
Gate: Production cutover — Go-Live sign-off
| Tool | What to do | |
|---|---|---|
| AEP | Promote via sandbox packages; start Prod dataflows | |
| Adobe Analytics | Cut over (parallel run if migrating) | |
| Launch (Tags) | Publish to Prod with rollback; remove old tags | |
| Marketo | Activate campaigns; domain warm-up | |
| RTCDP | Activate Wave 1 audiences | |
| AEM | DNS/CDN cutover; redirects | |
| Target | Activate first activities | |
| AJO | Phased activation; IP warm-up | |
| CJA | Share projects; schedule reports |

screenshots/phases/phase-7.png8. Hypercare (2–4 weeks)
Gate: Daily monitoring; fixes — Hypercare Exit sign-off
| Tool | What to do | |
|---|---|---|
| AEP | Dataflow failures, ingestion lag, profile counts | |
| Adobe Analytics | Data anomalies, broken variables | |
| Launch (Tags) | Beacon errors, duplicate hits, page speed | |
| Marketo | Deliverability, sync errors | |
| RTCDP | Match rates, sync failures, audience size drift | |
| AEM | Error logs, cache, author issues | |
| Target | Traffic split, page performance | |
| AJO | Bounces, complaints, step-event errors | |
| CJA | Ingestion lag, data view issues |

screenshots/phases/phase-8.png9. Closure & handoff
Gate: Handoff pack: runbooks, access list, training, open backlog
| Tool | What to do | |
|---|---|---|
| AEP | Runbook for failed dataflows and schema changes; final SDR; access list; training | |
| Adobe Analytics | SDR handoff, Workspace training, governance cadence | |
| Launch (Tags) | Property documentation, publishing process, audit schedule | |
| Marketo | Program templates, operations runbook, SLA review | |
| RTCDP | Audience naming and ownership guide; destination runbook; governance doc | |
| AEM | Author training, component docs, release process | |
| Target | Results repository, roadmap process, governance | |
| AJO | Journey catalog, template library, deliverability runbook, training | |
| CJA | Data dictionary, project catalog, access model |

screenshots/phases/phase-9.pngFinal rows of the master sequence
| # | Tool | Configuration | Depends on | Output | Phase |
|---|---|---|---|---|---|
| 23 | All tools | End-to-end test: one synthetic person from web visit → profile → audience → journey → report | 1–22 | End-to-end test log | QA / UAT |
| 24 | All tools | Go-live in waves; hypercare monitoring across dataflows, activations, journeys, tags | 23 | Go-Live and Hypercare Exit sign-offs | Go-live & hypercare |
| 25 | All tools | Handoff: runbooks, SDR/SDD final versions, access list, training, backlog | 24 | Closure and handoff pack | Closure |
Interview questions
What happens in UAT?
Business users test agreed scenarios against acceptance criteria in a production-like environment, log defects, and sign off when criteria are met.
What is in a go-live plan?
Cutover steps and owners, timing, rollback plan, communication, smoke tests after launch and who approves go/no-go.
What is hypercare?
A 2–4 week period of heightened support after go-live where the delivery team monitors daily and fixes issues before steady-state support takes over.
What goes into a handoff pack?
Runbooks, final SDR/SDD, access list, training materials, open backlog and support contacts.
A critical defect appears on launch day. What do you do?
Assess impact, decide fix-forward or rollback with the sponsor, communicate, then run a root-cause review.