Checks, acceptance and delivery
Delivery should make the artifact, version, usage and maintenance path clear. Transferring a file is only part of making a result usable by someone else.
Agree on completion criteria
Criteria can include source support, readable mobile pages, completed primary tasks and recoverable failures. They should relate to the need rather than only listing technical checks that are easy to pass.
Distinguish kinds of verification
Structure checks, functional tests, visual review, device testing and human acceptance answer different questions. A pass applies to the tested conditions. Local testing is not deployment, and deployment does not establish content or commercial acceptance.
Preserve usable deliverables
Identify locations, versions, instructions, editable sources and known limits. Where further maintenance is expected, retain changes, dependencies and the next step so future participants do not have to guess the original reasoning.
Record gaps and recovery options
List untested conditions, missing information and inapplicable situations. Keep traceable versions rather than removing history, and know how to locate the last usable release when changing a public site or system.