Project timeline templates: how to show the plan on a single page

A plan timeline has one job: let someone who was not in the planning meeting see, in under a minute, what happens when, who owns it, and which date the whole project depends on. Most timelines fail that test not because of the tool, but because they try to show every task. The fix is to decide what goes on the page before choosing a template.

This article gives a one page structure that works in any tool, a filled-in example you can copy, the steps to build it in Excel and Microsoft Project using the names those programs show on screen, and a short comparison of which project management tools include a timeline view on their free plans (checked on October 8, 2026).

What a one page plan timeline must show

Templates differ in color and layout, but the useful ones all carry the same five kinds of information. If one of these is missing, readers will come back with questions. If more than these are present, the page stops fitting.

1. Phases

Group the work into four to seven phases, such as Discovery, Design, Build, Test and Launch. A phase is a band of time, not a task. Fewer than four phases usually hides where the risk is. More than seven makes the page too dense to read at a glance.

2. Milestones

A milestone is a date when something is decided, delivered or approved: "Design sign-off", "Beta to 20 customers", "Go live". It has no duration. Three to eight milestones is a good range for a project of a few months. Each one should be something a person outside the team can check.

3. Owners

Every phase and every milestone needs one name next to it. Not a team, a person. A timeline without owners is a schedule nobody is responsible for.

4. The dependency that matters

Do not draw every dependency. Draw the one or two where a slip moves the end date, for example "Build cannot start until the API contract is signed". Readers need to know where the critical path is, not every arrow.

5. Today

Mark the current date. A timeline without a "today" line forces every reader to work out how far along the project is, and they will each get a different answer.

Everything else, such as individual tasks, hours, budgets and detailed notes, belongs in the task list or the board behind the timeline, not on the page.

A copyable plan timeline template

The structure below works as a table in a document, a spreadsheet, or the first slide of a status deck. The example is a twelve week launch of a customer portal. Replace the rows with your own.

Phase	Weeks	Owner	Milestone at the end	Depends on
Discovery	1 to 2	Product lead	Scope agreed with sponsor	None
Design	3 to 4	Design lead	Design sign-off	Scope agreed
Build	5 to 9	Engineering lead	Feature complete	Design sign-off, API contract
Test	9 to 10	QA lead	Beta to 20 customers	Feature complete
Launch	11 to 12	Product lead	Go live	Beta feedback resolved

Then add three lines under the table:

• Critical date: API contract signed by the end of week 4. If it slips, Build and Go live move by the same amount.
• Today: Week 6, Build in progress.
• Biggest open risk: Payment provider review not yet scheduled.

That is the whole page. It fits on one screen, it prints on one sheet, and it answers the questions a sponsor actually asks.

Turning the table into a visual timeline

If the audience prefers a picture, draw one horizontal bar per phase across a row of weeks, place each milestone as a diamond at the end of its phase, and draw a vertical line at today. Keep the phase names on the bars rather than in a legend. Use one color for the whole timeline and a second color only for the phase that is at risk. Color that means nothing makes the at-risk phase harder to spot.

Building it in Excel

Microsoft offers a gallery of free timeline templates for Excel. On the template page, the timeline set includes "Four-week project timeline", "Detailed project timeline", "Project timeline with milestones", "Work plan timeline", "Milestone and task project timeline" and "Date tracker Gantt chart", among others. Microsoft's instructions for Excel for the web are short: open the timeline templates and double click a template to start editing.

A practical sequence:

1. Pick "Project timeline with milestones" if the project has clear decision points, or "Four-week project timeline" for a short piece of work.
2. Delete the sample tasks, then enter your phases first, with start and end dates.
3. Add milestones as zero length items at the end of each phase.
4. Add a column for the owner if the template does not have one.
5. Insert a vertical line or a conditional format for today's date.
6. Set the print area to one page in landscape before sharing.

Excel's strength is that everyone can open the file. Its weakness is that the timeline is a separate artifact. When a phase moves on the task list, someone has to move it on the timeline by hand, and after a few weeks the two drift apart.

Building it in Microsoft Project

Microsoft Project generates the timeline from the schedule, which removes the drift problem. Microsoft's support article "Create a timeline in Project" describes the steps:

1. The timeline is on by default most of the time and appears above the current view. If it is not showing, select View, then select Timeline.
2. Right-click a task and select Add to Timeline. Repeat for each phase and milestone you want on the page. This is where the one page discipline matters: add the phases and milestones, not every task.
3. To show a second timeline, for example one row per workstream, select the Timeline view, then Timeline Format and Timeline Bar. Right-click a timeline and choose Date Range to set its own start and finish.
4. To make a milestone stand out, select it and choose Timeline Format, then Display as Callout. Drag tasks up or down to put them on separate rows.
5. Change colors with Background Color and pick a date format under Timeline Format, then Date Format. The same list can remove dates from the timeline entirely.

