Migration owner-disposition questionnaire

Use this at M0 and revisit it before the first milestone publication. It separates decisions that can be made for a noindex staging candidate from the production-only decisions a human must make at cutover. Record answers in the client repository; do not store client identities, credentials, or approval records in the shared toolkit.

An answer authorizes only the named scope. A staging approval is not production approval. Never pre-check an answer, infer an owner, treat silence as consent, or convert a technical PASS into human approval. If a handover reviewer rejects a closed item, reopen the same issue so its history remains the acceptance record.

Authority and workflow

1. Who may approve product, content, and staging decisions?
2. Who gives final stakeholder sign-off?
3. Which GitHub account owns code review or CODEOWNERS approval?
4. Who fills the release operator, production/DNS approver, monitor, and emergency-admin roles?
5. Does the current repository plan support the required protected-branch controls, or is a later account-plan upgrade accepted?
6. Should changes land through a review branch and pull request?
7. Who reviews generic toolkit changes separately from client-specific changes?

Listings, reviews, and source ownership

8. Is the supplied map/listing URL the owner-approved destination, and what entity does it name?
9. Is an official listings/reviews API available? If not, is a dated manual capture acceptable?
10. Who controls the listing provider account?
11. May recent public reviews be captured read-only for staging content, and what attribution and freshness rules apply?

Templates, content, translation, and SEO

12. Which page-family/template contract is approved?
13. Should missing structured sections be completed from already-approved source-language content?
14. May draft FAQs be added to applicable pages, subject to handover review?
15. Who reviews factual, clinical, legal, and content accuracy?
16. Who reviews the localized-language copy?
17. May translation defects be corrected while preserving source meaning and protected terms?
18. Which geographic/service-area targets are approved?
19. Is a route-level keyword and search-intent map approved?
20. May thin pages be expanded under the agreed SEO and factual-source rules?

Forms, identity, and anti-abuse

21. Who provisions Turnstile or equivalent anti-abuse credentials, and where are secrets stored?
22. What is the form-delivery channel?
23. Which staging-only recipients may receive test submissions?
24. May redacted submissions be sent in every supported language during staging QA?
25. Who confirms receipt and routing?

Chat and contact behavior

26. What may the assistant discuss, and which source content is authoritative?
27. What is the chat retention rule?
28. How does a visitor request human help: call, email, contact form, or another approved path?
29. Is stronger session/IP rate limiting approved for staging and production candidates?
30. Who performs the manual chat transcript and safety review?

Analytics, consent, and privacy

31. Which existing analytics/tag-manager property is migrated at cutover?
32. Who owns or can configure that property?
33. Which optional tracking is blocked until consent, and which strictly necessary operational signals may run before consent?
34. Which conversion events are approved?
35. Must analytics remain disabled on localhost and noindex staging unless explicitly test-enabled?

Design review

36. Which design direction is selected from the isolated coded/mock options?
37. Which representative routes and viewport sizes require visual approval?
38. Is approval staged by language or reviewed as one bilingual candidate?

Staging evidence and cutover boundary

39. May a clean sealed candidate deploy to the existing noindex staging service?
40. May the sole reviewer-facing noindex handover update at the same milestone?
41. May an authorized, non-destructive active security scan run against staging only?
42. Which representative routes are in the Lighthouse/PageSpeed gate?
43. What are the approved performance, accessibility, best-practices, and adjusted-SEO floors?
44. When should the full-site crawl run: every change, milestone only, or final readiness only?
45. Who reviews the final paired candidate/handover evidence?
46. Confirm that production deployment, custom-domain attachment, DNS, indexability, and cutover remain manual human actions unless separately authorized at the time of cutover.

Project record template

Copy this table into the client repository and add one row per question. Keep the answer concise but preserve any explicit limitation such as “staging only” or “manual at cutover.”

Close the intake loop only when every question is either answered or explicitly marked deferred with an owner, phase, and follow-up issue. A deferred production-only item need not block staging when the staging boundary and safe fallback are recorded.