Gantt Timeline Project Planning

Learn the fundamentals, define a controlled project, build a work breakdown, schedule activities, manage dependencies, risks, issues and decisions, then monitor delivery through an interactive Gantt timeline and dashboard.

New project — local autosave activeGantt export: embedded SPI master workbook — no PHP required

Project planning in simple terms

A project plan connects the intended outcome to the controlled work required to achieve it.

Need→Objectives→Scope→Requirements→WBS→Schedule→Risks→Delivery→Acceptance→Lessons

Charter & Scope

Define why the project exists, the outcome required, what is in and out of scope, constraints, assumptions and acceptance criteria. This creates the project's controlled baseline.

WBS

Break deliverables into manageable work packages and tasks. A good WBS makes ownership, estimation, sequencing and progress measurable.

Dependencies & Critical Path

Tasks can depend on other tasks. Finish-to-start is common. The critical path is the longest dependent sequence controlling the earliest completion date.

Milestones & Gates

Milestones mark significant events; gates are formal decision points with entry/exit criteria and approval authority. They are not simply tasks with long durations.

Risk vs Issue

A risk might happen; an issue has happened. Risks need probability, impact, mitigation and ownership. Issues need action, owner and resolution dates.

Control & Change

Track planned versus actual dates, decisions and changes. Approved changes should update the baseline deliberately rather than allowing the plan to drift silently.

Good-practice planning principles

Use measurable objectives and acceptance criteria; identify stakeholders early; estimate work before committing dates; sequence dependencies; identify resource constraints; maintain a live risk/issue log; use gates for major commitments; review schedule health regularly; record decisions and approved changes; close with acceptance and lessons learned. Frameworks commonly used for project management include ISO 21502, PMI practices, PRINCE2 and Agile approaches where iterative delivery is appropriate.

Project Charter

Define the project before scheduling the work.

Project ID

Project title

Project manager

Sponsor / authority

Planned start

Target finish

Status

Priority

Purpose / business need

SMART objectives

In scope

Out of scope

Deliverables & acceptance criteria

Budget / cost limit

Project phase

Constraints

Assumptions

Team, Stakeholders & RACI

Record who matters, their role and how they are engaged.

Name / Group	Role	Influence	Interest	RACI	Communication / Notes

Work Breakdown Structure & Task Register

Build work packages, tasks, milestones and gates. Dependencies use Task IDs separated by commas.

ID	WBS	Task / Deliverable	Type	Owner	Start	Finish	%	Status	Priority	Predecessor(s)	Notes

Interactive Project Timeline / Gantt

Generated directly from the task register. Edit dates or progress and the visual updates automatically.

TaskCompleteOverdueMilestoneGate

Risk Register

Score probability × impact (1–5) and control the response.

ID	Risk	P	I	Score	Owner	Response / Mitigation	Status

Issue Log

Record problems that have occurred and need resolution.

ID	Issue	Owner	Opened	Target	Status	Action / Resolution

Stage Gates & Decisions

Formalise major approval points and preserve the decision trail.

Gate	Target Date	Entry / Exit Criteria	Decision Authority	Decision	Decision Date	Notes

Closure & Lessons Learned

Outcome / acceptance

Lessons learned

Benefits / follow-up actions

0Tasks

0%Average progress

0Overdue

0Milestones / Gates

0Open risks

0Open issues

Schedule Health

Upcoming Milestones & Gates

No milestones or gates scheduled.