Microsoft also notes that pasting the timeline into Word, PowerPoint, Outlook, Excel or Visio gives more formatting options. For a status deck, that paste is the usual last step.

The trade-off with Project is access. The timeline is easy to keep accurate, but only people with the software and the file can update it.

Timeline views in project management tools

Many teams no longer keep a separate timeline file at all. They use a timeline or Gantt view inside the same tool that holds their tasks, so the picture updates when the work does. Whether that view is on the free plan varies. The table below is taken from each vendor's pricing page on October 8, 2026.

Tool	Free plan	Timeline or Gantt on the free plan	Where it becomes available
Jira	Up to 10 users	Timeline view included	Free
Asana	Personal, 2 users	Not included (list, board and calendar only)	Starter, $10.99 per user per month billed annually
ClickUp	Free Forever	Gantt and Timeline views, 60 uses each	Gantt unlimited on Unlimited; Timeline unlimited on Business
GitHub Projects	GitHub Free	Roadmap layout included	Free

Two points are worth checking before relying on a tool's timeline for a one page view.

Can it hide detail? A timeline view that shows every task is just a Gantt chart. Look for a way to filter to phases and milestones only, or to group by phase.

Can someone outside the team see it? The point of a plan timeline is to share it. If the sponsor or client needs a paid seat or a full account to open it, a pasted image may still be the practical answer.

For tools that put kanban, Gantt and calendar views on the same cards, the feature list and the comparisons page show which views are included without an upgrade.

Matching the format to the audience

The same plan often needs two or three versions of the timeline. Trying to make one page serve everyone is how timelines end up crowded.

Sponsors and leadership want the end date, the next milestone and whether anything is at risk. For them, the five row table above with the three lines underneath is usually enough. A visual bar chart is optional.

The delivery team wants to see overlaps. When Build and Test share a week, the team needs to know who is doing both. A timeline with one row per workstream, rather than one row per phase, shows those overlaps better. Microsoft Project's second timeline bar, or a timeline view grouped by assignee in a task tool, fits this case.

Clients and outside partners want to know what they have to provide and when. Add a row for client actions, such as "content delivered" or "feedback on design", and give it its own color. Most delays on client work happen at those handoffs, and putting them on the page makes the dependency visible to the people who control it.

A simple rule keeps the versions consistent: build the most detailed one first, then derive the others by hiding rows, never by retyping dates. When the dates live in one place, the versions cannot disagree.

Keeping the timeline honest after week one

The first version of a timeline is always optimistic. What separates a useful timeline from a decorative one is how it is maintained.

Update it on a fixed day. Once a week, before the status meeting, move the today line and adjust any phase that has moved. A timeline updated "when something changes" is updated when someone remembers.

Show slips, do not hide them. When a milestone moves, keep the original date visible, struck through or in a lighter color, next to the new one. Sponsors trust a timeline more when they can see that it has been corrected, and the history makes the next estimate better.

Re-baseline deliberately. If the plan changes so much that the original dates are meaningless, agree a new baseline with the sponsor and record the date of that decision on the page. Quietly redrawing the whole timeline loses the record of what happened.

Keep the page to one page. As the project goes on, the temptation is to add rows. If a new item is important enough to go on the timeline, ask which existing item can come off.

Link it to the work. If the timeline lives in a separate file, put a link to the task board at the top. If it lives in the task tool, make sure the phase bars are driven by the dates on real cards, so that moving a card moves the bar.

What to change first

Take your current plan and cut it down to phases, milestones, owners, one critical dependency and today. If that does not fit on one page, the project has too many phases, not too little space. Then decide where the timeline will live so it is updated on the same day each week. A team that wants Gantt bars that move when the cards move can try Pinateca, which is free for up to 5 people.

Q1. What is the difference between a project timeline and a Gantt chart?

A Gantt chart lists every task with its start, end and dependencies, and is a working tool for the person running the schedule. A project timeline shows only phases and milestones so that people outside the team can understand the plan at a glance. Many tools produce the timeline from the same data as the Gantt chart.

Q2. How many milestones should a plan timeline have?

For a project of a few months, three to eight is a workable range. Each milestone should be a decision, delivery or approval that someone outside the team can verify. If there are more than that, some of them are probably tasks.

Q3. Is there a free project timeline template in Excel?

Yes. Microsoft publishes free timeline templates for Excel, including "Project timeline with milestones", "Four-week project timeline" and "Date tracker Gantt chart". In Excel for the web, open the timeline templates and double click one to start editing.

Q4. How do I add a task to the timeline in Microsoft Project?

Right-click the task and select Add to Timeline. If the timeline is not visible, select View and then Timeline. Repeat for each phase or milestone you want on the page.

Q5. Does Asana's free plan include a timeline view?

Asana's free Personal plan lists list, board and calendar views. Timeline and Gantt views are listed from the Starter plan, which costs $10.99 per user per month billed annually, according to Asana's pricing page on October 8, 2026.