Confirm what is going live
Record the release version, included changes and any known limitations. Test the important user journeys using realistic roles and data before scheduling the release.
Separate configuration from code
Identify environment-specific settings and the people responsible for them. Keep credentials out of source control. Check that production uses the intended domains, integrations and storage locations.
Plan the data transition
If a migration is required, agree a backup, cutover and reconciliation plan. Check how the application handles existing records and whether the old system needs a temporary read-only period.
Verify the public experience
A running internal service is only part of the evidence. Verify HTTPS, public routes, static assets, forms and the main browser journeys through the actual domain.
Prepare recovery and ownership
Agree a rollback approach and make sure the previous release or backup is usable. Document who receives issues, how support is contacted and what the maintenance arrangement covers.
Check after launch
Review service health and the first real workflows after release. Capture unexpected issues clearly and prioritize fixes before adding further features.