Website Project Plan Template for Agencies (With Timeline)
Last updated: November 18, 2026
A website project plan lists each phase of the build, what it produces, who owns it, when the client gives input, and when they sign off. For an agency it also sets the rules that keep those dates true: how many feedback rounds, how changes are priced, and how much time testing gets. Copy the template below or download it.
This guide is for agency owners and project leads planning a client website. A plan earns its keep when things change: in PMI’s 2018 Pulse of the Profession, 52% of projects completed in the previous 12 months had scope creep, up from 43% five years earlier, and erroneous requirements gathering was among the top three causes of project failure. A plan that names the scope, the rounds, and the change process makes those problems visible early.
What a Website Project Plan Includes
| Part | What it settles |
|---|---|
| Project | The client, the one person who approves, the start date, and the launch date. |
| Goals | What the site must do, and how success will be measured after launch. |
| Scope | Pages and templates, the screen widths designed for, and what is not included. |
| Phases | Each phase’s deliverable, owner, client input date, and sign-off date. |
| Feedback rounds | How many rounds each phase includes, how many days each round gets, and how feedback is given. |
| Change process | How new requests are priced and who approves them. |
| Testing and launch | The kinds of testing, the testing window, and who owns the launch checklist. |
| Risks | What could move the dates, and what you will do about each. |
| Sign-off | The agency and client both agree the plan before work starts. |
Website Project Plan Template
One row per phase. Fill in the owner, the date the client’s input is due, and the date they sign off. The phases follow the website design process.
| Phase | Deliverable | Owner | Client input | Client signs off |
|---|---|---|---|---|
| Discovery | Written brief | Project lead | Questionnaire answers, kickoff call | The brief |
| Sitemap and content | Sitemap and content plan | Project lead, writer | Page list, copy owner and due dates | The page list |
| Wireframes | Wireframes for each page type | Designer | One round of feedback per page type | Layout and hierarchy |
| Visual design | Design files for each page type | Designer | Brand files, feedback rounds | The look |
| Build | Staging site | Developer | Final copy and images | Nothing yet |
| Testing and review | Fixed issues, UAT results | Test lead, developer | Feedback rounds, user acceptance testing | Ready to launch |
| Launch | Live site, handover notes | Developer, project lead | Domain and hosting access | Project complete |
Get the website project plan as a two-page PDF: project, goals, scope, phases, feedback rounds, change process, testing, risks, and sign-off.
Example Timeline for a 10-Page Website
Here is the template turned into weeks for a small marketing site with two rounds of feedback on design and two rounds of testing. It is an example to adapt, not a benchmark: build yours from your page count, how fast content arrives, and the rounds you include.
| Week | Phase | Client input due | Sign-off |
|---|---|---|---|
| 1 | Discovery | Questionnaire answers, kickoff call | Brief |
| 2 | Sitemap and content | Page list approved, copy owner named | Page list |
| 3 to 4 | Wireframes | Feedback round 1 and round 2 | Layout |
| 4 to 6 | Visual design | Feedback round 1 and round 2; final copy due | Look |
| 6 to 9 | Build on staging | Images and remaining content | None |
| 9 to 11 | Testing and review | Client review round, then UAT | Ready to launch |
| 12 | Launch and handover | Domain and hosting access | Project complete |
Build Feedback Rounds Into the Timeline
- Give each round a length. “Three working days per round” is a date the plan can hold. “When you get a chance” is not.
- Count the rounds per phase. Write the number in the plan, and what an extra round costs.
- Name one approver. One person on the client side settles conflicting comments and signs off each phase.
- Ask for feedback in one place. Comments spread across email, chat, and calls take time to collect and are easy to miss. See how to ask for client feedback and how to manage client feedback.
Plan for Change
Every client project changes. The plan decides how. Agree at kickoff that requests outside the scope come back with their time and cost before anyone builds them, and that the client approves each one in writing. On a fixed budget, offer a swap: PMI quotes Jesse Fewell’s dynamic scope option, “You can replace any not-started deliverable with anything of equal or lesser cost.” Our guide on how to handle scope creep has replies you can use.
Plan Testing Time Honestly
Give testing its own weeks, so a fixed launch date cannot quietly squeeze it, and plan at least two rounds: one to find problems and one to confirm the fixes. Put the targets in the plan, such as WCAG 2.2 level AA for accessibility and the “good” Core Web Vitals thresholds for speed, so “ready” means the same thing to everyone. A test plan covers the details.
How to Keep the Plan True
- Send the plan again whenever a date moves. A plan the client has not seen since kickoff is not a shared plan.
- Track planned against actual. Note the date each input actually arrived, so a slip has a visible cause.
- Log decisions as they happen. Approvals, declined requests, and changes, with the date and who decided.
- Review risks weekly. Late content and new reviewers are easier to handle when you see them coming.
Where a Feedback Tool Helps
In the testing and review phase, the client reviews the built site. In OverlayQA, clients comment on the staging site through a review link with no account or extension, and click Done reviewing when their round is finished, so the plan’s rounds have a clear end. Each comment arrives as an issue with a screenshot, the page address, browser, and screen size, in one list with the bugs your team finds.
Frequently Asked Questions
What should a website project plan include?
The project and approver, goals, scope, phases with owners and sign-off dates, feedback rounds, the change process, testing and launch, risks, and the sign-off of the plan itself.
How long does a website project take?
It depends on the number of pages, how fast content arrives, and how many feedback rounds are included. Build the timeline from those, and plan at least two rounds of testing.
Who should write the website project plan?
The agency’s project lead, with input from the designer and developer on durations. The client approver should agree it before work starts.
What is the difference between a project plan and a scope of work?
The scope of work says what will be delivered. The project plan says how and when: phases, owners, dates, feedback rounds, and the process for changes.
How many feedback rounds should a website project include?
There is no standard number. Pick one per phase, write it in the plan with the days each round gets, and state the price of an extra round.
What do you do when the plan slips?
Name the cause, update the dates, and send the revised plan to the client the same week. If the slip comes from new work, treat it as a change request rather than absorbing it.
Give every feedback round a clear end. With OverlayQA, clients comment on the page with no account and click Done reviewing when their round is finished.