- Launch item
- Home screen and intro
- Category
- Page
- Assignee
- Empty
- Prep
- Empty
Work & projects · Launch check
Small pre-launch checklist
When you check for gaps before opening a page, service, or event to the public
Only you can see the new document. Checks and statuses start empty, and share links, polls and surveys open when you publish them yourself.
Small pre-launch checklist
- Launch target
- Not set
- Planned launch
- Not set
- Overall lead
- Not set
- Type
- Not set
- Status
- Not set
Write down what you're launching, then start by checking the first-use flow.
Launch scope
Decide what goes out to whom, and who will check if something goes wrong.
| Launch item | CategoryLabels | AssigneeAssignee | PrepStatus |
|---|---|---|---|
| Home screen and intro | Page | Empty | Empty |
| One core feature | Feature | Empty | Empty |
| Notices and guide text | Guide | Empty | Empty |
- Launch item
- One core feature
- Category
- Feature
- Assignee
- Empty
- Prep
- Empty
- Launch item
- Notices and guide text
- Category
- Guide
- Assignee
- Empty
- Prep
- Empty
Final checks before launch
Go through the key user flow, the announcements, and your response plan yourself, then check them off.
Pre-launch checklist
| Check item | Category | Assignee | Checked | Check by | Evidence & notes |
|---|---|---|---|---|---|
| Check announcements and links | Guide | Not set | Unchecked | Not set | Look for wrong info and broken links |
| Confirm how to respond to problems | Operations | Not set | Unchecked | Not set | Confirm who's responsible and how to roll back |
| Check the mobile screen | Usability | Not set | Unchecked | Not set | Check for clipping on small screens |
| Try the key flow yourself | Usability | Not set | Unchecked | Not set | Check everything from start to finish |
| Check permissions and personal data exposure | Security | Not set | Unchecked | Not set | Make sure nothing that shouldn't be visible is |
- Category
- Guide
- Assignee
- Not set
- Checked
- Unchecked
- Check by
- Not set
- Evidence & notes
- Look for wrong info and broken links
- Category
- Operations
- Assignee
- Not set
- Checked
- Unchecked
- Check by
- Not set
- Evidence & notes
- Confirm who's responsible and how to roll back
- Category
- Usability
- Assignee
- Not set
- Checked
- Unchecked
- Check by
- Not set
- Evidence & notes
- Check for clipping on small screens
- Category
- Usability
- Assignee
- Not set
- Checked
- Unchecked
- Check by
- Not set
- Evidence & notes
- Check everything from start to finish
- Category
- Security
- Assignee
- Not set
- Checked
- Unchecked
- Check by
- Not set
- Evidence & notes
- Make sure nothing that shouldn't be visible is
If something goes wrong
Deciding who moves first for each severity keeps everyone calm.
| Situation | SeverityLabels | Response ownerAssignee | Response readyStatus |
|---|---|---|---|
| The core flow stops | High | Empty | Empty |
| Guide text is wrong | Medium | Empty | Empty |
| Minor display glitch | Low | Empty | Empty |
- Situation
- The core flow stops
- Severity
- High
- Response owner
- Empty
- Response ready
- Empty
- Situation
- Guide text is wrong
- Severity
- Medium
- Response owner
- Empty
- Response ready
- Empty
- Situation
- Minor display glitch
- Severity
- Low
- Response owner
- Empty
- Response ready
- Empty
1.
Whoever spots the problem tells the response owner.
2.
Decide within 10 minutes whether to roll back or fix.
3.
After acting, check the same flow again.
Launch timing
Pick a time together when you can check without rushing.
When should we launch?
- Weekday morning
- Weekday afternoon
- Weekend
Launch timing and owner
☐
Every checklist item was checked in person.
☐
The response owner knows the launch timing.
☐
I shared the final prep details with everyone involved.