Understanding a project’s status should not depend on waiting for the next weekly report. In WiseTeam, you can see which tasks and project stages are in progress, what has been completed and what remains to be done. As the team updates its work, the project manager can assess the current position directly in the system. There is no need to collect the same information again and prepare a separate progress report for the weekly meeting.

A weekly project review still has an important purpose: bringing people together to assess the situation, resolve open questions and agree the next actions. Live visibility and regular discussion work together. You can check progress whenever you need to, while setting aside time for decisions that require the team.

See project status where the work happens

When tasks, deadlines and responsibilities are spread across separate lists and conversations, the project manager has to assemble the picture. A prepared report captures one moment, while work continues: one task finishes, another gets blocked and a priority changes.

WiseTeam’s project and task management functions bring that information into a shared system. Managers can see individual tasks and project stages, their statuses, deadlines and owners. This connects the overall project position with the work behind it.

If a stage is still in progress, for example, the manager can review the related work to understand what remains. One task may be underway, another may need a decision, and a third may already be complete. The discussion can start with the specific reason the stage has not finished.

For that view to reflect reality, the team needs to update task information as work happens. Mark completed work as done, revise a deadline when it changes and record a blocker against the relevant work. These updates belong in everyday task management.

Five questions for the weekly project review

Open the project in WiseTeam at the start of the review. The team can work from the information already there, without copying project status into slides or another spreadsheet. Use the following questions to guide the discussion.

1. What is complete, and which stages are moving forward?

Review completed tasks, work in progress and stage statuses. Check whether the completed work allows the next stage to begin and whether the intended outcome has been achieved.

Agree in advance what counts as complete. If another person must check the work, producing it may not be enough. A shared definition helps everyone interpret the statuses they see in the system consistently.

Consider how tasks contribute to the project outcome. Several small completed tasks do not finish a stage if a required check remains outstanding. The weekly review is an opportunity to resolve that difference between visible activity and actual readiness.

2. What is preventing the remaining work from progressing?

Focus on tasks that have stalled, are overdue or block other work. Establish whether they need information, a decision, another task’s output or someone’s availability.

“Speed up the project” does not identify an action. A more useful agreement is: “The responsible manager will approve the decision by Tuesday so the team can start the next stage on Wednesday.”

Record the action against the project or related task and assign an owner. Its progress can then be followed in the same system.

3. Are the dates still realistic?

Review approaching task and stage deadlines. Assess whether the remaining work can be completed in time and what must happen before it can start.

WiseTeam lets you plan activities in Gantt charts, define dependencies and save baselines: reference plans against which you can compare progress. These help you review the work sequence and identify deviations from the plan.

When an activity slips, identify which later activities are affected. Changing the date should be accompanied by an agreement about the related work and any communication needed with other project participants.

4. Does the allocation of work match the team’s capacity?

A weekly review can reveal that one person has several important assignments due at the same time. Discuss what needs to happen first and whether part of an assignment can move to another team member.

Consider complexity, skills and available time. Five short tasks can take less effort than one demanding task, so task counts alone cannot establish whether workloads are balanced.

When work is reassigned, update responsibilities and dates in the system. Everyone should be able to see what changed and which commitments now apply.

5. Which decisions are needed this week?

Finish the review with specific agreements. Give each action an owner and a deadline. If someone outside the meeting must decide, assign responsibility for contacting them and identify when an answer is needed.

Where the project tracks budget and working time, discuss material variances alongside completed and remaining work. Time spent helps explain effort, but it does not establish whether the intended result has been achieved.

There is no need to examine every area in equal detail each week. Spend more time where the current information shows a deviation or a decision is required.

Example: most tasks are done, but the stage is still open

This hypothetical example illustrates the review process. It does not describe a particular WiseTeam customer project.

A project has four stages: preparation, implementation, checking and completion. Preparation is finished. Within implementation, nine of twelve tasks are marked complete, two are in progress and one has not started.

The statuses visible in the system show the project manager that implementation remains unfinished. Reviewing the outstanding work reveals that the unstarted task needs a decision. That task also affects the start of the checking stage.

During the weekly meeting, the team opens the same project and agrees:

• who will obtain the missing decision and by when;
• which work can continue while the answer is pending;
• whether the checking stage’s start date needs to change.

The agreements are recorded in the system. Once the decision is made and work progresses, the team updates the task and stage statuses. The project manager can see the changed situation without waiting for another weekly report.

A short guide for the weekly discussion

This table is an agenda aid. It does not need to be filled out as a separate report each week; review the answers directly in the system.

Establish a useful review rhythm

Choose a regular weekly time and begin with the work that needs attention. Tasks progressing as expected do not need to be read aloud one by one; their status is available in the system.

For a small project, a 30-minute meeting can be a starting point. Adjust the duration to the size and complexity of the project, and arrange separate discussions for questions that require deeper investigation with specific people.

WiseTeam’s dashboards also support monitoring across multiple projects. An overall view can help managers decide which projects need a closer discussion.

Do not postpone an important issue until the meeting. Live visibility is most useful when the team can respond as soon as a blocker becomes apparent. The weekly review then provides a regular opportunity to assess overall progress and the effect of earlier decisions.

After a few reviews, consider whether discussions are producing clear actions. If the same question keeps returning, check whether the action has an owner, whether that person can resolve it and whether the required information is available. Keep the answer with the relevant work so the next discussion starts from the current position.

Want to see project progress in one place and run weekly reviews using information already in the system? Contact WiseTeam to request a demonstration.

Give it a try yourself – sign up for a 14-day free WiseTeam demo now and begin transforming how you manage your projects.