Schedule template

Gantt chart template with phases, dependencies, and an editable Gantt version.

Download a CSV Gantt chart template with phases, task rows, durations, and dependency references, then open the same structure as an editable Gantt chart in GanttPilot.

8 phases, 34 task rows, dependency references, and example durations you are meant to replace. Use it as a starting structure, not a finished plan.

The task table behind the chart

Every row has a duration and, where it matters, a dependency. Read the Depends on column first: that is the part of a Gantt chart template you cannot get from a picture of one.

PhaseTaskDurationDepends on
Initiation and ScopeConfirm project goal and success criteria2 days-
Initiation and ScopeIdentify stakeholders and decision owners2 days1
Initiation and ScopeDefine scope, deliverables, and exclusions3 days1
Initiation and ScopeAgree budget envelope and constraints3 days3
Planning and BaselineBreak scope into work packages3 days3
Planning and BaselineEstimate durations and effort3 days5
Planning and BaselineMap dependencies between work packages2 days5
Planning and BaselineAssign owners and resources2 days6, 7
Planning and BaselineReview critical path and float2 days6, 7
Planning and BaselineBaseline the schedule and communicate dates2 days4, 8, 9
Design and ApprovalsDraft design or solution outline6 days10
Design and ApprovalsInternal design review3 days11
Design and ApprovalsStakeholder approval and sign-off4 days12
Procurement and SetupConfirm long-lead items and suppliers5 days13
Procurement and SetupRaise purchase orders and contracts5 days14
Procurement and SetupPrepare environment, site, or workspace6 days13
Procurement and SetupOnboard team and confirm access3 days13
Build and DeliveryDeliver work package 112 days16, 17
Build and DeliveryDeliver work package 212 days18
Build and DeliveryDeliver work package 310 days18
Build and DeliveryReceive and check supplier deliverables5 days15
Build and DeliveryIntegrate work packages6 days19, 20, 21
Testing and ReviewPrepare test and acceptance criteria3 days13
Testing and ReviewFunctional testing8 days22, 23
Testing and ReviewFix defects and retest6 days24
Testing and ReviewQuality review and stakeholder walkthrough4 days25
Launch and RolloutLaunch readiness check3 days26
Launch and RolloutTraining and documentation5 days26
Launch and RolloutGo-live or rollout3 days27, 28
Launch and RolloutPost-launch monitoring window5 days29
Closeout and HandoverClose open items and corrections5 days30
Closeout and HandoverFinal acceptance and sign-off3 days31
Closeout and HandoverHandover to operations or owner3 days32
Closeout and HandoverLessons learned and project close2 days33

What each phase is for

The structure runs from scope through planning, design, procurement, delivery, testing, launch, and closeout, so the plan has somewhere to put approval time, lead times, and rework.

WBSPhaseTypical tasksWhy it mattersDuration
1Initiation and ScopeGoal, stakeholders, scope, deliverables, constraintsA Gantt chart drawn before scope is agreed will be redrawn. Fixing what is in and out of scope first is what makes the later dates worth publishing.5-10 days
2Planning and BaselineWork breakdown, estimates, dependencies, owners, critical path review, baselineThis is where the Gantt chart is actually built: work packages, durations, and the dependency logic that decides which dates can move and which cannot.8-15 days
3Design and ApprovalsDraft solution, internal review, stakeholder sign-offApproval time is real schedule time. Leaving it out is one of the most common reasons a plan slips in its first month.10-18 days
4Procurement and SetupSuppliers, purchase orders, environment or site setup, team onboardingLead times and access usually decide when delivery work can start, regardless of when the plan says it should.8-15 days
5Build and DeliveryWork package delivery, supplier deliverables, integrationThe longest phase, and the one where parallel work packages either overlap cleanly or overload the same people.25-45 days
6Testing and ReviewAcceptance criteria, testing, defect fixes, retest, stakeholder walkthroughTesting is not one task. Fix-and-retest loops need their own rows or the finish date will be optimistic.12-25 days
7Launch and RolloutReadiness check, training, documentation, go-live, early monitoringGo-live is a milestone, but readiness, training, and the watch period around it are the work that protects it.8-15 days
8Closeout and HandoverOpen items, final acceptance, handover, lessons learnedCloseout keeps acceptance and turnover visible instead of trailing off after the launch milestone.8-15 days

