Gantt chart examples that show how real projects are laid out

A gantt chart example is most useful when it shows the decisions behind the bars, not just the bars. Below are five worked examples from different kinds of project: a software release, a conference, a product launch, an office fit-out and a hire. Each one lists the tasks, how long they take, what has to finish before what, and where the milestones sit, so the same layout can be copied onto a real project.

Every example uses weeks as its unit and assumes a team of roughly five to fifteen people. Before the examples, one short section on what makes a gantt chart readable at all, because the same rules decide whether any of these examples will survive contact with a real team.

What every example below has in common

A gantt chart is a horizontal bar chart of work against time. Each row is a task, the horizontal axis is the calendar, and the length of a bar is how long the task takes. Wikipedia credits the form to Henry Gantt, who designed his chart around 1910 to 1915, and notes an earlier tool of the same kind developed in 1896 by Karol Adamiecki, published only in Russian and Polish.

The examples below all follow five rules that separate a working chart from a decorative one:

1. Tasks are outcomes, not activities. "Homepage design approved" is a task. "Work on design" is not, because nobody can tell when it is finished.
2. Fifteen to thirty rows. Fewer than ten and the chart adds nothing a list could not show. More than forty and nobody reads it. Detailed subtasks belong in a task list underneath.
3. Dependencies are explicit. If task B cannot start until task A finishes, that is written down, not remembered. This is the line that lets the chart answer "what happens if A slips a week".
4. Milestones have zero length. A milestone is a moment, such as a launch or a sign-off, drawn as a diamond rather than a bar.
5. Every bar has one owner. A bar owned by "the team" is a bar nobody updates.

In the tables below, "after" means the task starts when the listed task finishes, which is the finish-to-start dependency most charts use by default.

Example 1: a mobile app feature release (10 weeks)

A product team of six ships a new feature to an existing app. The structure is a design phase, two build sprints, and a release window that depends on app store review.

#	Task	Owner	Weeks	Starts after
1	Problem and scope agreed	Product lead	1
2	Designs approved	Designer	2	1
3	API changes complete	Backend	2	1
4	Sprint 1: core screens	Mobile	2	2
5	Sprint 2: edge cases and analytics	Mobile	2	3, 4
6	QA and bug fixing	QA	1	5
7	Store submission and review	Mobile	1	6
8	Release (milestone)	Product lead	0	7
9	Release notes and help article	Support	1	5

What this example shows:

• Parallel work is visible. Design and API work run side by side in weeks 2 and 3. A list would hide that both have to be finished before Sprint 2.
• The external wait gets its own bar. Store review is not under the team's control, so it is a separate row with its own week. Teams that fold it into QA tend to announce dates they cannot keep.
• Support work hangs off Sprint 2, not off the release. The help article starts as soon as the feature is stable, so it is ready on launch day rather than a week later.

The critical path here is 1, 2, 4, 5, 6, 7, 8. Any slip on those rows moves the release. A one week slip on the API work in row 3 does not, because Sprint 1 still needs the designs first.

Example 2: a one day conference for 200 people (16 weeks)

Events are the clearest case for a gantt chart because the end date is fixed and everything is scheduled backwards from it.

#	Task	Owner	Weeks	Starts after
1	Budget and date confirmed	Organizer	1
2	Venue contracted	Organizer	3	1
3	Speakers confirmed	Program lead	6	1
4	Registration page live (milestone)	Marketing	0	2
5	Promotion campaign	Marketing	8	4
6	Agenda published	Program lead	1	3
7	Catering and AV booked	Organizer	2	2
8	Speaker slides collected	Program lead	2	6
9	Badges and signage printed	Organizer	1	Registration close
10	Event day (milestone)	Everyone	0	All above

What this example shows:

• Long bars carry risk. Speaker confirmation takes six weeks and gates the agenda, which in turn gates slides. If speakers are late, three rows move.
• A milestone can gate a long task. Promotion cannot start until the registration page is live, so the page gets a diamond of its own.
• Some tasks depend on a date, not a task. Badge printing waits for registration to close. Writing that date into the chart stops someone ordering badges for 140 people when 200 eventually register.

Example 3: a product launch campaign (8 weeks)

A marketing team of five launches a new plan or product. The work fans out from one positioning decision into several channels that all converge on launch day.

#	Task	Owner	Weeks	Starts after
1	Positioning and message agreed	Marketing lead	1
2	Pricing page copy final	Copywriter	2	1
3	Launch video recorded and edited	Video	3	1
4	Email sequence written	Copywriter	2	2
5	Sales deck and FAQ updated	Product marketing	2	1
6	Paid ads built	Performance	1	2, 3
7	Internal briefing (milestone)	Marketing lead	0	5
8	Launch day (milestone)	Everyone	0	4, 6, 7
9	Results review	Marketing lead	1	Launch + 2 weeks

What this example shows:

• A fan-out and fan-in shape. One decision at the top, five parallel streams, one date at the bottom. This is the shape most marketing gantt charts take, and it makes the slowest stream obvious at a glance.
• Internal readiness is a milestone. Briefing sales and support before launch is easy to forget and costly to skip, so it gets its own diamond.
• The review is scheduled in advance. Putting the results review on the chart before launch means it actually happens.

