
A managed change queue
Track requests, decisions, dependencies, and completion. Coordinate content changes with technical releases and measurement. Keep enough history to separate a planned test from an unrelated change.
List domains, hosting, certificates, software licenses, and renewal contacts. Keep accounts under business ownership. Check who owns the final assets and source files.
- A written brief
- Named responsibilities
- Agreed review points




