Running Weekly Meetings Off the Schedule

Most weekly job meetings are run off a meeting-minutes template and memory. The schedule shows up as a printed Gantt nobody opens. That's backwards. The weekly meeting is the one time every week the people doing the work are in the same room, and the schedule is the only document that connects what each of them does to everyone else. This post covers how to run a weekly subcontractor coordination meeting (and an owner-architect-contractor meeting) from the schedule, with an agenda, prep list, and what to capture.

Two meetings, two views

Most jobs have two recurring meetings that should use the schedule differently.

The sub meeting is about who's working where, what's in the way, and what's ready. The OAC meeting is about milestones, decisions the owner or designer owes, and risks to completion. Mixing them makes both worse: subs don't need to hear about the furniture budget, and the owner doesn't need to hear about the drywall crew's hoist schedule.

Prep: what to have ready

Before the sub meeting:

1. A three-week lookahead filtered from the current schedule. See How to Build a Three-Week Lookahead from the CPM Schedule.
2. Last week's lookahead with what was planned to happen, so you can mark what did.
3. The constraint log: open RFIs, submittals, deliveries, inspections, and anything else blocking upcoming work.
4. A short list of critical and near-critical activities in the window, highlighted.
5. Inspection dates and any deliveries scheduled for the window.

Before the OAC meeting:

1. Current forecast for contract milestones versus baseline.
2. The critical path in a sentence or two.
3. A list of owner and design-team decisions needed, with the date each must be answered to avoid affecting the schedule.
4. Any pending change orders with schedule impact.

Prep should take an hour, not a day. If it takes a day, the schedule isn't structured to produce these views. Activity codes for area, trade, and responsibility fix most of that. See Activity Codes, Filters, and Layouts That People Use.

The subcontractor meeting agenda

Keep it under an hour. Go in this order:

1. Safety (5 minutes). Required on most jobs, and it should be first.
2. Look back (10 minutes). Go through last week's planned activities. Did each one happen? If not, why? Record the reason.
3. Critical items (10 minutes). Walk the critical and near-critical activities in the next three weeks. Confirm crews, materials, and access.
4. Look ahead by area (20 minutes). Go floor by floor or area by area. For each activity starting in the next three weeks, confirm the sub is ready and nothing is blocking it.
5. Constraints (10 minutes). Review the constraint log. Assign owners and due dates for anything open.
6. Commitments (5 minutes). Confirm what each sub commits to finish next week.

Running the look back

This is where the meeting earns its time. For each activity planned last week:

Two things come out of this. First, the actual progress for the schedule, which saves you a round of phone calls at month end. Second, a running record of why work doesn't happen as planned. If the same reason keeps showing up (inspections, deliveries, design questions), you've found the thing to fix.

If you track it consistently, this is the basis of percent plan complete. See Percent Plan Complete (PPC) and Reasons for Variance.

Running the look ahead

For each activity starting in the window, ask the responsible foreman three things:

• Are you ready to start on that date? (Crew, materials, equipment.)
• Is the area ready? (Predecessor work complete, access clear.)
• Is anything open that could stop you? (RFIs, submittals, inspections.)

Anything that's a "no" goes on the constraint log with a name and a date. "Electrical needs the L4 ceiling heights clarified, RFI 112, architect to answer by the 14th." That's a constraint someone can act on.

The OAC meeting agenda

1. Milestone status versus baseline and last month.
2. Critical path in plain language: "Steel erection drives metal deck, which drives roofing and dry-in. Dry-in is forecast 3 days behind baseline."
3. Decisions needed from the owner or design team, sorted by the date each is needed.
4. Changes with schedule impact, pending and approved.
5. Risks to milestones, including procurement items like switchgear, elevators, and curtain wall.

The decisions list is the most valuable part. "We need the lobby finish selection by March 3 or the stone order misses the window and lobby finishes push TCO." When it's tied to a schedule date, the owner can see the consequence.

What to record

Meeting minutes should capture, at a minimum:

• Actual starts and finishes reported
• Reasons planned work didn't happen
• New constraints, with owner and due date
• Decisions made and decisions requested, with need-by dates
• Any notice of delay given or discussed

Those records matter later. If the owner's late finish selection delays TCO, the minutes showing when you asked and what date you needed it by are the documentation. Contracts vary on what counts as notice, so don't rely on meeting minutes alone; send formal notice as your contract requires. See Delay Notices.

Feeding it back to the schedule

The weekly meeting should update the schedule, and the schedule should update the meeting. Practically:

• Enter actual starts and finishes from the look back that week, not at month end.
• Adjust remaining durations when a foreman tells you something will take longer.
• Add constraints that affect logic (a late delivery, a failed inspection) to the schedule if they move dates.
• Regenerate the lookahead from the updated schedule for next week's meeting.

When subcontractors can update their own activities directly, a lot of this happens before the meeting. schedule.construction supports that, along with lookaheads and weekly work plans generated from the same schedule, so the meeting and the CPM don't drift apart.

Common problems

• The meeting runs on the minutes template, not the schedule. Open the lookahead first and work from it.
• Everything is discussed at the same level. Keep the sub meeting at activity level and the OAC meeting at milestone level.
• No reasons recorded. "Didn't happen" without a reason teaches you nothing.
• Constraints without owners. An RFI on the log with no one responsible and no date will still be open next week.
• Schedule updated only monthly. By then, the weekly information is three weeks stale.

Key takeaways

• Run the sub meeting from a three-week lookahead and the OAC meeting from milestones and the critical path.
• Look back at last week's plan before looking ahead, and record why work didn't happen.
• Every constraint gets a name and a date.
• Tie owner and design decisions to the schedule date they affect.
• Feed what you learn back into the schedule weekly, not monthly.