
CI/CD pipeline diagram template
Eight stages with checks and time budgets · Canary promotion with a rollback branch · Example limits and pipeline rules
Preview and use template →A feature launch checklist keeps every team's preparation visible in one place, so nothing is found missing on launch day. This example for a shared calendars feature sets milestones from four weeks before release to two weeks after, gives five teams their own tickable tasks and records the go or no-go criteria and decision owners.
No account needed · Opens as your own editable page

Start from the launch date and place each milestone by working back. Lead times for docs, translations and marketing assets are often longer than engineering expects, so they set the real start date.
Ask each team lead to edit their own checklist rather than writing it for them. People commit to tasks they have written, and they know which steps are easy to forget.
Write measurable criteria before the beta starts, not in the week before launch. Criteria written late tend to be bent to fit a date everyone has already announced.
Yes. Click a checkbox in the editor to mark a task done, and rename the five team lists to match who owns each area in your launch.
No. Open the template and edit it in your browser. Your work saves on this device. An account is optional if you want to sync your workspace.
Yes. Use Export in the editor to save a PNG, SVG or PDF, or download an editable .epicdraw backup.