Gantt charts for student projects: a 10-week example

Why plan backwards from the hand-in date?

The hand-in date tells you when the work must be ready. Work backward using realistic durations to find the latest safe start for each step. If the plan does not fit, change scope, availability or the approach; do not shorten estimates just to make the bars line up.

The University of St Andrews' study skills page on Gantt charts for planning makes the same point with a roast dinner: you start from the part that takes longest and work back, so everything is ready at the same time. With an assignment you already know the due date, so that is where the plan starts.

Here is that chain for the example used throughout: four students, a market research report with appendices, ten weeks, and the report due on the Friday of week 10. Read it from the bottom of the project upwards. It counts working days, so in Ganttile it assumes Hide weekends is turned on under Settings.

1. Report hand-in: the Friday of week 10.
2. Proofread and format: the Wednesday and Thursday before it.
3. Buffer: the four working days in front of the proofread, from Thursday of week 9 to Tuesday of week 10.
4. Final edit: the Wednesday of week 9.
5. Revisions from the supervisor's comments: the Monday and Tuesday of week 9, one task per section owner, so the comments have to be back by the end of week 8.
6. Supervisor reading the draft: a week, so the full draft goes to the supervisor at the end of week 7.

That last line is the one that changes behaviour. In a ten-week project the complete draft is due at the end of week 7, and if the topic is only approved at the start of week 3, the group has five weeks for all of its research, analysis and writing. Seeing that in week one changes how the group spends weeks two to four.

What does a ten-week group project look like on a Gantt chart?

The example uses six phases, plus a list for other deadlines. That is enough to show the handoffs without recording every study session. In Ganttile, each list has a summary bar spanning its tasks. Adapt the detail to your assignment.

A few things in that plan are deliberate. The survey cannot be designed until the topic is approved, so "Chen: design the survey" is linked to that milestone rather than just placed after it, and "Chen: run the survey" is linked to the design. The supervisor's reading week is a bar of its own, and the group fills it with work that does not depend on the comments: references, appendices and the executive summary, plus slides if the course has a presentation. And the analysis starts in week 5, so there are early results to show at the progress meeting.

Links help expose the effect of a slip. If the survey finishes a week late and no spare time remains before analysis, with Auto schedule turned on the findings and draft forecast also move. Compare that forecast with the agreed review and submission dates; Auto schedule does not renegotiate a supervisor meeting for you.

Who owns a task when four people share the work?

Give each task one accountable owner, even when several people help. A row labelled "everyone" makes it hard to know who will report progress or raise a problem. The Australian National University's group work advice recommends specific responsibilities and deadlines.

In Ganttile, put the owner at the front of the task name, as in "Chen: survey findings". Split work when the parts have different owners or handoffs; otherwise put the coordinator first in the task name and the contributors after them, as in "Chen + Dana: survey findings" with Chen coordinating. Meetings can use "All:" with one person responsible for arranging them.

Use one task colour per student and agree the colour key in the group chat or the first meeting notes. Ganttile draws no legend, so write the key alongside the chart whenever you export it. Colour helps each person find their work, but it does not measure workload: compare effort and availability as well as bar length.

Choose a chart keeper, even though everyone can work in the chart. Ganttile is free for the whole group: invite the other three through its linked Breeze account and they can view and edit the same chart, so each person marks their own tasks done. The keeper, Aisha in this example, owns the structure: she checks the dates at the weekly meeting and sends the supervisor a dated PDF. Agree how members report changes between meetings so the chart does not lag behind the work.

Where should supervisor checkpoints go?

Show agreed supervisor appointments and submission dates as milestones, then work out what must be ready for each. Keep the fixed appointment separate from a moving forecast if work is late. For topic approval, you need the proposal; for a draft review, you need the combined draft.

Draw the supervisor's reading time as a bar, not a gap. A week where nothing appears to happen invites someone to fill it with the next task, and then the comments arrive while the group is busy with something else. A bar called "Supervisor reading the draft" explains the week and shows what can run alongside it. The guide to milestones and dependencies covers how a milestone and the links in front of it work together.

