Gantt Chart Examples for Every Project Type

One example in full: the Hallam Trust conference

Twelve summaries help you recognise your own project; one plan with real dates shows you the shape. Here is a single example carried the whole way down — a 400-person annual conference on Thursday 15 October 2026, planned from Monday 1 June, five working days a week.

An event chart behaves unlike every other example here because the finish date cannot move. You are not asking "when will we be done?" but "does the work fit in front of the date, and by how much?" Had the chain landed on 20 October, no amount of effort would help — you would cut scope, start earlier, or shorten the marketing window.

Two details about how gantts.app schedules this. It computes total float — how far a task can slip before the finish date moves — not free float. And it schedules as-placed: a dependency can push a task later than where you put it but never drag it earlier, which is exactly what you want for a rehearsal parked deliberately in the week of the event. The link guarantees it cannot happen before print and headcount are done; it does not yank it back to August.

The 12 examples compared

Before the individual write-ups, here is how the main types differ on the four things that actually change the chart:

Project type	Typical span & axis	Dependency density	Where the risk lives
Construction	6–24 months, weekly	Very high — nearly everything is FS	Inspections and permits: one failure moves everything
Software / agile	1–6 months, weekly by sprint	Low between sprints, high into release	Scope, not sequence — bars grow rather than move
Marketing campaign	6–12 weeks, weekly	Moderate, mostly within a track	Approvals between parallel tracks
Event planning	3–6 months, weekly	Moderate, converging late	The fixed date. Contingency is the gap in front of it
Product launch	8–16 weeks, weekly	High and cross-team	Hand-offs between product, marketing and support
Research / thesis	9–24 months, monthly	Low but long-chained	Third-party approvals with unknowable durations
Weekly plan	5 days, daily or hourly	Almost none	Nothing structural — it is a communication device

The pattern in that last column is worth reading twice. In construction the risk is sequence; in software it is scope; in events it is a date. Same chart, three different questions to ask it.

1. Construction project

A construction Gantt chart is heavily phased and dependency-driven: pre-construction (permits, design, site survey), site prep & foundation, structure & framing, MEP and interiors, and inspection & handover. Tasks chain tightly — you can't pour footings before excavation, or drywall before rough-in inspection passes — so finish-to-start dependencies and the critical path do real work here. Key milestones include permit approval, foundation sign-off, "dried in," and final inspection.

Because so much work is sequential, this is where the critical path earns its keep: it names the single delay — a late permit, a failed inspection — that would push completion. Start from the construction template.

2. Software / agile development

A software Gantt chart maps releases and sprints rather than a single linear build: discovery, design, then repeating sprint blocks for build and QA, followed by UAT and release. Typical tasks are epics broken into stories, code review, testing, and a launch checklist. Milestones mark sprint reviews, feature-complete, code freeze and go-live. Even agile teams use a Gantt view to communicate a release timeline to stakeholders who live outside the backlog.

The trick here is altitude: keep the timeline at epic and sprint level and let the day-to-day live in your issue tracker. A two-week sprint is one grouped bar with a review milestone at its end, not thirty story bars. See the software development template.

3. Marketing campaign

A marketing campaign Gantt chart coordinates several tracks running in parallel: strategy & planning, content production, design & assets, channel setup (email, paid, social), and launch & reporting. Tasks like drafting copy, approvals, ad creative and scheduling overlap across teams, so swimlane-style grouping by workstream keeps it legible. Milestones include creative sign-off, campaign launch, and the post-mortem.

Grab the marketing template or start fresh in the Gantt maker.

4. Event planning

An event Gantt chart counts down to a fixed, immovable date, which makes backward scheduling essential. Phases run venue & budget, vendors & logistics, marketing & registration, run-of-show prep, and event day & wrap-up. Typical tasks: book venue, confirm caterer, send invites, finalize agenda, rehearse. Milestones include contracts signed, registration open, and the event itself as a hard deadline milestone.

This is the type worked in full at the top of this page: because the end date can't move, what matters is the gap between where the critical chain lands and the date itself. Use the event planning template or plan it live in the editor.

5. Product launch

A product-launch Gantt chart aligns product, marketing, sales and support around one go-live date. Phases: readiness (final QA, pricing, docs), go-to-market (messaging, landing pages, PR), enablement (sales and support training), and launch & post-launch. Cross-team dependencies are everywhere, so the critical path shows exactly which slip would move the launch. Milestones: feature freeze, launch date, and the 30-day review.

