FreeNo sign-upYour plan stays on your computer

Gantt Chart Maker

Put the plan on a calendar as bars, with what each activity waits for, the critical path and the buffer. Each week, record the work actually finished: the chart moves the dates, finds the critical path again, and shows how much buffer is left.

The time you have

  • Count from when the work starts. With a start date, the chart shows the dates too.
Count time in

The activities

  • What each waits for, by letter: "A, C". Leave it empty for work that can start straight away.
  • Work packages are optional: each week you count the ones finished, which says more than a percentage.

Your plan never leaves your browser

The names of activities, risks and people stay on your computer and in your progress file. To write the diagnosis, only the weeks and counts are sent to our server, by place in your list. How it works

About the tool

Why it exists

A plan everyone can read, kept true every week

A plan in a spreadsheet tells people little; the same plan as bars on a calendar shows what happens when, what waits for what, and which chain sets the finish. Its value comes from updating it every week with what actually happened, so the chart shows the project as it is, not as it was planned.

It works on its own, and as the last stage of our playbook for planning a project that finishes on time, where it takes the plan from stages 1 to 4 and the risks and buffer from stage 5, and puts every stage's results in one report.

The method

How the tool works

The chart. One bar per activity against the weeks, arrows from what each waits for, diamonds for milestones, the critical path darker, the finish and the date, and the buffer between them. The chart shows the critical path; the calculation behind it finds it.

The weekly update. For each activity: not started, started or finished, the week it started and finished, and for work running late, a new expected finish. Finished work sits at its actual dates, work running late at its new finish, and work not started after what it waits for, and not before this week. The critical path and the finish are worked out again from there.

Work done. The darker part of each bar is work finished, counted in finished work packages rather than estimates of progress: a package is finished or it isn't.

The buffer left. The time between the forecast finish and the date. "Start next week's update" keeps each week's figure, so you can see how fast the buffer is going against how much work is done.

Dates fixed by hand. Work that should have finished by now, isn't finished, and has no new date stops the tool: a chart whose finish never moves while the work does is being kept, not updated.

Measuring the finish. When every activity is finished, the results compare each actual duration with its estimates. Keep them: they are the best estimates you will have for the next project.

What leaves your computer. Names stay in your browser and your progress file. To write the diagnosis, the page sends our server only the weeks and counts, by place in your list, and the server keeps nothing.