Ask the supervisor how long they need to read a draft rather than guessing. Supervisors with a dozen groups often need longer than the example's week at the busiest point of term.

How much slack does a student plan need?

Base contingency on the risks you can name: a slow survey response, a missing group member or a revision round. The example reserves four working days out of fifty before proofreading. That is an illustration, not a recommended percentage for every assignment.

A visible shared buffer makes contingency easier to discuss than extra days hidden in every estimate. It needs active management: if revisions overrun by two working days, reduce the four-day buffer to two and check that proofreading still fits. An ordinary linked buffer task will not shrink itself. If the overrun exceeds it, revise the plan and speak to the supervisor.

The other source of slips is everything else in your life. Dublin City University's study skills page on managing time suggests putting major commitments on the chart so you can see problem areas at a glance. For a group, that means a list called "Other deadlines" holding each member's other hand-ins and exams as milestones. In the example Ben has a lab report due in week 5 and Dana has an exam in week 8, which is why Dana has nothing in week 8 and Ben's desk research is finished early in week 5.

The same DCU page warns that a chart like this gives only a rough picture of how the term fits together, and that you still need short-term goals for the detail. That is the right split. The chart says what has to be finished by Friday, and each person decides how to get there.

What do markers and supervisors look for in a submitted chart?

Check the assignment brief and the marking criteria first, because some courses specify what the plan should include. Beyond that, a chart that is easy to read and mark usually has:

• one page, readable when printed, with weeks rather than days across the top;
• phases that match the stages named in the brief;
• the supervisor checkpoints and the hand-in shown as milestones;
• an owner on every task;
• slack you can point to, rather than a plan that only works if nothing goes wrong.

Export a PDF from Ganttile for the submission or to send to your supervisor, and mark finished tasks as done before you export, so the reader can see what is complete. Keep the week-one PDF too, since Ganttile keeps no baseline of the original plan, and a reflection on how the project went often starts from the difference.

What happens when a group member goes quiet?

Deal with it early, on the chart, and in the way the group agreed at the start. The University of Southampton Library's guide to starting a group project suggests deciding how to handle a member not attending and missed work when you set the ground rules, and agreeing those rules in writing. That agreement is what makes the next steps feel fair rather than personal.

1. Look at which bars carry their name, and which of those lead to the next checkpoint.
2. After the time the group agreed, say two working days with no reply, message them with the specific tasks and dates.
3. If there is still no reply, follow your course's process and agree any reassignment with the group and supervisor. Update owners and forecasts so the effect is visible.
4. Tell the supervisor early, and send the chart with the message.

The chart is useful evidence here because it records who was meant to do what and when. ANU's page makes the same point about records: agendas, minutes, planning documents and written agreements can help you show your lecturer how the project progressed. Keep the dated exports and brief meeting notes; the current chart alone does not preserve who owned a task before it was reassigned.

Quick answers for students

Can I make a student Gantt chart in Excel instead?

Yes, especially if the course asks for a spreadsheet. There are step-by-step instructions for a Gantt chart in Excel. The trade-off is that, unless you build the formulas yourself, moving one task does not move the tasks that depend on it, which is the main thing a group plan needs. If you are free to choose the tool, compare the free Gantt chart tools first.

Is a Gantt chart worth it for a solo project?

For a short essay, a list of dates is enough. Once a solo project runs for several weeks with stages that depend on each other, a chart starts to help, and a small, simple chart with a handful of tasks is plenty.

Should the chart show days or weeks?

Weeks, for a project of ten weeks or longer. Days make the chart too wide to read on one page, and short personal steps, such as sending a reminder or booking a room, usually belong on a personal to-do list rather than the group chart.

Set up the plan at your first group meeting

Start before topic approval so you can see what must happen afterward. Confirm the supervisor's review time, check everyone's other deadlines and agree how updates will reach the chart keeper.