Build a launch plan in the Gantt maker or browse the template library.

6. Research / thesis timeline

A research or thesis Gantt chart spans months and is milestone-heavy: literature review, proposal, data collection, analysis, and writing & revision. Tasks tend to be long and sequential, with dependencies on approvals (ethics board, supervisor sign-off) that are easy to underestimate. Milestones include proposal defense, data-collection complete, first draft, and submission. It's a favorite for students because it turns a vague year into a visible plan.

Start a thesis timeline free in the editor.

7. Small business project

Small-business Gantt charts are lean and practical — opening a shop, launching a service, or running a quarterly initiative. Phases might be plan, set up, launch, and review, with a handful of tasks each. The value here is less about complex dependencies and more about a shared, at-a-glance schedule that a small team can actually keep updated. Milestones: financing secured, doors open, first sale.

See how a Gantt chart works, then build one in the Gantt maker.

8. Simple weekly plan

Not every Gantt chart spans months. A weekly plan zooms the axis to days and lays out tasks across a single week — useful for content calendars, sprint weeks, or personal productivity. Phases collapse into simple groupings (Mon–Fri), tasks are short, and dependencies are light. It's the friendliest on-ramp for anyone new to Gantt charts.

Open a blank weekly plan in the editor and set the timescale to days.

Four more quick examples

• 9. Manufacturing / production run — phases for sourcing, tooling, production, QA and shipping; dependencies gate each stage and milestones mark first article and shipment.
• 10. Consulting engagement — discovery, analysis, recommendations and delivery, with client review milestones between phases and a fixed end date.
• 11. Onboarding / HR rollout — a 30/60/90-day plan with training, systems access and check-in milestones, often shown on a weekly axis.
• 12. Grant or nonprofit program — long, reporting-driven phases tied to funding milestones and compliance deadlines that behave like hard dependencies.

Whatever the domain, the structure repeats: group tasks into phases, connect the ones that depend on each other, mark the moments that matter as milestones, and let the critical path tell you where the risk is. What changes between them is the timescale and the density, not the underlying idea.

What makes a good Gantt chart

Across all 12 examples, the strong charts share the same traits:

• Clear phases. Group related tasks so the plan reads as a story, not a wall of bars.
• Real dependencies. Link tasks that must happen in order so a slip in one automatically pushes the rest.
• Visible milestones. Mark approvals, launches and deadlines as distinct points people can rally around.
• A highlighted critical path. Know which tasks actually drive the finish date, so you protect the right ones.
• Readable density. Keep roughly 10–30 bars per view; roll big projects up into phase summaries and break detail into sub-charts.
• Status at a glance. A today line and % complete turn the chart into a live report, not a static plan.

The Hallam Trust plan scores well on most of that and badly on one: twelve rows, three milestones, a clear critical chain — but catering contracts finishing in June for a rehearsal in October is a gap nobody would defend out loud. Look for those. A task with months of float is usually a missing dependency wearing a disguise.

Just as important is what to leave out: a Gantt chart is a communication tool, not a task database. Resist the urge to log every sub-task, and push granular detail down into a checklist or issue tracker so the chart stays scannable in a single glance. New to this? Our step-by-step guide walks through building one from scratch, and what is a Gantt chart covers the fundamentals.

Opening an example in the editor

Any of these becomes a working plan in about a minute, using the buttons as they are actually labelled:

1. Pick the closest starting point in the template library — it opens directly in the editor with phases, tasks and dependencies already wired up.
2. Or start from nothing: ✨ Paste to Gantt and paste an outline. Durations in brackets, after for a link and a trailing ! for a milestone are all detected — Marketing campaign (45d) after Registration opens, then Conference day !.
3. Build rows by hand with ＋ Task, ◆ Milestone and ▣ Group, then indent tasks under a phase.
4. Double-click a row for Runs after (predecessors), Assignee and % complete. Milestones have zero duration and cannot be dragged wider, so if a row needs to be longer it was never a milestone.
5. ⚡ Auto-schedule pulls every task to the earliest date its links allow — the fastest way to find out whether a fixed date like 15 October is still reachable.
6. Tick Critical path, set Zoom to Week for anything spanning months, and save a ◳ Baseline once the plan is agreed.
7. Share it: ⬇ Export for 📄 PDF document, 📊 Excel (.xlsx), 📑 CSV (spreadsheet) or 📽 PowerPoint (.pptx), or 📤 Share… for a 🔗 Shareable link. Set View to Milestones only for the version a board sees.

Frequently asked questions