Free Web Design Checklist Template
A web design checklist covers discovery, sitemap and wireframes, UI design, development, QA, and launch handover tasks in order.
Share template
A web build can drift when nobody pins down scope, sign-off points, and what needs to be ready before launch, so drafts keep looping and the go-live keeps moving. The web design checklist runs the work as a board with 25 cards, moving from Project setup and discovery through to Launch, handover and support, so the milestones stay visible and nothing turns into a last-minute scramble.
Each column carries the specific checks that usually trigger delays: who owns content and what gets migrated, when feedback is due, and where approval happens before the next stage starts. The handover end covers the parts clients ask about on day one, like editing training and analytics and cookie consent, and the board keeps those items in the same flow as design and frontend development instead of tacking them on at the end. Workwear green and stamp-ink magenta sit under Space Grotesk headings with Inter body text, so the board reads like a practical plan rather than a mood board.
- Project setup and discovery Cards cover the brief, goals, content ownership, approvals rhythm, and the milestones you’ll track against.
- Sitemap and wireframes Cards move through a structure audit, sitemap, low-fidelity wireframes, and a sign-off point before design starts.
- UI design and component library Cards cover the visual direction, component library and tokens, responsive templates, interactions, and design approval.
- Development and CMS setup Cards cover environment setup, CMS structure, content migration, and integrations for full-stack development work.
- Launch, handover and support Cards cover launch and rollback checks, DNS cutover, post-launch fixes, handover docs, editing training, and closing out invoicing.
In Plutio, the checklist runs as a project with tasks that you assign to whoever’s doing the work, then you add your own dates since the board holds order, not a calendar.
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.
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.
| Column | What is in it |
|---|---|
Project setup and discovery | This column captures the brief and goals, calls out content ownership and migration scope, and pins down the weekly inputs and approvals you’ll need. The last cards turn that into a project plan and milestones before anything gets designed.
|
Sitemap and wireframes | This column moves from an audit of the current structure into a sitemap and primary navigation, then low-fidelity wireframes for key pages. The final cards hold client feedback and sign-off so the structure doesn’t keep changing later.
|
UI design and component library | This column covers the visual direction, homepage mockups, and a component library with design tokens in Figma. The remaining cards create responsive templates and interactions, then capture design approval before build starts.
|
Development and CMS setup | This column covers environment and repository setup, then the CMS structure and content types for cms & wordpress style builds. The later cards handle content migration and the third-party services and payment gateways that often block launch.
|
Staging QA and optimisation | This column covers analytics, GTM, and cookie consent configuration, then testing and bug fixes. The last cards cover proofreading and accessibility checks, plus a client QA list and sign-off before go-live.
|
Launch, handover and support | This column covers the launch checklist and rollback plan, DNS cutover, and post-launch monitoring. The remaining cards cover handover documentation, editing training so the client can keep updating the site, and the final invoice closeout for e-commerce builds.
|
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 designers, studios, and project managers running website redesigns, CMS rebuilds, and new builds where client sign-off and launch readiness need to stay explicit.
Questions about this project template
What should be on a web design checklist?
A web design checklist usually covers discovery, sitemap and wireframes, UI design, development and CMS setup, staging QA, and launch handover steps. This board keeps those stages in order and breaks them into cards, including sign-offs before the next stage starts.
How do you stop a website project from dragging on?
A website project drags on when scope, content ownership, and feedback timing stay vague, so drafts loop without a decision point. The checklist includes cards for defining weekly inputs and approvals and for getting wireframe, design, and QA sign-off before moving forward.
Who writes and migrates the website content?
Content ownership and migration scope need to be agreed early, because content delays can block design, development, and QA. The first column includes cards to confirm who owns content and what gets migrated, and the build column includes a content migration step into the CMS.
What do clients need to provide each week to hit a launch date?
Clients usually need to provide inputs, reviews, and approvals on a predictable cadence, or the work stalls between stages. The discovery column includes a weekly inputs and approvals schedule so feedback and sign-off don’t get left to chance.
Can a client update their website without hiring the designer?
A client can update pages without calling the designer when the CMS structure is set up and the handover includes editing guidance. The final column includes handover documentation and editing training as part of closing out the build.
What needs to be done for cookies, tracking, and GA4?
Cookie consent and tracking setup usually happen during staging, alongside QA, because changes are easier to test before launch. The staging QA column includes analytics, GTM, and cookie consent configuration, then testing and sign-off.
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
