15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →
Templates / Project

Free To Do List Template

A to do list project breaks work into stages, with checklist cards for each step from onboarding through post-launch handoff.

To Do List template preview

Language:

en

Last updated:

October 2026

Share template

Launch work tends to sprawl fast: pages, redirects, checkout rules, and all the little checks that stop a release from turning into a late-night scramble. The to do list keeps the work in one place, in the order it needs to happen, so a rebuild doesn’t skip the steps that protect day-one operations. The board uses dusty rose and industrial green accents under Zilla Slab headings, so each stage reads like a labeled checkpoint rather than a mood board.

Each column holds the actual work, written as cards that move from Onboarding through Post-launch and Handoff. The early cards cover scope, access, and baselines, then the board shifts into design directions and component work, and on into build tasks like CMS permissions, content migration, and shipping, tax, and payment settings. The final columns focus on QA that tests bookings, forms, and checkout end to end, followed by monitoring, fixes, training, and the handoff notes that stop “who has the credentials?” from becoming a launch-week fire drill.

  • Onboarding Cards cover scope and success criteria, access and credentials, and the workspace and communication setup that has to happen before any build work starts.
  • Discovery Cards track the inventory, baseline audits, redirect plan, and content and product collection, so the rebuild doesn’t start without a map of what exists.
  • Design Cards walk through homepage directions, a component library, sign-off on templates, and the assets and style tokens the build needs.
  • Build Cards cover staging setup, theme and component implementation, CMS editing permissions, migrations, and the configuration for payment, shipping, and tax.
  • QA and Launch Cards keep testing and launch steps together, including accessibility checks, end-to-end tests for bookings, forms, and checkout, redirects, and post-deploy smoke tests.

The board comes into your workspace as a project, leaving you to add your own dates and assign the cards to the people doing the work using tasks. Once the cards are assigned, the board becomes the place you check what’s next, what’s blocked, and what’s already verified before anything goes live.

We went from spending hours on every proposal to creating fully customized ones in under 5 minutes. That's not an exaggeration - we timed it.

Yazan & Mawaheb
Yazan & MawahebAgency Owners

What is on this board

6 columns carrying 25 cards. Adding it builds the whole thing as a project in your workspace, with every column and card in place.

ColumnWhat is in it

Onboarding

The column lists the first setup checks, including scope confirmation, access collection, and setting up the workspace and communication channels.

  • Confirm scope and success criteria
  • Collect access and credentials
  • Create project workspace and communication channels

Discovery

The column captures the audit and planning work, from page and media inventory through performance and SEO baselines, redirects, and content and product lists.

  • Inventory existing site pages and media
  • Run performance and SEO baseline audit
  • Map redirects and URL plan
  • Collect content and product lists

Design

The column holds the design checkpoints, including multiple homepage directions, reusable components, final template sign-off, and exporting assets for development.

  • Draft three homepage design directions
  • Build component library and responsive templates
  • Review and sign off final templates
  • Export assets and style tokens for development

Build

The column tracks implementation work like staging setup, theme and component work, CMS editing permissions, content and product migration, and payment, shipping, and tax settings.

  • Set up development environment and staging site
  • Implement theme, templates, and components
  • Configure CMS editing sections and permissions
  • Migrate content and import products
  • Integrate payment, shipping, and tax settings

QA and Launch

The column covers verification and cutover, including cross-device and accessibility testing, end-to-end checks, redirect rules, deployment, and post-launch monitoring.

  • Run cross-device functionality and accessibility tests
  • Test bookings, forms, and checkout end to end
  • Implement redirects and canonical URL rules
  • Execute launch cutover and deploy to production
  • Monitor live site and run post-launch smoke tests

Post-launch and Handoff

The column keeps the cleanup and handoff work visible, including post-launch fixes, CMS and store training, documentation and credentials delivery, and moving into maintenance.

  • Triage and fix post-launch issues
  • Run CMS and store editor training session
  • Deliver handoff documentation and credentials list
  • Arrange ongoing maintenance and start monthly billing

What happens when you install it

  • A project is created with its board, 6 columns and 25 cards already there.
  • Nothing carries a due date, because a board holds the order the work runs in rather than a calendar. The dates go on once you know when the job starts.
  • Every card opens as a task with its own description, assignee, dates, subtasks and files, and columns are renamed, reordered or deleted like any other.

Who it is for

Web developers and studios running frontend development, CMS & WordPress rebuilds, and e-commerce builds that need a clear launch checklist they can assign and track.

Questions about this project template

What should a launch to do list include for a website rebuild?

A website rebuild to do list usually includes onboarding and access, discovery and audits, design sign-off, build tasks, QA and launch checks, and post-launch handoff. This board covers each stage as its own column, with cards that spell out the checks inside it.

How do I organize a website project to avoid launch-day surprises?

Launch-day surprises usually come from missing verification steps, like not testing forms, bookings, checkout, redirects, or accessibility before release. This board keeps those checks in the QA and Launch column, so the work doesn’t jump from build to deploy without a pass.

How many cards are in this to do list project board?

The board includes 25 cards across six columns. The cards already describe the work, so the main changes are assigning owners and adding your own dates.

Does this to do list include SEO redirects and old link planning?

Yes, the discovery work includes mapping redirects and a URL plan, and the QA and launch work includes implementing redirects and canonical URL rules. Those steps sit alongside the other launch checks instead of getting treated as an afterthought.

Does the board cover CMS editing permissions and handoff?

Yes, the build stage includes configuring CMS editing sections and permissions, and the post-launch stage includes a training session plus handoff documentation and a credentials list. The handoff work lives in the same flow as the rest of the launch steps.

Is this to do list a document I send to a client to sign?

No, this template is a project board for running the work, not a proposal or contract. The columns hold the stages of the work, and the cards hold the tasks that move through them.

Start free today

Your entire business, one login away

No credit card required. No contracts. Just the tools you need to run, grow, and automate your business with Super Work AI.

No credit card required

Plutio - Your entire business, one login away