ChecklistForge

Software Deployment Checklist

A step-by-step checklist for deploying software to production safely.

Published June 27, 2026

PrintablePDFITSoftwareDevOpsDeployment

Pre-deployment checks

  • Confirm the code is reviewed, approved and merged to the release branch.
  • Verify all automated tests and the build pass in the pipeline.
  • Check that database migrations are written and reversible where possible.
  • Confirm environment variables, secrets and config are set for production.
  • Review and update dependencies, and check for known vulnerabilities.
  • Schedule the deploy window and notify the team and stakeholders.
  • Freeze unrelated changes to keep the release scope clear.

Prepare and back up

  • Take a fresh backup of the production database before deploying.
    Verify the backup completed and is restorable.
  • Snapshot or back up critical files and current configuration.
  • Record the currently deployed version and commit hash.
  • Confirm rollback artifacts, such as the previous build, are available.
  • Put up a maintenance page if downtime is expected.
  • Verify monitoring and alerting are active before you begin.

Execute the deployment

  • Deploy to a staging or canary environment first if available.
  • Run database migrations and confirm they complete successfully.
  • Deploy the new application version to production.
  • Apply configuration and feature-flag changes as planned.
  • Clear or warm caches and CDN content as needed.
  • Restart or reload services and confirm they come back healthy.

Smoke test and verify

  • Confirm the application loads and the correct version is live.
  • Test critical user paths such as login, checkout or core workflows.
  • Verify integrations and third-party services respond correctly.
  • Check error rates, response times and resource usage.
  • Validate that the database changes behave as expected.
  • Confirm background jobs and scheduled tasks are running.

Rollback plan

  • Define clear criteria for when to roll back versus fix forward.
  • Document the exact steps to revert code, config and migrations.
  • Know how to restore the database backup if data is affected.
  • Assign who has authority to trigger a rollback during the window.
  • Test that the rollback path works before relying on it.
  • Communicate immediately if a rollback is performed.

Post-deployment monitoring

  • Watch dashboards, logs and alerts closely for the first period after deploy.
  • Compare key metrics against the pre-deploy baseline.
  • Remove the maintenance page and confirm full availability.
  • Notify stakeholders that the deployment is complete and stable.
  • Close out the release and update deployment records and tickets.
  • Log any issues and follow up with a retrospective if needed.

0 / 37 done

A software deployment checklist is a step-by-step list that guides a team through pushing code to production safely. It covers pre-deploy verification, backups, the deployment itself, smoke tests, a rollback plan and post-deploy monitoring — so releases go out predictably instead of becoming late-night emergencies.

Most production incidents trace back to skipped steps: an unrun migration, a missing config value, no backup before a risky change, or no plan to roll back when something breaks. A repeatable checklist removes that guesswork.

This checklist walks through deployment in order — confirming what's ready, protecting against data loss, executing the deploy, validating that it works, and watching the system afterward. Keep a clear path back to the previous version at every stage.

Use the printable version during release windows, or save the PDF and share it with developers and on-call engineers so the same steps run on every deploy. Adapt it to your pipeline, whether you ship manually or through CI/CD.

FAQ

What should I check before deploying to production?

Confirm the build passed all tests, the change is reviewed and approved, migrations and config are ready, and you have a recent backup and a rollback plan. The pre-deploy section covers each of these so nothing critical is missed.

Why is a rollback plan so important?

Even well-tested deploys can fail in production due to data, load or environment differences. A clear rollback plan — knowing how to revert code, config and migrations quickly — turns a potential outage into a brief blip.

What is a smoke test after deployment?

A smoke test is a quick check of critical paths right after deploy, such as logging in, loading key pages and a core transaction. It confirms the deployment is healthy before you consider the release done.

Does this work for CI/CD pipelines?

Yes. Many of these steps can be automated in a CI/CD pipeline, but the checklist still helps you confirm each gate is in place. Use it to design your pipeline and as a manual fallback for hotfixes and manual deploys.

Can I download this deployment checklist as a PDF?

Yes. You can print it or save it as a PDF for your team to follow during every release window, ticking off each step as the deployment progresses.

Related templates