Free Project Plan Template
A project plan covers the work stages, the tasks in each stage, and who owns them, so a team can run delivery in order.
Share template
The handoff happens, the work starts, and suddenly progress lives in half a dozen places, leaving a client unsure what’s next and a team chasing loose ends. This project plan turns delivery into a single board, so the work moves in a clear order and nothing important vanishes between “nearly done” and “live.”
The board runs from Kickoff and content through Launch and handover, with 24 cards that spell out what gets done at each step, from content checklists and wireframes to forms testing and post-launch checks. Raleway headings sit over Roboto body text, with deep aubergine for structure and a wayfinding green accent that keeps the next step easy to spot without turning the plan into a sales page.
- Kickoff and content Starts the board with the kickoff call, content and access requests, and a gap check before the sitemap work begins.
- Sitemap and design Holds the sitemap and wireframe tasks, including a sign-off card so the build doesn’t start on moving targets.
- Build on staging Groups the build tasks on a staging setup, from WordPress configuration through theme work and the site build items.
- Testing and optimisation Tracks the checks that catch broken forms and tracking before launch, including notifications, Core Web Vitals, and basic SEO.
- Launch and handover Finishes with deployment, post-launch checks, the handover session, and the final invoice step for the remaining 70%.
Kickoff and content Cards cover the kickoff call, access and content requests, and a review pass to flag gaps before design starts. Sitemap and design Cards move through sitemap and page list work, wireframes, and a sign-off point before build. Build on staging Cards cover the staging setup and build work, including WordPress setup, theme work, and optional site build pieces. Testing and optimisation Cards focus on cross-browser checks, forms and notifications, Core Web Vitals, basic SEO, and analytics. Launch and handover Cards cover go-live prep, deployment, post-launch monitoring, a handover and editing demo, support contacts, and the final invoice step for the remaining 70%. Once the template is in your workspace, you add your own dates (since the board shows the order, not a calendar) and assign the cards to whoever’s doing the work, so the plan doubles as a day-to-day run sheet instead of a document that gets filed and forgotten.
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
5 columns carrying 24 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 |
|---|---|
Kickoff and content | Cards cover the kickoff call, the content and access checklist, and a review pass that flags gaps before design starts.
|
Sitemap and design | Cards move from drafting the sitemap and page list into wireframes, then stop for sign-off before build begins.
|
Build on staging | Cards cover staging setup and development work, including WordPress configuration, theme development, and the site build tasks.
|
Testing and optimisation | Cards run through cross-browser checks, forms and email notifications, Core Web Vitals work, basic SEO, and analytics setup.
|
Launch and handover | Cards cover go-live prep, deployment, post-launch checks, the handover and editing demo, and the final invoice step for the remaining 70%.
|
What happens when you install it
- A project is created with its board, 5 columns and 24 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 design and development teams doing frontend development work, cms & wordpress builds, or e-commerce builds where a client wants clear handover and fewer post-launch surprises.
More project plan templates
More virtual assistant templates
See all 35 templates
Questions about this project template
What should a project plan include for a website build?
A website build project plan usually breaks the work into stages, then lists the specific tasks inside each stage and who owns them. This board runs from kickoff and content through launch and handover, with cards for sitemap, build, testing, and go-live steps.
How do you structure a website project from kickoff to launch?
A common structure is kickoff and content first, then sitemap and design, then the build, then testing, then launch and handover. This template follows that order so the work moves left to right without mixing build tasks into discovery.
What do you need from a client before starting a website project?
Projects typically need access and content early, plus agreement on goals and what pages are getting built. The first column includes cards for the kickoff call, sending content and access checklists, and reviewing what comes back to flag gaps.
Who should be assigned to tasks in a project plan?
Each task needs an owner so work doesn’t sit in a column with nobody responsible for it. The template expects you to add the people doing the work to the project and assign the cards to them.
How do you make sure website forms work after launch?
Form testing needs to cover submission, notification emails, and any tracking tied to enquiries. The testing column includes cards for forms and email notifications, plus analytics and conversion tracking setup before launch.
What happens after a website goes live if something breaks?
Post-launch work usually includes checks, monitoring for errors, and a clear support contact plan. The final column includes post-launch checks and monitoring, plus a post-launch support plan and contacts as part of handover.
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
