Website project timeline template
By The Onbo team · Updated
Short answer
A useful website timeline lists each phase with its dates, and marks the client's inputs, approvals and payments as milestones alongside your work. When clients can see that design starts after the deposit and build starts after content arrives, the launch date becomes something you plan together rather than a promise you alone have to keep.
Most website timelines show only the designer’s work: design, build, launch. The dates that actually decide the launch, when the client sends content and approves designs, are invisible. This template puts both on the same page, so everyone can see what moves the date.
How to use this template
Copy the table below into a document or spreadsheet. Fill in the dates backwards from a target launch, or forwards from the deposit date. Share it with the client at the website project kickoff and update it whenever a milestone moves. Keep your internal tasks in your project tool; this timeline is the shared, client-facing version.
The website project timeline template
| Phase | Your work | Client input or approval | Payment milestone | Planned date | Actual date |
|---|---|---|---|---|---|
| 1. Onboarding | Send agreement, invoice and questionnaire | Accept agreement, pay deposit, answer questionnaire, send brand files | Deposit | [date] | |
| 2. Discovery | Draft sitemap and content plan | Approve sitemap, confirm content owners | [date] | ||
| 3. Design | First concept, then revisions | Feedback on concept; approve final design | Design approval payment | [date] | |
| 4. Content | Supply or edit agreed copy | Deliver page content by agreed dates | [date] | ||
| 5. Build | Build pages and features | Provide access by invite; review staging site | [date] | ||
| 6. Review and testing | Fix issues, test devices and forms | Final review and sign-off | [date] | ||
| 7. Launch | Go live, check analytics and forms | Approve launch; make DNS changes or delegate them | Final payment | [date] | |
| 8. After launch | Training and handover | Confirm handover complete | [date] |
Add rows for anything specific to the project, such as an online shop setup or a copywriting add-on.
Why show client inputs as milestones?
- Clients see their part. Few clients realise how much the timeline depends on them until it’s written down.
- Delays have a clear cause. If content arrives two weeks late, the launch moving two weeks is visible and fair.
- Payments match progress. A payment at design approval rewards the milestone both sides care about.
- Conversations get easier. “We’re waiting on the About page” points to a row, not a person.
For example, a two-person web studio might share this timeline at kickoff with the content due date three weeks out. When the client’s copy is a week late, the studio moves the build and launch rows by a week and sends the updated table, and the client agrees without a difficult call because the reason is on the page.
How do you set realistic dates?
- Start from the client’s real deadline, if there is one, and check whether it’s fixed.
- Give each phase enough time for your capacity, including other projects.
- Give the client realistic input windows. Writing page copy takes longer than most clients expect.
- Allow time for approvals. A review that needs three people rarely happens in a day.
- Add buffer before launch, not scattered through the plan.
Agree in your agreement what happens when client inputs are late: the timeline moves, a placeholder is used, or extra work is quoted.
How do you share the timeline with clients?
Send it as part of the kickoff summary, then again whenever a date moves, with a one-line note on why. Keep the format the same each time so the client learns to read it at a glance. A shared document both of you can open works well; so does a simple PDF attached to the update. What matters is that the client always knows which version is current and what they need to do next.
A timeline checklist
- Every phase has a planned date
- Every client input has its own dated row
- Approvals name the person who approves
- Payments are tied to milestones
- Late-input rules are written in the agreement
- Buffer is placed before launch
- The client has a copy from kickoff
- Actual dates are filled in as you go
- Changes are sent to the client in writing
- The timeline is reviewed at each milestone
For what to collect before phase 1 ends, use the website client onboarding checklist. Our guide on how to collect and organize client requirements covers turning questionnaire answers into the brief behind phase 2.
Where Onbo fits
Onbo covers phase 1 from one link. Your client accepts the agreement, pays the deposit through your own payment link, with later payments such as design approval and launch scheduled on the same invoice, answers your questionnaire and uploads brand files into your Google Drive. Reminders follow up on unfinished steps, so the onboarding row finishes on time more often. Try it free for 30 days; see pricing.
Questions
How long does a website project take?
It depends on size, features and how quickly the client supplies content and approvals. Build your timeline from the phases and the client's input dates rather than quoting a fixed number of weeks.
What are the phases of a website project?
Onboarding, discovery and sitemap, design, content, build, review and testing, and launch, with client inputs and approvals between them.
How do I stop a website timeline slipping?
Show client inputs as dated milestones, tie payments to approvals, and agree in writing what happens to the dates when an input arrives late.