Project timeline template

What’s inside

• Project header — goal, launch date, owner, and hours per week you can give it.
• Phases — for example Discover, Design, Build, Launch, each with a start and end date.
• Milestones — checkpoints someone else can see: “wireframe approved”.
• Task table — task, phase, estimate, due date, owner, depends on.
• Hours check — total estimate against weeks × weekly hours, with a 20% buffer.

When to use it (and when not)

Use it for projects with a fixed date and several stages: a website launch, a product drop, a client deliverable, a thesis chapter, an event. It is most useful when other people depend on your milestones.

For team projects with many parallel workstreams, a dedicated project management tool with Gantt charts and resource views will do more than this template. For anything under two weeks, a weekly planner is enough.

How to use it

1. Fix the launch date and write the goal in one line.
2. List the phases backwards from launch. Give each a date range.
3. Set milestones at the end of each phase.
4. Break phases into tasks of 2 hours or less where you can, and estimate each.
5. Mark dependencies. “Build homepage” depends on “wireframe approved”.
6. Run the hours check. Add 20% buffer. If it does not fit, cut scope or move the date now, not in week five.
7. Review weekly. Compare actual progress with the next milestone.

How Needt fills it in

Create the project in Needt and add tasks with estimates and deadlines — “build product page, 3h, by Nov 3 #Website”. Subtasks hold the smaller steps. Auto-scheduling spreads the work across the weeks before each deadline, in free time around your meetings and other projects, so the hours check happens on your real calendar. The Workspace Kanban or Flow view shows phases at a glance.

When a milestone slips, the later tasks reschedule and Needt shows what moved. To build the first draft, ask:

Create a timeline for the shop website relaunch on Nov 10: discovery, design, build, launch. Estimate the tasks and flag if it doesn’t fit around my client work.

Keep the brief and decisions in a Doc linked to the project.

A worked example

Alex’s shop website relaunch, Nov 10. Six hours a week available.

Total 27 hours plus a 20% buffer is about 32 hours. Just over four weeks at six hours is about 26. It does not fit, so Alex cuts the blog migration and moves it to after launch.