The Progress Meeting Playbook: 7 Questions to Keep Your Project Afloat

Progress meetings are the pulse of any construction project. When they work, they surface problems early, align trades, and keep the schedule honest. When they don't, they become expensive status-readings where people recite last week's log and dodge bad news. The difference between the two is structure—specifically, the questions you ask. This playbook gives you seven questions that turn a routine check-in into a project-saving tool. Use them as a template, adapt them to your phase and contract type, and watch how quickly the tone shifts from reporting to problem-solving.

1. Why Most Progress Meetings Fail and Who Needs This Fix

If your progress meeting feels like a round-robin of reading minutes, you're not alone. Many teams default to a format where each person reports what they did, what they plan to do, and what's blocking them. That sounds logical, but it often produces a laundry list of minor updates while the real risks stay hidden. The person who is behind schedule may downplay it. The subcontractor who needs a drawing revision may not mention it until the last minute. The structural steel delivery that slipped by two weeks might be buried in a spreadsheet that nobody opened.

This playbook is for project managers, site supervisors, and coordinators who run or attend weekly progress meetings on commercial, residential, or infrastructure projects. It's also for owners and consultants who want to hold the contractor accountable without micromanaging. If you've ever left a meeting wondering what actually got decided, or if you've sat through an hour of updates only to realize the critical path is still unclear, these questions are for you.

The core problem is that humans avoid delivering bad news in a group setting. Without a structured inquiry, a progress meeting can become a performance where everyone looks competent while the project drifts. The seven questions below are designed to create a safe but rigorous environment. They force specificity, expose assumptions, and make it hard to hide behind vague language like "we're making good progress."

What goes wrong without this structure? Missed deadlines, budget overruns, and rework. A delay in foundation work that is caught at the weekly meeting might cost a few days. The same delay caught four weeks later, after the concrete crew has been mobilized and the steel fabricator has cut material, can cost weeks and thousands in change orders. The cost of not asking the right questions compounds fast.

2. What to Settle Before the First Question

Before you run the seven-question format, you need a few things in place. First, a single source of truth for the schedule. That doesn't mean a perfect Gantt chart—it means a current, agreed-upon baseline that everyone references. If your schedule is three weeks out of date, the questions will produce answers that don't match reality. Spend thirty minutes before the meeting updating the critical path and the next two weeks of activities.

Second, a one-page dashboard or progress report that includes the following: planned vs. actual start/finish for each work package, percent complete, and a list of open issues with owners and due dates. This dashboard is not a novel—it should fit on a single sheet or screen. The meeting should not be spent reading it; participants should have reviewed it beforehand. The questions build on the dashboard, they don't replace it.

Third, clear roles: who facilitates, who takes notes, and who makes decisions. The facilitator should not be the person who is also reporting on their own work. Ideally, it's the project manager or a dedicated meeting lead. The note-taker captures decisions and action items, not every word. The decision-maker—often the owner's representative or the general superintendent—must be present or delegated. If the person who can approve a change order or a schedule shift is absent, the meeting loses its power to resolve issues.

Fourth, a rule about time. A progress meeting for a medium-sized project (say, 20–50 people on site) should run no more than 60 minutes. For smaller projects, 30 minutes. For large or complex projects, 90 minutes max, with a strict agenda. The seven questions can be covered in 45 minutes if everyone comes prepared. If you find yourself running over, the problem is usually not the questions—it's that people are using the meeting to discover information they should have found beforehand.

Finally, establish a norm that bad news is rewarded, not punished. This is the hardest cultural shift. If a subcontractor reports a delay and gets blamed or penalized, they will stop reporting delays. The project manager must model the behavior: thank someone for surfacing a problem early, then focus on solutions, not blame. Over time, the quality of information improves dramatically.

3. The Seven Questions: Core Workflow

These seven questions are designed to be asked in order. They move from broad to specific, from past to future, and from individual to system. Adapt the wording to your project's phase and contract type, but keep the logic intact.

Question 1: What was supposed to happen since our last meeting, and what actually happened?

This is the baseline check. It forces a comparison between planned and actual progress. The answer should reference the schedule and the dashboard, not general impressions. If the answer is "we're on track," ask for the evidence: which milestones were completed, which started late, which are behind. If the answer is vague, probe gently. The goal is to get a factual picture, not a comfortable one.

Question 2: What is the single biggest risk to completing the next milestone on time?

