Project management

How to run an effective weekly construction meeting

An effective weekly construction meeting starts on time, follows the same agenda every week, works from the look-ahead schedule and open-item logs, ends with every action item assigned to a person and a date, and has minutes out within a day.

Two construction professionals review paper plans beside a tablet at a jobsite workbench.
Plan reviews connect field conditions, drawings, and the next decisions on a job. AI-generated illustration.

To run an effective weekly construction meeting, use one fixed agenda, start and stop on time, and spend the hour on what is coming rather than what already happened. Review safety, the three-week look-ahead, open RFIs and submittals, pending changes, and problems that need a decision. Every item that comes up leaves the room with an owner and a due date, and minutes go out within 24 hours. If the same items appear week after week with no movement, the meeting is a status report, not a management tool.

There are usually two weekly meetings on a commercial job: the subcontractor coordination meeting run by the superintendent, and the owner, architect, and contractor meeting (often called the OAC meeting) run by the project manager. The structure below works for both. The emphasis changes.

Weekly construction meeting agenda

Sample weekly agenda (about 60 minutes)
ItemMinutesWhat to cover
Safety5Incidents, near misses, upcoming high-risk work
Old business10Last week's action items: done, not done, new date
Look-ahead schedule15Next three weeks by area, constraints, manpower
RFIs and submittals10Overdue and due in next two weeks only
Changes10Pending change requests, pricing status, decisions needed
Quality and inspections5Upcoming inspections, failed items, testing
New business and decisions5Anything needing a decision before next week

How to run the meeting in 7 steps

  1. Fix the day, time, and length. Same slot every week. People plan around a meeting that is predictable and short.
  2. Send the agenda and logs a day ahead. Include last week's action items, the three-week look-ahead, and the open RFI, submittal, and change logs.
  3. Start with safety. It sets the tone and keeps safety from becoming the item that gets cut when time runs short.
  4. Clear old action items first. Each one is done, or it gets a new date and a reason. Items that slip twice get escalated.
  5. Spend the most time on the look-ahead. For each activity: is the area ready, is material on site, is information complete, is the crew available. Constraints become action items.
  6. Make decisions or schedule them. If a decision needs people not in the room, assign someone to get it by a set date. Do not let a 20-minute debate eat the agenda; take it offline.
  7. Send minutes within 24 hours. Numbered items carried week to week, with owner and due date. Ask for corrections by a set date so the minutes become the record.

Sub coordination meeting vs. OAC meeting

The sub coordination meeting is about the work: sequencing, access, manpower, and who is in whose way. Foremen should attend, not just office staff, because they know what is really happening. Keep it practical and walk the site afterward if there is a sequencing argument.

The OAC meeting is about decisions and money: RFIs the owner or design team owes, change orders waiting for approval, schedule status against milestones, and owner-furnished items. The PM should bring a short list of what the contractor needs from the owner and architect this week, by name and date. On federal work the schedule itself is a contract obligation; FAR 52.236-15 requires the contractor to submit a progress schedule and record actual progress on it as the contracting officer directs, and if the contractor falls behind, the contracting officer can require more shifts, overtime, or equipment at no added cost to the government. Keeping the schedule current week to week makes those conversations factual.

Worked example: turning a stalled meeting around

Here is an example. A GC is building a $3.4 million charter school addition. The OAC meeting runs 2 hours, the minutes are 9 pages, and RFI 18 (the gym floor finish) has been on the list for five weeks. Nobody is sure who owes the answer.

The PM restructures. Minutes shrink to an action list with numbered items, each with one name and one date. Overdue items go at the top in bold. The RFI section shows only items past their needed-by date and items due in the next two weeks. For RFI 18, the minutes now read: "Owner to confirm gym floor finish selection by 3/14. Flooring sub needs answer by 3/21 to hold the May install date." The owner's rep sees her name and date in bold the next week and answers before the meeting.

Within a month the meeting is down to about an hour, and the count of overdue items has fallen. Nothing about the project changed. The meeting started producing decisions instead of discussion.

Running the meeting when people join remotely

Many OAC meetings now include an architect or owner's rep on a video call. That works if the screen shows the same thing everyone in the trailer is looking at: the action list and the look-ahead, scrolled by the person running the meeting. Ask remote attendees to stay on camera for decisions, and read each new action item aloud with its name and date before moving on. Record the decision in the minutes, not just in the call recording, since nobody will search an hour of video six months from now. If remote attendees keep missing, the decision list goes to them by email the same afternoon.

Mistakes to avoid

  • Reviewing every open item every week. Focus on overdue items and items due soon. The full logs are attached for anyone who wants them.
  • Action items assigned to companies. "Architect to answer" goes nowhere. Name the person.
  • Minutes written days later. By then, people remember different versions of the meeting.
  • Letting the meeting become the only communication. Urgent problems should not wait for Tuesday.
  • No owner attendance. If the owner's decision-maker never comes, send a separate weekly email listing decisions needed with dates and cost or schedule impacts.
  • Discussing money in front of subs. Keep change order pricing and payment issues for the OAC meeting.
  • Skipping the meeting when things are going well. A short meeting during a smooth week is when you catch next month's problem. Keep the slot, even if it only runs 20 minutes.

Templates, terms, and tools

Use the construction meeting minutes template and the three-week look-ahead template. Keep the RFI log template and change order log template attached to every agenda. Related terms: look-ahead schedule, critical path method, and owner's representative. If the schedule is updated weekly, see how to update a construction schedule every week.

Smart Business Automator pulls open RFIs, submittals, and change orders for each job into one view so the meeting agenda builds itself, and action items stay tied to the job until they close. See construction workflow automation.

Frequently asked questions

How long should a weekly construction meeting be?

Most teams aim for about an hour. If meetings regularly run over, cut the agenda to overdue and upcoming items and move technical discussions to separate, smaller meetings.

Who should run the weekly construction meeting?

The superintendent typically runs the subcontractor coordination meeting. The project manager typically runs the owner, architect, and contractor (OAC) meeting. On some projects the architect or owner's representative runs the OAC meeting.

Who writes the meeting minutes?

Usually the party running the meeting, often the contractor's project engineer or PM. Whoever writes them should send them quickly and ask attendees to submit corrections by a set date.

What is an OAC meeting?

An owner, architect, and contractor meeting, usually held weekly or every other week, to review progress, open questions, changes, and decisions needed from the owner and design team.

Should subcontractors attend the OAC meeting?

Usually not every week. Bring specific subs when their scope is on the agenda, such as a mechanical sub for a coordination problem or a long lead submittal.

Sources

  1. Acquisition.gov: FAR 52.236-15 Schedules for Construction Contracts
Written and edited by

Maurice Francois writes and edits construction operations guides for Smart Business Automator. More from Maurice on the Scaling Legends podcast.

Get a free assessment