Phase: Closing | Audience: Internal | Project: WEB-2026-01 Corporate Website Development
In simple words: The Go-Live Checklist lists every step for launch day with an owner and a tick box, plus a rollback plan if something goes badly wrong.
Think of it like: A pilot's pre-flight checklist: every item is checked in order before take-off, however experienced the pilot.
When is it created? | Prepared before launch (7 Dec 2026), used 7–11 Dec |
Who prepares it? | Backend Developer |
Who approves or uses it? | Go/no-go decision with the client |
What happens next? | Site is live; training and handover follow |
Below is the actual document for project WEB-2026-01. Read the purpose first, then go through each numbered section.
Issued by: [Your Company] Technologies Pvt. Ltd.
Purpose: Every step for launch on Wed 9 Dec 2026, with owner and a tick box. Go-live proceeds only when all pre-launch items are ticked.
Item | Detail |
Document no. | WEB-2026-01/GLC |
Version | 1.0 |
Date | 7 Dec 2026 |
Owner | Backend Developer |
Audience | Internal |
Phase | Closing |
Status | Planned |
# | Task | Owner | Done |
1 | UAT sign-off form signed | PM | ☐ |
2 | Content freeze announced to client | PM | ☐ |
3 | Full backup of staging site | Backend | ☐ |
4 | Production server hardened and updated | Backend | ☐ |
5 | DNS TTL lowered to 5 minutes, 24 hours before switch | Backend | ☐ |
6 | 301 redirects mapped from old site URLs | Backend | ☐ |
7 | GA4 production property and Search Console ready | Backend | ☐ |
8 | Robots setting allows search indexing | Content | ☐ |
9 | Forms send to production sales inbox | QA | ☐ |
10 | Go/no-go meeting held with client (8 Dec, 16:00) | PM | ☐ |
# | Task | Owner | Done |
11 | Deploy site to production | Backend | ☐ |
12 | Switch DNS to new server | Backend | ☐ |
13 | SSL certificate issued; padlock shows | Backend | ☐ |
14 | Smoke test all 11 pages on phone and laptop | QA | ☐ |
15 | Submit a live contact form | QA | ☐ |
16 | Submit XML sitemap to Search Console | Content | ☐ |
17 | Confirm GA4 real-time shows visits | QA | ☐ |
18 | Send go-live confirmation to client | PM | ☐ |
# | Task | Owner | Done |
19 | Monitor uptime and error logs for 48 hours | Backend | ☐ |
20 | PageSpeed check on live site | QA | ☐ |
21 | Confirm daily backups running | Backend | ☐ |
22 | Training session held and recorded | PM | ☐ |
23 | Handover document delivered | PM | ☐ |
24 | Raise M4 invoice | PM | ☐ |
The old website stays on the old hosting for 7 days. If a critical problem cannot be fixed within 2 hours of launch, DNS is switched back to the old server (live again within 5–10 minutes because of the lowered TTL), and a new launch date is agreed with the client.
WEB-2026-01/GLC · v1.0 · Internal. Bracketed items such as [Client Name] are placeholders.
Next lesson: 36. Handover Document and User Guide