Projects template
A board for a client website project in six stages: agree scope and a change process in writing, name one client approver per stage, get written sign-off on the sitemap, the designs and the staging site, and plan the launch with a way to undo it.
No account and no email needed. Opens in Excel or Google Sheets.
Fifteen tasks across six stages, each with a completion criterion and its own checklist, plus a suggested day. The sign-off points are explicit because they are where client projects actually go wrong: an unapproved sitemap turns into a redesign, and a launch without a rollback turns into a long evening.
Client website projects rarely fail on the build. They fail because scope was a conversation, content arrives three weeks late from someone who never agreed to write it, and the person who approves the design turns out not to be the person whose opinion counts.
What that looks like
A freelance web designer or small agency that builds websites for clients.
Group is the stage of the project: discovery and scope, content and structure, design, build, testing and launch, handover and review. Status and priority already use the product's own fixed values, so they map without edits.
Download the CSV
It opens in Excel or Google Sheets. Edit the tasks first if you like, or import it as it is.
Create a board in TaskSiddhi
Give it a name, such as the week, the project or the client.
Open the spreadsheet import
Upload the CSV. Columns are matched automatically; map Group, Done when and Checklist to a text column or to custom fields.
Preview, then import
Check the rows before anything is written, then import.
Make it yours
Copy the board once per client project. Fill in the approver names in stage one before you start stage two: the later sign-offs depend on them.
All fifteen tasks, with their completion criteria and checklists. Owner and due date are left blank on purpose.
15 tasks in 6 groups, 61 checklist items
Ask why the site is needed, who it is for, what success looks like and which pages are essential, and write the answers into one brief the client confirms.
Done when
A brief records the goals, audience, success measures and must-have pages, and the client has confirmed it in writing.
Checklist0 of 5 ticked
List what is included and excluded, the number of feedback rounds, and how a request beyond scope is priced and approved, so extra work is decided before it is done.
Done when
A written scope states inclusions, exclusions, the number of feedback rounds and the change-request process, and the client has agreed it in writing.
Checklist0 of 4 ticked
For each stage choose one person on the client side who gives approval and agree how long they have to respond, so feedback arrives from one voice.
Done when
Each stage has one named client approver role and an agreed response time, and the client has acknowledged both.
Checklist0 of 3 ticked
List the text, images, logos, product data and other material the site needs, name who supplies each and by when, and state what happens to the timeline if an item is late.
Done when
A content list names each item, who supplies it, its due date and the effect of lateness on the timeline, and each required item is later received and approved, or its omission and its effect on scope and launch are agreed before build starts.
Checklist0 of 4 ticked
For every asset note the stated licence or permission, where it came from and any unresolved restriction. An asset with an unresolved restriction is excluded or replaced; this is not legal clearance.
Done when
Each asset has a recorded source, stated licence or permission and any unresolved restriction, and every asset with an unresolved restriction is excluded or replaced.
Checklist0 of 4 ticked
Sketch the pages and how they link, mark which are built first, and send them to the client's approver for approval before any design starts.
Done when
A sitemap and page list exist with the build order marked, and the client's approver has approved them in writing.
Checklist0 of 3 ticked
Share layouts for the main pages and ask the client's approver for one consolidated set of comments per feedback round agreed in the scope, not separate comments from several people.
Done when
Layouts for the key pages have been shared, one consolidated set of comments has been received for each agreed feedback round, and each comment is marked done, declined or queued.
Checklist0 of 3 ticked
Complete the designs for desktop and mobile widths, and send them for sign-off, noting that later changes go through the change-request process.
Done when
Desktop and mobile designs are complete and signed off in writing, with later changes routed through the change-request process.
Checklist0 of 4 ticked
Build on a staging site with access restricted where feasible, set indexing controls and check them, and keep production credentials and sensitive test submissions off the board; record only where access details are kept.
Done when
Staging access is restricted where feasible, indexing controls are configured and checked, and no production credentials or sensitive test submissions are stored on the board.
Checklist0 of 4 ticked
Confirm which forms and optional analytics the client needs. Identify applicable visitor-data and consent requirements, with qualified advice where needed, and configure the agreed controls before enabling any tracking. Test forms with synthetic data.
Done when
A decision on which forms and analytics are needed is recorded, the agreed controls are configured before tracking is enabled, and form delivery is tested with synthetic data with results recorded and no submissions kept on the board; no compliance claim is made.
Checklist0 of 4 ticked
Record the devices and browsers tested, representative page and form test cases, the agreed performance checks and the accessibility checks performed, and give each failure a severity, an owner and a retest result; no compliance claim.
Done when
A test record lists the device and browser matrix, representative page and form cases, agreed performance checks and accessibility checks performed, and each failure has a severity, owner and retest result.
Checklist0 of 4 ticked
Send the staging site to the client's approver with known open issues listed and record written approval and a disposition for each issue; release-blocking security, privacy and core-function failures are fixed and retested first.
Done when
The approver records written approval and a disposition for each known issue, and release-blocking security, privacy and core-function failures are fixed and retested before launch.
Checklist0 of 4 ticked
Record who controls the domain, hosting and certificates, a tested backup or recovery method and who can run it, the redirect list, the switch steps, the rollback rule and the post-launch checks. Review the plan before the switch.
Done when
The plan records domain, hosting and certificate control, a tested recovery method and who can execute it, the redirects, switch steps, rollback rule and post-launch check list, and has been reviewed before the switch.
Checklist0 of 6 ticked
Execute the switch, check representative pages, redirects, forms and the certificate on the live site, record failures, and record the decision to fix forward or roll back.
Done when
The switch is executed and representative pages, redirects, form delivery and the certificate are checked on the live site, failures are recorded, and the decision to fix or roll back is recorded.
Checklist0 of 4 ticked
Give the client the documents and account transfers the agreement provides for, show them how to make basic changes, agree the support period, and record whether they accept the project as complete.
Done when
The handover documents and account transfers agreed in the scope are delivered, a short training is held, the support period is agreed, and the client's response is recorded as acceptance, conditional acceptance or rejection.
Checklist0 of 5 ticked
Open a task to see what counts as finished and its checklist. Ticks here are just to try it out and are not saved.
The same rows as a CSV. Columns in the file: Task, Group, Status, Priority, Owner, Due date, Suggested day, Done when, Checklist, Notes.
Download web design workflow (CSV)The measured demand behind this template, and what it does not prove. We publish it so the page cannot be mistaken for a forecast.
| Keyword | India | US | UK | UAE |
|---|---|---|---|---|
| web design workflow(target) | 40 | 110 | 20 | 10 |
A freelance designer or small agency looking for a process to run client work. The measured volume is small, so this page exists for the people who search the phrase rather than as a traffic bet.
What we hold this page to
Thin or mismatched demand — no traffic expectation
Not checked for this template.
No. It covers the project around the design: scope, approvals, content, sign-offs, testing, launch and handover. What you design and how you design it is yours; this board exists so the process does not eat the design time.
Because the most expensive delay in client work is contradictory feedback from several people with no tie-breaker. Naming one approver per stage does not stop others commenting, it just makes clear whose approval ends the stage.
Then make that a task with their name and a date on it, which is exactly what stage two does. Content is the single most common reason these projects stall, and it stalls precisely when nobody owns it.
Yes. The stages are the same; discovery just includes an audit of what exists and what must be preserved, such as URLs and redirects. Add those as tasks in stage one.
Use the change process you agreed in stage one: record the change, its cost and its effect on the dates, and get the stage approver to accept it before the work starts.
See approvalsImport the template, assign owners and see what is overdue at a glance. Free, with no paid plan.
Not sure it fits? See who TaskSiddhi is for
