Weekly Gantt chart template

• 5 groups
• 14 tasks
• 2 deadlines
• 12 dependencies
• 1 week
• Updated September 24, 2026

What is in this week's plan?

Each group is one thing the team is doing this week, in priority order, with the check-ins on top. Collapse any group to hide its tasks while you talk about the others.

Why does every task start with a role?

Because a copied template has no people in it. The owner is written at the front of each task name (Account, Ops, Lead, Writer, Designer or Dev), so the left side of the chart reads like a rota. When you copy it, swap each role for a first name.

Keep it to one owner per task. If a piece of work genuinely needs two people, it is usually two tasks with a link between them, the way the draft and the review are here. A bar with two names on it tends to be the one nobody feels responsible for on Thursday.

Which dates are deadlines, and which are estimates?

In this template every bar is an estimate and every milestone is a deadline. A bar says when the team expects the work to happen, and it can move. A milestone is a date promised to someone outside the team, and moving it means telling them.

• Bars are estimates. The page layout runs Wednesday to Thursday because that is the best guess. If the copy lands late, the bar moves, and nobody outside the team needs to hear about it yet.
• Milestones are deadlines. There are only two: the proposal to the client on Friday and the monthly update next Monday. Both are one-day bars in a different colour, so they stand out from the work around them.
• The Estimate column is effort. It adds a third number, the hours of work. Drafting the proposal has a two-day bar and a five-hour estimate, because the owner has other work in those same two days.

Priority 2 has no deadline marker on purpose. Its Friday finish is a target, which is exactly why it is the work allowed to carry over when the week gets tight.

What happens at the midweek check?

Fifteen minutes on Wednesday with the chart on screen. Each owner answers one question: will my task finish inside its bar? Anything that will not gets a decision there and then, not on Friday afternoon.

The chart shows where to look first. Dev: build and test the page has six hours of work in a one-day window on Friday, and it cannot start until the layout is done on Thursday. If the designer says on Wednesday that the layout needs another day, the build will not finish this week, and you still have two days to choose: find the developer some help, cut what the page includes, or agree that it carries over.

To try that on the chart, turn on Auto schedule under Settings first. Stretch the layout bar by a day and the linked build is pushed past Friday, which is the conversation the midweek check is for.

How does unfinished work move to next week?

At Friday’s review, add unfinished work under Next week and link it to the original task. Keep the original bar so you can compare what you planned with what carried over. Ganttile does not roll tasks forward automatically.

1. Leave the original bar where it is. Dragging it into next week rewrites what this week looked like. Left in place, it shows what was planned and when.
2. Add a task under Next week. Use the plus on the Next week row, put the owner and "(carried)" in the name, and size the bar to the work that is left.
3. Link the old bar to the new one. Draw a dependency from the original to the carried task, so anyone reading next week's chart can see where it came from.
4. Colour what finished, if you like. Giving finished bars a colour in the task editor makes the Friday review readable at a glance. Use the colour to record completion; scheduled dates alone do not show whether the work finished.

The template does this once so you can see the result: Dev: finish page build (carried) sits on next Monday, linked from Friday's build bar and from the Friday review.

How do you strip the chart back for the weekly meeting?

Show only what the meeting is about. A weekly discussion needs the priorities, the owners and whatever is at risk, not every column.

• Collapse the groups you are not discussing. The arrow next to each group name folds its tasks away, so the priority being discussed fills the screen.
• Hide weekends. Turn on Hide weekends under Settings and the week reads as five working days, with next Monday straight after Friday.
• Drop the columns you do not need. The columns menu in the toolbar switches Start time, End time, Duration and Estimate on and off. For the meeting, the task names and the bars are usually enough.
• Stay on the Day scale. The timescale menu also offers Week, Month and longer views, but for one week the Day view is the one that shows which day each task lands on.

What should you change when you copy it?

Click Use template and the plan lands in your account starting on the coming Monday, with every link in place. Then swap the three priorities for this week's real ones, replace the roles with names, and delete the Next week example unless something has already carried. Keep the check-ins that help your team review handoffs and adjust priorities. If your team plans further ahead than a week, the six-month plan in weeks works the same way.

For work spanning several phases, start with the project schedule template. Use day-level detail where estimates are reliable and broader phases for work that is still uncertain.