Go-live checklist

It is free to fill in online, needs no account, and downloads as a Word document or a PDF. See all IT and projects templates

• Project or system

  For example: New customer portal

• Launch target

  For example: Production, portal.example.com

• Planned go-live date and time

  For example: Saturday 4 March 2028, 06:00 to 09:00

• Launch lead

  For example: Hamza Idrissi

• Testing

  One row for each item. The date goes in Done on when it is finished.

  For example: All planned tests passed User acceptance test signed off Load test at twice expected traffic Two low priority bugs open, accepted by the sponsor

• Data and migration

  One row for each item. The date goes in Done on when it is finished.

  For example: Test migration run and checked Final migration time agreed Old data kept read-only for 90 days

• Security and access

  One row for each item. The date goes in Done on when it is finished.

  For example: Test accounts and default passwords removed Security review done HTTPS and certificate valid Admin access limited to named people

• Hosting, backups and monitoring

  One row for each item. The date goes in Done on when it is finished.

  For example: Backup taken and a restore tested Monitoring and alerts on Domain and DNS ready Email sending checked

• People, training and support

  One row for each item. The date goes in Done on when it is finished.

  For example: Support team trained Help pages published On-call rota for the first week Customers told of the date

• Rollback plan

  For example: If the checks fail by 09:00, switch DNS back to the old portal (about 15 minutes). Decision by the launch lead.

• Checks right after launch

  For example: Sign in, place a test order, pay, receive the email, check the dashboards.

• Decision

  For example: Go

• Conditions or reasonsoptional

  For example: Fix the two open bugs within one week.

• Approved by

  For example: Sofia Marin, Managing Director

• Date of decision

  For example: 2 March 2028

1. 1Testing
2. 2Data and migration
3. 3Security and access
4. 4Hosting, backups and monitoring
5. 5People, training and support
6. 6Rollback plan
7. 7Checks right after launch
8. 8Decision

1. 01

   Fill in

   Type your details in the form. The document fills itself in as you type; click any gap to jump to its field.

2. 02

   Check

   Read it through. Gaps you have not filled stay marked, so nothing goes out half done.

3. 03

   Download

   Save it as a Word document to edit further, or as a PDF to send or print.

What details does this template ask for?

The form asks for 15 details, starting with Project or system, Launch target, Planned go-live date and time, Launch lead, Testing. 1 more are optional.

Can I download this template as Word or PDF?

Yes. When you have filled in the form, save it as a Word document to keep editing, or as a PDF to send or print. It is free and needs no account.

Is what I type sent anywhere?

No. What you type stays in your browser while you fill in the document. It only goes to nerix if you choose to open the template in the chat.

Are these IT and project templates free?

Most are. Fill in and download them for free as Word or PDF, with no account. A few longer documents are premium: free to fill in, paid once to download, and marked with their price.

Does a security policy make us secure?

No document does that alone. A policy helps when it matches what people really do, so keep it short, explain it to your team and review it every year.

Is a project charter only for large projects?

No. A small project benefits too, because one page that names the goal, the limits and the decision maker prevents most arguments later.

• API integration specificationSpecify how two systems connect: what data moves, how it is secured, how errors are handled and who owns it.IT and projects
• Architecture decision recordRecord a technical decision with its context, options, reasons and consequences, for the team to find later.IT and projects
• Bring your own device policySet the rules for using personal phones and laptops for work: security, privacy, support and leaving.IT and projects
• Bug reportReport a software problem so a developer can repeat it, judge its impact and fix it.IT and projects
• Change management planPlan how people will be told, trained and supported through a big change, and how you will know it worked.IT and projects
• Change requestAsk for a change to a project or system, show its impact and record whether it is approved.IT and projects

See all IT and projects templates