Create a timeline view for a project

Quick answer

Prepare separate task, start-date and end-date columns, then use Insert > Timeline on a computer. In the timeline’s Settings, map each column explicitly. Test the result by extending one task’s end date in the source, rather than treating a plausible-looking card as proof that the dates were interpreted correctly.

Check availability first

Google lists timeline view for Workspace Essentials; Business Starter, Standard and Plus; Enterprise Essentials, Starter, Standard and Plus; Education Fundamentals, Standard and Plus; and Frontline. This guide does not promise availability in a personal account or under every organization policy. Check the command in your intended account before preparing production data.

The instructions cover desktop web creation and editing. Android and iOS can display timeline views, but that does not establish equivalent creation controls. Use a private, disposable project sheet and synthetic tasks. You need permission to edit the source, not simply a screenshot of somebody else’s timeline.

The goal is a three-card project view whose dates, group labels and changed endpoint can all be traced to source cells. This is a schedule visualization, not an automatic dependency engine. Extending one task in this exercise does not instruct Sheets to reschedule the next one.

Build the source fixture

Name the source tab Project. Enter these headers in A1:E1: Task, Start, End, Team, Detail. Then enter:

Row	Task	Start	End	Team	Detail
2	Draft brief	2026-11-02	2026-11-04	Design	Agree the outline
3	Review brief	2026-11-05	2026-11-06	Review	Resolve comments
4	Prepare launch	2026-11-09	2026-11-12	Design	Assemble materials

The dates above describe intended calendar dates. Enter them in the format recognized by your spreadsheet’s locale, and format B2:C4 as dates. If typing the ISO-style text leaves it as text in your setup, use the date picker or an unambiguous locale-supported date entry. Merely applying a date appearance to text is not a reliable conversion.

As a temporary numeric check, put =C2-B2 in F2 and fill down to F4. The expected differences are 2, 1 and 3 days. This checks stored date arithmetic; it is not a statement about inclusive working-day counts or card-width pixels. Remove these temporary checks before creating the timeline, or leave column F outside the selected range.

Create and map the timeline

1. On the computer, choose Insert > Timeline.
2. Set the data range to Project!A1:E4 and click OK.
3. In the new timeline tab, open Settings.
4. Check the data range and assign Card title to Task, Start date to Start, and End date to End.
5. Assign Card detail to Detail and, if desired, Card group to Team.

There should be three source-backed tasks. Two belong to Design and one to Review. Grouping by Team is for visual organization; it does not aggregate the two Design tasks into a single summed duration. If you prefer separate rows for each task, leave the optional grouping unset.

For this exercise use end dates, not Duration. Mixing those two approaches makes the weekend setting harder to interpret. Google’s Duration alternative has its own include-weekends behavior; it is not needed to explain these explicit start and end dates.

Inspect the cards against the source

Select Draft brief and check its title, dates and detail. Repeat with Prepare launch. Confirm that the later task is positioned in the November 9–12 interval rather than merely noticing that it is longer. A timeline using the wrong date column can still look orderly.

Use a simple checklist: three tasks, the expected names, correct date endpoints, correct team assignment, and meaningful details. Do not use color as the only way to distinguish teams. Team text remains available in the source even if someone cannot distinguish the chosen colors.

If you want colors, choose a source column for Card color and apply the intended background colors there. Keep this optional until the dates are correct. Conditional formatting on a source column and direct card-color editing have different interactions; avoid combining them in the first practice file.

Change one endpoint, then reverse it

Select the Prepare launch card and choose Edit Data in its details. This takes you back to the source row. Change C4 from November 12 to November 13, 2026. The start remains November 9, and the date difference becomes 4 rather than 3. Return to the timeline and confirm the same card extends to the new endpoint. The other two source rows should remain unchanged.

As a negative check in the practice file, temporarily make C3 equal B3. The card will not have the same visible span as a valid start-before-end interval. Restore C3 to November 6 before keeping the project. Then restore C4 to November 12. These checks distinguish an endpoint problem from an unrelated display setting.

Troubleshoot and keep the source authoritative

A missing card length can mean equal start/end dates or date text that Sheets did not recognize. Inspect B and C directly and repeat the subtraction check. A missing fourth task added later can mean the data range still ends at row 4; update Settings > Data range deliberately rather than assuming growth.

Wait for the file to save, reopen it, and inspect both the Project tab and timeline. Keep the native Google Sheets file as the interactive version. If you distribute a downloaded file or static image, inspect that output separately; this exercise does not verify preservation of an interactive timeline outside Sheets.

No native timeline or screenshot was produced during authoring.

Official references

The controls and eligibility above are based on Google’s create and edit timeline documentation; the fixture and boundary checks are proposed reader exercises.