This question surfaces the top concern. It prevents the meeting from drowning in minor issues. Each person should name one risk—not a list. If multiple people name the same risk, that's a signal. If someone says "nothing," they may not be looking hard enough. Common risks include material delays, weather, design changes, labor shortages, and inspection bottlenecks.

Question 3: What decisions are needed this week to keep work moving?

Progress stops when decisions stall. This question identifies which choices—from design approvals to material substitutions to sequence changes—are blocking the next step. Assign an owner and a deadline for each decision. If the decision requires input from someone not in the room, note that and escalate.

Question 4: Are there any changes to scope, budget, or schedule that have not been formally documented?

Scope creep is a silent killer. This question catches verbal agreements, field changes, and informal additions that haven't gone through change control. It also surfaces potential claims before they become disputes. If someone says "we agreed to add an extra outlet," that needs a change order. If it's not documented, it's a risk.

Question 5: What did we learn from the last week that should change how we work going forward?

This is the continuous improvement question. It could be a lesson about a supplier's lead time, a better way to sequence two trades, or a communication gap that caused rework. Capture it and decide whether to update the project's procedures or simply adjust the next week's plan.

Question 6: Who is not in this room that we need to hear from?

Progress meetings often include the same people every week, but the missing voices matter. The electrician's foreman might have a different view than the project manager. The supplier's sales rep might know about a shortage that the buyer doesn't. This question reminds the team to check in with those who are not present, either by calling them during the meeting or scheduling a follow-up.

Question 7: What is our commitment for the next week—exactly?

End with clear, specific commitments. Not "we'll try to pour the slab" but "we will pour the slab on Thursday if the inspection passes Wednesday." Each commitment should have a single owner and a deadline. Write them down, distribute them within an hour, and start the next meeting by reviewing them.

4. Tools, Setup, and Environment Realities

The seven questions work best with a few supporting tools. A shared digital dashboard, like a simple Google Sheet or a project management platform, allows everyone to see the same data in real time. The dashboard should include a column for each question's answer, updated before the meeting. This reduces the time spent on data entry during the meeting and lets the team focus on discussion.

For on-site meetings, a physical whiteboard can be effective. Write the seven questions on the board, and fill in answers as you go. This keeps the group focused and creates a visual record. For remote or hybrid teams, use a shared screen with a live document. Avoid PowerPoint slides that are read aloud—that's a lecture, not a meeting.

The physical environment matters. Hold the meeting in a room near the site, with a view of the work if possible. If you're in a trailer, make sure the whiteboard is visible and the Wi-Fi works. If you're on a video call, require cameras on and mute when not speaking. The worst setup is a conference room with a long table where people sit in the same seats every week and fall into a passive listening mode. Change the seating occasionally. Ask different people to lead each question.

One practical tip: start the meeting with a two-minute safety moment or a positive observation from the site. This sets a constructive tone. Then move directly into Question 1. Do not allow a long preamble or a recap of the agenda. The agenda is the seven questions.

For projects with multiple subcontractors, consider a tiered approach. Hold a 15-minute huddle with each trade separately before the main meeting, then bring the highlights to the full group. This avoids boring people with details that don't affect them while still giving everyone a voice.

5. Variations for Different Project Constraints

Not every project can follow the same script. Here are three common variations and how to adapt the seven questions.

Fast-track or design-build projects

On a fast-track project, the schedule is compressed and design is still evolving. The risk question (Question 2) becomes even more critical. You may need to ask it twice: once for design risks and once for construction risks. The decision question (Question 3) should include a deadline for each decision, because a delay of one day can cascade. Consider adding an eighth question: "What assumptions are we making that could be wrong?" This helps catch optimistic scheduling.

Remote or distributed teams

When the project team is spread across sites or time zones, the meeting format needs extra discipline. Send the dashboard 24 hours in advance. Require written answers to the seven questions before the meeting. During the call, do not read the answers—discuss only the exceptions and the risks. Keep the call to 30 minutes. Record it for those who cannot attend live. The biggest risk with remote teams is that people multitask and miss key decisions. To counter this, start with a quick check-in: each person says one word about how the project is going. This builds connection.

Small projects or tight budgets

If you're managing a small renovation or a single trade, you don't need a full hour. Condense the seven questions into a 15-minute stand-up. Do them at the same time every day or every other day. Use a whiteboard or a notebook. Skip Question 5 (lessons learned) if time is tight, but keep Questions 1, 2, and 7. The key is consistency: even a short, structured check-in beats a long, unstructured one.

