When taking down a production system, create an issue in the Infrastructure repository using this template as the body. Feel free to add/remove tasks as appropriate, add a username after each task to assign it, and/or make corresponding items in your issue tracker. Here’s a more extensive list. The General Records Schedules 3.x are relevant, as well.

You are welcome to ask any questions as comments in the issue or #infrastructure.

Checklist preview

  • Notify any users of the system, via banner across the site, email, Slack, etc. Ideally, help them find alternatives, make sure they’re off in time, etc. (The needs here will be specific to your use case.)
  • Set up redirect(s), if applicable.
  • Export any production data and put it into Google Drive, for records retention purposes.
  • Ask for the organization to be deleted.
  • Delete any associated AWS resources, and decommission any AWS accounts. Ask in #infrastructure for help.
  • Archive the GitHub repositor(ies). Ask in #admins-github if you need help.
  • Clean up any DNS entries that are no longer needed, from the DNS repository or elsewhere.
  • If there’s a custom (second-level) domain, figure out what to do with it.
  • Assuming it has an ATO, notify GSA IT that the system no longer exists. Ask in #infrastructure for help.
  • Email GSA Privacy Office at so they can take down the SORN
  • Fill out and send the Disposal Notification Template, which can be found in the list of IT Security Forms
  • Remove (sub)accounts in external services
  • Remove any external integrations
  • Archive the Slack channel
  • Archive the issue tracker (Trello, etc.)
  • Optional: Put up a Federalist site with an embedded Google Form at the same URL. See the Fugacious page (code) as an example.