Delivery that lasts

Launch checklist

Most launch problems are not code. They are the domain nobody owns, the backup nobody tested and the error nobody sees. Work through the list here, or take the PDF into a meeting.

Use the tool

Domain and access
  • Domain registered in your own name, not the builder's
  • DNS access documented, and at least two people can reach it
  • TLS certificate valid and set to renew automatically
  • www and the bare domain both work, one redirecting to the other
Backups and rollback
  • Backups run automatically, every day
  • A restore has actually been tested, not just configured
  • Rollback plan written down: who does what if the launch fails
  • The previous version stays deployable for the first weeks
Legal and consent
  • Privacy policy and terms published and dated
  • Cookie consent appears before any non-essential trackers load
  • Contact and company details (VAT number) are on the site
  • Forms state what happens with the data people enter
Monitoring and errors
  • Error monitoring alerts a person, not a dashboard nobody watches
  • An uptime check tests the site from outside
  • A test error was triggered and the alert actually arrived
Quality pass
  • Performance checked on a mid-range phone over mobile data
  • Keyboard navigation and contrast checked on the main flows
  • Forms tested with wrong input, not only with correct input
  • A 404 page exists and helps visitors onward instead of dead-ending
  • Analytics events verified in the live tool, not only in the code
The first 48 hours
  • Everyone knows how to reach the developer if something breaks
  • A moment is planned on day 2 to review errors and numbers
Good to know

How to read the result

  • Run it a week early

    Half of these need someone else to act. Found on the evening itself, they become the reason you postpone.

  • Your answers stay here

    Kept in this browser so a reload does not cost you the list, and nowhere else. Reset clears them.

  • Same list as the PDF

    The tool and the PDF read from one source, so they cannot disagree. Use whichever fits the moment.

More tools

Try another one

  • Software health check Planning
    Software health check

    Score software you already run, and see what the no answers add up to.

    Open tool
  • Partner questions Planning
    Partner questions

    The questions to ask any software builder before you sign.

    Open tool

Need something these can't do?

These are the small ones. The bigger ones we develop for the people who ask.

Tell us what you need