Weekly project review meeting: a 20-minute agenda

A weekly project review meeting is the cheapest way to keep a team on the same schedule. Done badly, it turns into a round-table where everyone reads out a list of tasks nobody else cares about. Done well, it takes twenty minutes, uses the plan as the single source of truth, and ends with decisions instead of vague intentions. This guide gives you an agenda you can copy, shows what to look at in your Gantt chart, and explains how to prepare so the meeting stays short.

What the meeting is for

A review meeting has one job: make sure the plan on screen matches reality, and decide what to do where it does not. It is not a place to discover what people are working on. That should already be visible in the plan before anyone joins.

Three questions drive the whole meeting:

1. Where are we against the plan? Which tasks are done, which are late, which are about to start.
2. What is blocking us? Anything that stops a task from moving, whether it is a missing input, a person who is overloaded or a decision nobody has made.
3. What changes now? New dates, new owners, a scope cut, or nothing at all.

If a topic does not help answer one of those, it belongs in a different conversation.

Before the meeting: update the plan first

The most common reason review meetings drag is that the plan is out of date, so the first ten minutes are spent reconstructing the truth out loud. Fix that by asking each task owner to update their own tasks before the meeting starts: set progress, adjust a duration if the estimate was wrong, and add a note when something has changed.

This works best when the people who own tasks can edit them and everyone else can only look. If you have not decided who should have which role yet, read editor vs viewer access: who should edit a project plan. For the habit of keeping the plan current between meetings, see how to keep a project plan up to date.

Because everyone opens the same shared plan, there is nothing to export and email around. The chart you look at in the meeting is the one people updated this morning.

A 20-minute agenda you can copy

Here is a simple structure. Adjust the times to the size of your team, but keep the order.

Minutes	Topic	Question it answers
0–3	The big picture	Is the next milestone still on track?
3–8	Late and at-risk tasks	What is behind, and by how much?
8–13	Blockers and dependencies	What is stopping work, and who can remove it?
13–17	The next two weeks	Who starts what, and is anyone overloaded?
17–20	Decisions and actions	What did we change, and who does what next?

The big picture (3 minutes)

Open the chart zoomed out to the next milestone. Say out loud whether it is on track, at risk or already missed. Starting here stops the meeting from getting lost in details, because everyone knows what the details are protecting. If you are unsure how to choose them, what is a milestone in a Gantt chart covers it.

Late and at-risk tasks (5 minutes)

Go through only the tasks that are behind or about to be. A task whose bar has passed today's date but whose progress is still low is the first thing to check. Do not read through tasks that are going fine. Silence on a healthy task is a good sign.

For each late task, ask the owner for a new realistic finish date, not an apology. Then look at what depends on it. A one-day slip on a task with nothing after it is a footnote. The same slip on a task that holds up three others is the main topic. How to handle project delays goes deeper on recovery options.

Blockers and dependencies (5 minutes)

Ask: "What is waiting on something?" Look at the dependency lines in the chart. A task that cannot start because a predecessor is unfinished is a blocker you can see; a task that is stuck because someone is waiting for an answer is a blocker you have to ask about. Write each one down with a name next to it.

If your plan highlights the critical path, spend your attention there first. Slips on the critical path move the end date, while slips elsewhere may be absorbed. Critical path in a Gantt chart explains how to find it.

The next two weeks (4 minutes)

Look forward, not back. Which tasks are due to start, who owns them, and does anyone have too much at once? If one person is assigned to five overlapping tasks, either the dates or the assignments have to change. Make that call now, while it is cheap.

Decisions and actions (3 minutes)

End by reading back what changed. Each change should be one of three things: a date moved, an owner changed, or a scope item added or removed. Anything else is a note, not a decision. Apply the changes to the plan before people leave the call, so the chart is correct the moment the meeting ends.

Example: a website relaunch

Imagine a six-week website relaunch with a designer, a developer, a writer and a project lead. It is Thursday of week three, and the "Build" phase is due to start Monday.

• Big picture: the "Staging ready" milestone is two weeks away. The lead says it is at risk.
• Late tasks: "Final homepage design" is at 70% and was due yesterday. The designer expects to finish Friday.
• Blockers: "Build homepage" depends on that design task, so it will start Monday only if Friday's date holds. The writer is also waiting on the final layout to place copy.
• Next two weeks: the developer has the build and the contact form scheduled in the same week. The team agrees to move the form to the following week.
• Decisions: design finish moves to Friday, the form task moves one week, and the writer's copy task now starts the same Monday as the build. The lead updates all three before the call ends.

The whole conversation fits in twenty minutes because the plan already showed the problem. Nobody had to explain what the dependency was.

Tips to keep the meeting short

• Keep the same time every week. A recurring slot beats a meeting that is negotiated each time.
• Invite only people with a task in the next two weeks. Others can read the plan whenever they like.
• Never read the whole task list. Review exceptions only.
• Park side conversations. If two people need to solve something, schedule it after the meeting and keep the rest of the team out of it.
• Share the outcome. People who were not there should be able to open the plan and see the new dates without a separate email. If you need a short written summary, how to write a project status update provides a template.

Using an AI assistant for the prep

If your assistant is connected to your plan, you can use it to prepare. A prompt such as "List the tasks that are overdue or start in the next two weeks, and show which ones are on dependency chains" gives you the agenda items in seconds. The assistant works on the same plan as everyone else, so the changes you agree on in the meeting can be applied by asking for them in plain language. Setup is described in the connector docs, and what to delegate to an agent explains what is better left to people. The decisions still belong to the team.

Common mistakes

• Using the meeting to update the plan. Update beforehand; use the time to decide.
• Reviewing every task. Focus on late, blocked and upcoming work.
• Leaving without changes written down. If the plan does not change, nothing was decided.
• Skipping the meeting when things look fine. A five-minute check is still cheaper than finding a problem a week later.

Start with your next meeting

Pick a recurring time, ask owners to update their tasks that morning, and run the five-part agenda above. If you do not have a shared plan yet, you can create one in ProGantt Flow and invite your team to it. After two or three meetings, you will find the habit matters more than the tool: the plan stays honest because someone looks at it together every week.