Release the change you actually checked.
Prepare the task on the correct environment, review its result and identify what is approved to move to production.
This chapter is a general workflow checklist. Your site’s release process and current product controls determine how each step is carried out.
Inspect copy, layout and links.
Read the final text against the approved input. Check headings, images, button labels and link destinations. Inspect desktop and mobile layouts.
Ask for corrections where the result differs from the task or site rules. Check the complete revised page, not just the changed sentence.
Test the functions touched by the change.
Identify the relevant form, navigation path, store flow or integration. Test the behavior using an authorized process that protects real records and transactions.
A local visual preview may not have the same connected systems as the live site. Record what the preview can establish and which checks need another environment.
With staging: test the intended version.
Save the local change in version history and test that version on staging. Correct issues, then identify the exact version and destination approved for production.
Keep live operational data separate when moving the code change.
Without staging: narrow the release.
Check locally, confirm the recovery coverage and use the documented process for a small approved release.
This path does not have a separate staging check. Keep the scope and post-release verification explicit.
Read back the live result.
Open the changed page and repeat the relevant behavior check. Confirm whether the intended code or content is actually live.
If an operation reports an uncertain result, inspect current state before repeating it. Record findings so the next task can begin from what is known.