What makes a Gantt chart template worth using

Most Gantt chart templates are a grid of coloured bars. The useful part is the logic underneath, which is what these notes explain.

What a Gantt chart template should give you

A phase structure, editable durations, dependency logic, and milestones. A template that is only a list of task names with dates is a picture of a plan, not a plan you can check.

Why the durations here are ranges, not promises

The example dates produce a 90-120 day chart so the shape is visible immediately. They are placeholders. Replace them with your own estimates before showing the chart to anyone who will hold you to it.

Why dependencies matter more than dates

Dates are easy to change and easy to get wrong. Dependency logic is what tells you which dates are allowed to move on their own and which ones drag the finish date with them.

Dependencies to check before you publish dates

These are the links that decide whether the finish date is real. Check them before the chart goes into a status report.

Scope drives everything after it

Tasks 3 and 5 sit under most of the chart. If scope or the work breakdown changes, durations and dependencies downstream have to be rechecked rather than dragged.

Approval gates are schedule tasks

Design sign-off blocks procurement and setup. Review time belongs on the chart as its own row, with a duration, not as a zero-day milestone.

Procurement lead time is often the real constraint

Supplier deliverables run in parallel with build work. The integration task waits for both, which is where an optimistic delivery date usually breaks.

Test and fix is a loop, not a line

Fix defects and retest depends on functional testing finishing, and the walkthrough depends on the fixes. Collapsing these into one bar hides the most common source of slip.

Launch is protected by the tasks around it

Readiness check and training both feed go-live. Post-launch monitoring then feeds closeout, so acceptance is not signed while issues are still open.

Resource notesA Gantt chart shows time, not whether anyone is free to do the work.
  • The delivery team is the constraint through work packages 1 to 3; check whether the three packages were meant to run in parallel before assuming the dates hold.
  • The project manager appears in initiation, planning, and closeout. Those are usually the phases that get squeezed when the same person is running delivery.
  • Design and QA sit at the front and the back of the chart. If the same specialists cover both, testing tends to start late.
  • Stakeholders and approvers need reserved windows. Approval tasks with no named owner are the ones that slip quietly.

Three ways to start from this template

Take the CSV into a spreadsheet, open the same structure as an editable Gantt chart, or describe your project and let AI draft the task rows for you.

  • Download the CSV to edit phases, tasks, and durations in Excel or Google Sheets.
  • Open it in GanttPilot to move dates, redraw dependencies, and check the critical path.
  • Replace the example scope with your own before agreeing any date with a stakeholder.
  • Assign owners, then check resource load before you accept that parallel work packages fit.

Prefer to build it yourself? The online Gantt chart maker starts from an empty chart instead of a template.

Before it becomes a planThe example durations are placeholders. They are not an estimate of your project.

Replace the scope, re-estimate the durations with the people doing the work, confirm approval and lead times, and check the dependency logic still matches how the work will actually run.

Common questions

What is included in this Gantt chart template?

Eight phases and 34 task rows covering initiation, planning, design and approvals, procurement and setup, build and delivery, testing, launch, and closeout. Every row has a duration and dependency references.

Can I download the Gantt chart template?

Yes. The CSV download contains the same phases, task names, durations, and dependency references shown on this page, so it can be edited in Excel, Google Sheets, or any spreadsheet tool.

Can I open this template as an editable Gantt chart?

Yes. Open in GanttPilot loads the same task structure as an editable Gantt chart where you can move dates, change dependencies, assign resources, and check the critical path before saving it as a project.

Is this Gantt chart template free?

The CSV download and the Gantt preview are free to open. You need an account to save the project, keep editing it, or export it to Excel or Microsoft Project XML.

What is the difference between a Gantt chart template and a project schedule?

A template gives you the structure: phases, typical tasks, and dependency logic. It becomes a schedule once you replace the example scope and durations with your own project and agree the dates with the people doing the work.

Can I use this template for any type of project?

The structure is deliberately generic, so it fits most delivery projects. If your work is construction, plant installation, a shutdown, or a handover, the specialised templates in the library will need less editing.