Example 4: a small office fit-out (12 weeks)

Construction is where gantt charts are most common, and also where dependencies are least negotiable. This example is a small office refurbishment managed by an operations lead with external contractors.

#	Task	Owner	Weeks	Starts after
1	Layout drawings approved	Ops lead	2
2	Building permission received	Ops lead	3	1
3	Furniture ordered	Ops lead	1	1
4	Demolition and strip-out	Contractor	1	2
5	Electrical and data cabling	Electrician	2	4
6	Partition walls and ceilings	Contractor	2	5
7	Painting and flooring	Contractor	2	6
8	Furniture delivered and installed	Supplier	1	3, 7
9	Move-in day (milestone)	Ops lead	0	8

What this example shows:

• Long lead items start early. Furniture has a long delivery time, so it is ordered in week 3 even though it is not needed until week 11. Without a chart, ordering tends to happen after the walls are up.
• Trades are strictly sequential. Cabling before walls, walls before paint. These are physical dependencies, and the chart makes clear that a one week delay on cabling moves move-in day by a week.
• Approvals are tasks. Building permission sits on the critical path and is often the longest wait in the project.

Example 5: hiring for a new role (9 weeks)

Hiring is rarely drawn as a gantt chart, but it benefits from one because several people's calendars have to line up.

#	Task	Owner	Weeks	Starts after
1	Role description approved	Hiring manager	1
2	Job posted (milestone)	Recruiter	0	1
3	Applications open	Recruiter	3	2
4	First interviews	Hiring manager	2	Week 2 of 3
5	Practical task and final interviews	Panel	2	4
6	Offer accepted (milestone)	Hiring manager	0	5
7	Onboarding plan and equipment ready	Ops	2	5

What this example shows:

• Overlap is deliberate. First interviews start while applications are still open, which is why the dependency says "week 2 of 3" rather than "after 3".
• The panel is the bottleneck. Final interviews need three or four people in the same week. Seeing that bar on the chart weeks in advance is what gets time blocked in their calendars.
• Onboarding starts before the offer is accepted. Laptops and accounts take time, so preparation runs in parallel with the final round.

Turning an example into a chart in Excel or Google Sheets

Most teams first try to reproduce an example like these in a spreadsheet. Two facts, checked on October 8, 2026, set expectations.

Excel has no built-in Gantt chart type. Microsoft's support article "Present your data in a Gantt chart in Excel" says so directly, and points to free Gantt chart templates instead. In practice, the template or a stacked bar chart with the first series hidden is how a chart like the ones above is drawn in Excel. Dependencies have to be maintained by hand.

Google Sheets has a Timeline view, but only on Workspace editions. Google's help article "Create & edit a timeline view" lists eligible editions including Business Starter, Business Standard, Business Plus, the Enterprise and Education editions, Essentials and Frontline. Personal accounts are not on the list. On an eligible account the steps are:

1. On a computer, open the spreadsheet and select Insert, then Timeline.
2. Select the data range and click OK.
3. In the timeline tab, click the settings icon and choose the columns for Card title, Start date and End date. Card group can be set to the owner column to put each person's bars on one row.

The help article notes that a start date must be earlier than the end date, or a card will not show the intended duration. It does not describe a way to link tasks as dependencies.

For the examples above, that means a spreadsheet will show the bars but not the "Starts after" column in action. When task 2 slips, someone has to move tasks 4, 5, 6, 7 and 8 by hand. With fifteen rows that is manageable. With thirty rows changing every week, it is the point at which teams usually move to a dedicated tool, where dates are changed by dragging a bar rather than retyping cells, and where comments and updates sit on the task itself. The features page shows what that looks like on a gantt board, and the comparison overview puts several such tools side by side.

What to change first

Take the example closest to the project at hand, replace the task names, and fill in the "Starts after" column before drawing a single bar, because the dependencies are what make the chart worth keeping. If keeping those dependencies up to date by hand is the problem, try the same plan in Pinateca, where Gantt boards are part of the free plan for up to five people and ten boards.

Q1. What is a simple example of a gantt chart?

A simple gantt chart lists five to ten tasks down the left side, with a horizontal bar for each one across a calendar of weeks. For a website update, the rows might be content agreed, design approved, build, review and launch, with each bar starting when the one it depends on finishes and the launch shown as a milestone.

Q2. How many tasks should a gantt chart have?

For a small team, fifteen to thirty rows is a practical range. Fewer than ten adds little over a task list, and more than forty becomes hard to read. Detailed subtasks are better kept in a list underneath the chart.

Q3. What is the difference between a task and a milestone on a gantt chart?

A task has a duration and is drawn as a bar. A milestone has no duration and marks a moment such as a launch, an approval or an event day, usually drawn as a diamond. Milestones are useful as gates that other tasks depend on.

Q4. Can Excel make a gantt chart?

Excel has no predefined Gantt chart type, according to Microsoft's support article. A gantt chart can still be made with Microsoft's free templates or with a stacked bar chart, but task dependencies have to be updated by hand.

Q5. Which gantt chart example fits a marketing team?

The product launch example fits most marketing work: one positioning decision at the top, several channels running in parallel, and a fixed launch date where they all meet. It makes the slowest channel easy to spot.