An inventory that reflects reality
Each website has recorded hosting, domain renewal, certificates, source code and critical features. Unknown access is resolved before migration. The inventory is not a list of passwords in a public document; secrets remain separate with restricted access.
Changes pass defined checks
A release first passes a build and checks of critical routes, forms and access. The previous state is saved before production changes. After publication, I verify what visitors actually receive rather than relying on a successful command exit.
Copies and recovery evidence
Source history tracks code changes. A whole-server copy captures its contents at a particular time. An older copy cannot prove that newer changes are protected. Recovery testing is defined around the actual system and agreed scope.
A known scope for each problem
Monitoring should distinguish an unavailable website from a failure in one feature. Checks therefore cover contact handling, important public routes and agreed integrations as well as the homepage. Response priorities and arrangements are part of the agreement, not an invented universal deadline.