6. Pitfalls, Debugging, and What to Check When It Fails

The seven-question format is not foolproof. Here are common failure modes and how to fix them.

Pitfall 1: People give optimistic answers. If everyone always says "on track" but the project is slipping, you have a culture problem. The fix is to ask for evidence. When someone says "on track," ask "What percentage complete?" and compare to the planned percentage. If there's a gap, explore it. Also, rotate who answers first. If the same person always starts, others may follow their tone.

Pitfall 2: The meeting becomes a blame session. If Question 1 turns into finger-pointing, the facilitator must redirect. The focus should be on facts and solutions, not fault. Use language like "What can we do to get back on track?" rather than "Who caused this delay?" If blame persists, take the discussion offline.

Pitfall 3: Action items are not followed up. This is the most common failure. The meeting produces a list of commitments, but nobody checks them before the next meeting. The fix is to start each meeting by reviewing the previous week's commitments. If they weren't done, ask why and adjust. If the same items appear week after week, escalate to a higher authority or change the approach.

Pitfall 4: The questions feel mechanical. If the team is just going through the motions, the format has become stale. Shake it up: change the order, add a visual exercise (like drawing the critical path on a whiteboard), or invite a guest from a different trade. Sometimes, simply asking "What would we say if we were being completely honest?" can break the routine.

If the meeting consistently fails to produce better outcomes, step back and diagnose. Is the schedule accurate? Is the dashboard being used? Are the right people attending? Are decisions actually being made? The seven questions are a tool, not a cure-all. They work best when the foundational elements—trust, data, and accountability—are already in place.

7. Common Mistakes and a Quick Checklist

Even with a good process, teams make recurring mistakes. Here are the most common ones, along with a checklist to keep your meetings on track.

Mistake 1: Using the meeting to distribute information

If you're reading the schedule or the dashboard during the meeting, you're wasting time. Information distribution should happen before the meeting. The meeting is for interpretation, risk assessment, and decision-making. If participants haven't read the pre-read, start the meeting anyway and let them catch up. Over time, they will learn to come prepared.

Mistake 2: Letting one person dominate

In many meetings, the loudest voice or the highest-ranking person sets the tone. This can suppress dissenting views. The facilitator should actively invite input from quieter members. Use a round-robin format for Question 2, where each person speaks in turn. If the boss speaks first, others may echo. Have the boss speak last.

Mistake 3: Not documenting decisions and action items

A meeting without a record is a conversation. Assign a note-taker who captures decisions, action items, owners, and deadlines. Distribute the notes within an hour of the meeting. If you wait a day, people forget. Use a template that mirrors the seven questions, so the notes are easy to scan.

Quick checklist for your next meeting:

• Did everyone receive the dashboard at least 24 hours before?
• Is the schedule updated to reflect actual progress?
• Are the seven questions visible (on screen or whiteboard)?
• Is the facilitator neutral (not reporting their own work)?
• Is the decision-maker present?
• Are we starting and ending on time?
• Are we capturing commitments and assigning owners?
• Are we rewarding bad news, not punishing it?

If you can answer yes to at least six of these, your meeting is likely productive. If not, pick one or two to improve next week.

8. What to Do Next: Specific Actions for This Week

Reading a playbook is not the same as running the play. Here are three concrete steps to implement the seven-question format starting this week.

Step 1: Design your one-page dashboard. This week, create a simple template that includes the next two weeks of activities, planned vs. actual dates, percent complete, and a section for open issues. Use a spreadsheet or a project management tool. Share it with your team and ask them to update it before the next meeting. Keep it to one page—no more.

Step 2: Run a pilot meeting using the seven questions. Announce to your team that you're trying a new format. Print the seven questions on a handout or display them on the wall. Go through them in order. At the end, ask for feedback: what worked, what felt awkward, what would they change? Adjust based on their input. The first meeting may feel clunky, but that's normal.

Step 3: Create a follow-up habit. Within one hour after the meeting, send a summary that includes the commitments made for the next week. Use the same format each time. At the start of the next meeting, review those commitments before moving to Question 1. If a commitment was missed, discuss why and adjust the plan. This loop of commitment and review is what turns a meeting into a progress engine.

Finally, measure the impact. After four weeks, compare your project's schedule performance and issue resolution time to the previous four weeks. If you see improvement, keep the format. If not, revisit the prerequisites: is the schedule realistic? Is the dashboard being used? Are people honest about risks? The questions are only as good as the data and culture behind them.