Construction progress meetings and field communication field guide

What the meeting structure is, and why the wrong meetings cause delays

A construction project runs on a layered set of meetings, not one. The OAC meeting (owner, architect, contractor) handles the formal decisions and the contract record. The weekly subcontractor coordination meeting lines the trades up for the work ahead. The daily crew huddle gets the people on the slab pointed the right direction before they pick up a tool. Above those sit the milestone and progress reviews that check the job against the plan. Each meeting has a purpose, a short list of the right people, an agenda, and minutes with action items.

Run that set tight and decisions get made, get written down, and get tracked to closure. Run it loose and the same three issues come back week after week while the schedule slips and nobody can point to who owned the fix. That is the whole game. A meeting that ends without a decision and an owner was a meeting that wasted everybody's morning.

This guide sits next to two it does not repeat. The sequence and timing of the work, the critical path, and the look-ahead live in the construction scheduling guide. What the labor and material actually cost as the job runs lives in the job-costing guide. Meetings are where the schedule and the cost get coordinated, decided, and recorded. The contract and the project documents set which meetings are required, how often, and who has to be there.

Why meetings matter, and why bad ones do real damage

Meetings do five jobs nothing else does as well. They coordinate the trades so two crews are not fighting for the same slab on the same morning. They force decisions that would otherwise drift for weeks in email. They build the paper trail that the contract leans on. They catch problems while they are small, when the rebar detail is still a question and not a poured mistake. And they give you the record that defends a delay or a change when the dispute comes.

That is the case for meetings. The case against bad meetings is just as real, and it is the reason crews roll their eyes when you call one. A meeting with no agenda, no decision, and no owner pulls a foreman off the work, costs an hour of crew time he was supposed to be running, and produces nothing he can act on. Do that every week and the field stops taking your meetings seriously, which means the one meeting that actually mattered gets the same half-attention as the four that did not.

So the bar is simple. Every meeting earns its place or it gets cut. The point is never to meet. The point is to make a decision, clear a conflict, or move information that the work depends on, and to do it in less time than it would take to chase the same thing one phone call at a time.

The meeting hierarchy, matched to purpose

Think of the meetings as a hierarchy, each one matched to a decision altitude. The owner or executive review, often monthly, looks at budget, milestones, and the big risks. The OAC meeting, usually weekly or biweekly during active construction, handles progress, RFIs, submittals, changes, and the decisions the design and the contract owe the field. The weekly subcontractor coordination meeting works the next few weeks of field sequence and the conflicts between trades. The daily huddle handles today: the plan, the safety topic, and what changed since yesterday.

The mistake is running every conversation at the wrong altitude. You do not solve a rebar clash in the monthly owner review, and you do not relitigate the project budget in the daily huddle. Push each topic to the meeting built for it. A field sequencing conflict belongs in the coordination meeting. A design question that needs the architect belongs in the OAC. A change in the day's pour plan belongs in the huddle.

Cadence and attendees climb the same ladder. The higher the meeting, the fewer the people, the longer the interval, and the bigger the dollar value of each decision. The lower the meeting, the more often it runs and the more it is about getting hands moving in the next eight hours.

The OAC meeting: the formal one

The OAC meeting is the formal governance forum for the job, and on most commercial and institutional projects the contract names it and sets its frequency. The owner brings financial authority and approves changes. The architect interprets the drawings, answers RFIs, and protects design intent. The contractor reports schedule, cost, subcontractor performance, and what the field is actually finding. The contractor's project manager usually runs it, distributes the agenda ahead, and issues the minutes.

The standing agenda is predictable, which is the point. Review progress against the schedule, walk the open RFI log and push the architect on the ones holding up work, walk the submittal log and flag what is blocking procurement, review pending and approved changes, look at the schedule and the upcoming milestones, and close on the decisions the project needs from the owner and the architect to keep going. Safety and quality usually get a standing slot too.

Hold this meeting weekly during active construction on most jobs, dropping to biweekly in preconstruction or closeout where the contract allows. The decisions made here carry contract weight, so the minutes matter more than in any other meeting on the job. Get them out fast and let them stand as the record.

The weekly subcontractor coordination meeting

The weekly subcontractor coordination meeting is where the next few weeks of field work actually get built before anyone builds them. Gather the trades working in the upcoming window, walk the three-week look-ahead, and turn it into commitments: who is doing what, where, and what each trade needs from the others to start clean. This is the meeting that keeps two crews from showing up for the same area on the same day, and it is the one that most directly protects the schedule. The sequence and look-ahead mechanics live in the construction scheduling guide; this is where they get coordinated face to face.

Get the right person from each trade in the room. The attendee has to have the authority to commit their crew and to answer accurately for their scope. A sub who sends someone who cannot promise a start date or a manpower count is wasting the slot, because the whole purpose is to leave with commitments, not status.

Work the conflicts directly: trade-to-trade sequencing, who needs which area when, material laydown and storage, utility shutoffs and their timing, and the access and hoisting everyone is fighting over. On a concrete job this is where the pre-pour coordination happens, where the rebar, embeds, MEP sleeves, and the inspection all get sequenced so the pour day is not the day you discover a sleeve is missing. Keep it short. Thirty minutes is the target, forty-five on a complex job.

The daily crew huddle

The daily huddle is the short, field-level meeting that gets the crew aligned before the shift. Five to ten minutes, standing up, at the work, run by the foreman or the lead. Cover today's plan, the safety topic for the hazards in the work planned for the day, and what changed since yesterday. Keep it to one safety topic and one clear plan. The moment it runs past ten minutes you have turned a huddle into a meeting and lost the room.

This is the meeting closest to the actual work, and it is the one that catches the small misalignment before it becomes a redo. The huddle is where the foreman says the pour got pushed to the afternoon, the pump is staged on the north side, and the finishers come on at noon, not nine. It is also where a crew member raises the thing nobody upstairs knows about: a form that looks light, an embed that does not match the drawing, an access path that got blocked overnight.

On a pour day the huddle earns its keep. Walk the sequence, who places, who vibrates, who finishes, where the trucks stage, the slump check at the point of placement, and the call on what happens if a truck is late or the weather turns. Then the crew moves as one instead of sorting it out with the first truck already backing in.

Every meeting needs a purpose

Before you put a meeting on the calendar, answer one question: what decision or coordination does this meeting exist to produce? If the honest answer is status that could have been an email or a dashboard, do not hold the meeting. A standing meeting that survives only because it is on the recurring invite is the most common time sink on a job.

Purpose drives the rest. It tells you who actually needs to be there, how long it should run, and what the agenda is. A meeting to clear a trade conflict needs the two foremen and whoever owns the area. A meeting to decide a design change needs the architect and the owner's representative with authority to approve. Put the purpose at the top of the agenda in one sentence so everyone in the room knows what they are there to leave with.

Be willing to cancel. If the conflict cleared itself or the decision is not ripe because the RFI has not come back, cancel the meeting and give the crew the hour back. Holding it anyway, just to keep the streak, trains everyone to treat your meetings as optional.

The standing agenda

A recurring meeting runs on a standing agenda: the same core items every time, in the same order, distributed before the meeting so people show up ready instead of warming up cold. For the OAC those items are progress, RFIs, submittals, changes, schedule, safety, and the open decisions. For coordination it is the look-ahead, the conflicts, and the commitments. The recurring structure is what lets a meeting move fast, because nobody is reinventing the format each week.

Distribute the agenda ahead, ideally with the prior minutes and the current logs attached, so the meeting starts on substance rather than recap. Timebox it. Put rough minutes against the big items and hold to them, and when a topic blows the box, park it and take it offline with the two people who own it rather than letting it eat the room.

Open items carry forward onto the agenda automatically. Last meeting's unfinished actions are this meeting's first review, so nothing quietly drops off the list. That carry-forward, more than anything else on the page, is what turns a meeting from a status update into an accountability tool.

The right people in the room

Get the decision-makers in the room and keep everyone else out. A meeting works when the people present can actually commit: approve the change, promise the crew, answer for the scope. It fails when the room is full of people who have to go ask someone else, because then nothing gets decided and you are scheduling a second meeting to do what the first one was for.

Too many people is its own cost, and it is a cost people underestimate. Ten people in a one-hour meeting is ten hours of paid time, and most of them are listening to items that have nothing to do with their scope. The bigger the room, the slower the decision and the more the meeting drifts into a status broadcast. Invite by agenda item if you have to, so the electrical foreman comes for the twenty minutes that touch his work and gets back to running his crew.

The hard version of this rule is sending a representative who can actually commit, not a warm body to fill the chair. A sub who sends a foreman with no authority to promise a date has emptied the meeting of its point.

Minutes: the record of what was decided

Minutes are the official record of the meeting: what was decided, who owns each action, by when, and what stayed open. They are not a transcript. Nobody needs a paragraph of who said what. They need the decisions, the action items with owners and due dates, and the carry-forward of open items, written so a person who missed the meeting can act from them.

Capture the basics at the top: date, who attended, the agenda. Then the substance: each decision, each action item with one owner and a firm due date, and the running open-items list. Issue them fast. The common standard is within 24 hours, and the reason is mechanical. Delayed minutes mean delayed action items, and a delayed action item is a delayed job. Minutes that land a week later are a history lesson, not a tool.

Distribute the minutes to everyone who was there and everyone an action lands on, and let them stand corrected. If someone disagrees with what the minutes say, they speak up against this set, in writing, before the next meeting. Silence is how the minutes become the agreed record, which is exactly the weight you want them to carry when a dispute shows up later.

Action items: owner and due date, tracked to closure

An action item that does not name one owner and one due date is not an action item. It is a wish. Every item out of a meeting needs a single specific task, one person accountable for it, and a firm date or milestone it is due against. Two owners means no owner, because each assumes the other has it. No date means it slides forever, because there is never a day it is officially late.

Track each item to closure, not just to assignment. The whole value is in the follow-through, and follow-through is the part most meetings skip. The mechanism is the open-items log carried meeting to meeting: every item stays on the list, visible, until it is done, so nothing falls through the gap between two meetings. An item is not closed because it was discussed again. It is closed because the task is finished and the log says so.

This is where a field tool earns its place. Keeping the open-items and action log in a shared system like FieldOS, where each item has an owner, a due date, and a status that everyone sees, beats a personal notebook and a memory. The log lives in one place, it carries forward on its own, and the overdue items are obvious instead of buried in last month's minutes.

The open-items log

The open-items log is the running list of everything the project owes itself: the unanswered questions, the unmade decisions, the unfinished actions. It is one list, it carries from meeting to meeting, and it is the single best defense against things falling through the cracks. Anything raised that is not resolved on the spot goes on it with an owner and a date, and it does not come off until it is genuinely done.

The discipline is that the log is reviewed first, every meeting, before any new business. You walk the open items, update the status, close what is finished, and escalate what is stuck. That review is what creates accountability, because an owner sees their item on the screen, aging, in front of the whole room. Nobody likes carrying the same overdue line for three weeks running.

Number the items and keep the number stable across meetings so people can reference item 47 and everyone knows which one. A log where the numbering resets or items quietly vanish is a log nobody trusts, and a log nobody trusts gets ignored.

The decisions log

Track decisions separately from open actions: what was decided, who made it, when, and on what basis. Decisions drive the schedule and the cost, so the record of them is what you reach for when someone asks six months later why the slab edge moved or why the spec changed. The decision log answers that without anybody relying on memory.

The reason to log the decision-maker is accountability and authority both. A change the owner approved is a different animal from a field call the foreman made, and when a dispute or a back-charge comes around, who had the authority to decide matters as much as what was decided. A decision recorded with the name attached is a decision that holds up.

Decisions and the schedule move together. A decision delayed is a schedule delayed, which is why the open RFIs and the pending decisions that sit on the critical path get the most pressure in the meeting. The scheduling guide covers how a late decision eats float and moves the finish; the meeting is where you catch it before it does.

Reviewing RFI and submittal status

Review the RFI and submittal logs in the meeting, every time, because both are where the work quietly gets blocked. An RFI is the contractor's formal written question when the drawings or specs are unclear, conflicting, or missing a detail. The RFI log tracks the open ones, and the meeting is where you push the architect on the answers that field work is waiting on. An RFI sitting unanswered for three weeks is a stop sign nobody is looking at until the crew hits it.

Submittals are the same story from the procurement side. The submittal log tracks the approval status of the materials, products, and shop drawings sent to the architect for review, and a delayed approval can push delivery back by weeks. So the meeting watches the backlog and flags the items holding up the long-lead procurement before the lead time becomes a schedule problem.

Tie both logs to the schedule. The RFI or submittal that matters most is the one feeding an activity on the critical path, so review them against the look-ahead, not as a generic list. The bottleneck is rarely the count of open items. It is the one open item sitting in front of the next pour.

Reviewing the schedule and the look-ahead

Every progress meeting reviews the schedule, and the review has two jobs: confirm what got done against the plan, and find the slip while you can still recover it. Walk the critical path first, because a slip there moves the finish date and a slip off it usually does not. The full mechanics of the critical path, float, and the baseline live in the construction scheduling guide; the meeting is where the schedule meets the people who have to make it real.

The three-week look-ahead is what drives the coordination meeting. It is the near window the field actually builds from, and it answers the questions the trades need answered: what is coming, what has to be ready first, and which constraints are still in the way. Walk it forward, name the constraints, and assign someone to clear each one before the activity it blocks comes due.

Keep the schedule conversation honest. A status of percent complete that everyone nods at without checking is how a job convinces itself it is fine right up until the milestone it misses. Tie the review to what is physically in place, walk the worst-case path, which is usually the longest run off the most distant work, and surface the slip as a number, not a feeling.

Safety as a standing item

Safety is a standing agenda item in every meeting layer, not a topic you reach for after an incident. In the OAC it is the safety report and the open corrective actions. In the coordination meeting it is the trade-overlap hazards, the work happening overhead, and the shared exposures nobody trade owns alone. In the daily huddle it is the pre-task plan for the specific hazards in the work planned for the day, which is the version that actually protects the crew about to do it.

The daily safety talk is short and focused: one hazard, one safe practice, tied to what the crew is doing in the next eight hours. Documented talks matter beyond the safety value, because signed records of the topic, date, and attendees are commonly accepted by inspectors as evidence that hazard communication happened. On a concrete job that pre-task talk covers the real exposures: silica dust, the pump line and its whip, rebar caps, the placing boom near power lines, and the lift in and out of the pour.

When an incident or a near-miss happens, it goes into the meeting fast, with the corrective action assigned to an owner and a date like any other action item. Safety that lives only on a poster is safety nobody is tracking.

Minutes as a contract record and a delay-claim defense

Meeting minutes are a project record with contract weight, and on a disputed job they are some of the strongest evidence you have. The standard practice of distribute, then let stand corrected, is what gives them that weight. Minutes that go out promptly and draw no written objection before the next meeting become the agreed account of what was decided, what was owed, and when. That is exactly what you want in hand when a delay or a change becomes a claim.

The contract sets the rules around this, so hedge to it. Many projects run on AIA-style general conditions, and the formal notice of claims those documents require is its own process with its own delivery method, separate from routine meeting minutes. Minutes are powerful contemporaneous evidence; they are not a substitute for the contractual notice a claim demands. Read the contract for what notice it requires, in what form, and to whom.

For a delay claim, the value of the minutes is the contemporaneous record they build over time: when the RFI was raised, when the answer came back, when the decision was made, who owed what and missed it. A claim built from records written as the job happened beats one reconstructed from memory after the fact, every time. Write the minutes as if a lawyer will read them, because one might.

Virtual and hybrid meetings

Remote and hybrid meetings are normal now, and they work for the office-heavy meetings where people are reading logs and screens anyway. The OAC and the owner review run fine with the architect dialed in and the schedule and logs shared on screen, which saves the windshield time of getting everyone to one trailer. Share the agenda, the logs, and the minutes in the same shared system so the remote people see exactly what the room sees.

The field meetings resist going virtual, and for good reason. The daily huddle belongs at the work, standing up, where the crew can point at the form and the foreman can see who is paying attention. A coordination meeting can be hybrid, but the trades sequencing a tight area often need to be looking at the same drawing or the same slab together. Match the tool to the meeting. Office decisions tolerate a screen; field coordination usually wants boots on the deck.

Setting and holding the cadence

Set the cadence and hold it. Daily for the huddle, weekly for coordination and usually the OAC, monthly for the owner review. Same day, same time, every week, so the meeting becomes a rhythm people plan their work around instead of a surprise that interrupts it. A predictable cadence is worth more than a perfect agenda, because the crew that knows the coordination meeting is every Monday at seven shows up ready for it.

The cadence holds even when a given week feels light. If you cancel the moment there is not much to discuss, you teach everyone the meeting is optional, and then the week it matters they have already mentally dropped it. Hold the slot. If there is genuinely nothing to coordinate, end it in ten minutes. A short meeting that ran on schedule protects the habit; a canceled one erodes it.

The contract often sets the floor for cadence on the formal meetings, naming the OAC and its frequency. Meet at least what the contract requires, and add the field-level meetings the work needs on top of that. The rhythm is what keeps decisions from piling up between meetings into a backlog nobody can clear in one sitting.

Common meeting failures

Most bad meetings fail in one of a few predictable ways, and once you can name them you can catch them. No agenda, so the meeting rambles and runs long while the real decisions never surface. No minutes, or minutes with no action owners, so nothing that was decided actually moves. The wrong people in the room, or too many, so either no one can decide or the decision drowns in a status broadcast.

Then the failures of follow-through. Decisions get made but never tracked, so the same question comes back two meetings later as if it were new. Action items get assigned but nobody closes them, so the open-items log grows until people stop reading it. And the worst one: holding the meeting just to meet, with no purpose behind it, which trains everyone that your meetings are a tax on their day rather than a tool that helps them.

The fix for all of them is the same short discipline. A purpose at the top, an agenda distributed ahead, the right people only, minutes with owners and due dates out fast, and an open-items log reviewed first thing every meeting. Do those and the failures mostly disappear, because each one is a missing piece of that discipline.

Communication beyond the meeting

Meetings are not the only communication on a job, and a project that tries to handle everything in meetings either meets constantly or lets information rot between meetings. The daily report is the running record of what happened on site: crews, weather, deliveries, work done, delays, and visitors. It is the contemporaneous log that feeds the schedule update and backs a delay claim alongside the minutes, and it is covered from the cost and tracking side in the job-costing guide.

Set the channels and use them for what they are good at. The decision goes in the minutes and the log, not buried in a text thread nobody can find later. The urgent field change goes by phone or radio to the people it touches right now, then gets confirmed in writing. The routine update goes in the daily report. The standing question goes on the open-items log for the next meeting.

When something changes, over-communicate it. The cost of telling three people who did not strictly need to know is a minute. The cost of the one person who needed to know and did not is a redo, a clash, or a crew standing around. A change to the pour schedule, the access, or the sequence is exactly the kind of thing to push hard rather than assume traveled.

The records that hold the project together

Four documents carry the meeting structure: the agendas, the minutes, the action-item and open-items log, and the decisions log. Together they are the project's memory and its accountability, and they are what a dispute, an audit, or a new team member reaches for to reconstruct what happened and why. Keep them in one shared place, current, and searchable, not scattered across inboxes and notebooks.

This is where a field tool pays off. Running the agendas, minutes, action items, and decisions in a system like FieldOS, where the open items carry forward on their own and every action has a visible owner, due date, and status, beats reconstructing the thread from email every week. The record stays in one place, the overdue items are obvious, and the carry-forward happens without anyone retyping last week's list.

Field checklist for running a meeting

Common mistakes

• Running with no agenda, so the meeting rambles and the real decisions never get made.
• Producing no minutes, or minutes with no action-item owners and no due dates.
• Filling the room with the wrong people, or too many, so nothing gets decided.
• Making decisions but never tracking them, so the same question returns weeks later.
• Letting the cadence slip by canceling whenever a week feels light.
• Holding a meeting with no real purpose, which trains the crew to tune your meetings out.

Standards and references

There is no single code that governs how you run a meeting, so the references here are practice and contract, not a mandate. Construction management bodies such as CMAA, and project management practice from PMI, lay out the meeting hygiene this guide follows: a purpose and an agenda, the right attendees, minutes with action items, and tracking to closure. Treat them as the established way the work is run, not as an enforceable spec.

The contract is what actually binds you, and it usually names the formal meetings. Many commercial projects run on AIA-style general conditions, which set the framework for progress meetings, RFIs, submittals, changes, and the claims and notice process. Read the contract for which meetings are required, how often, who must attend, and what notice a claim demands, because the contract overrides any general practice, and the project specifications can tighten it further.

For accountability, the RACI model (responsible, accountable, consulted, informed) is the common reference, and its core rule maps straight onto action items: one person is accountable for each, and that single owner is what keeps an item from drifting. The discipline that matters across all of it is the same: match each meeting to its purpose with an agenda, write minutes with owners and due dates, and hold the cadence while you track the decisions. Confirm the specifics against the contract and the project, which control.

Terms

The meeting vocabulary is consistent across most projects, but the contract can define a term more narrowly, so read it for the project's own usage.

These are the terms that show up in the agendas, the minutes, and the logs, defined the way the field uses them.

OAC meeting

The owner-architect-contractor meeting, the formal progress and decision forum, usually weekly or biweekly during active construction

Agenda

The list of items and the purpose for a meeting, distributed ahead so people arrive ready

Minutes

The official record of a meeting: decisions, attendees, action items, and open items, issued and allowed to stand corrected

Action item

A single specific task with one accountable owner and a firm due date, tracked to closure

Open-items log

The running list of unresolved questions, decisions, and actions, carried meeting to meeting until each is done

Decisions log

The record of what was decided, by whom, when, and on what basis, separate from open actions

Cadence

The fixed rhythm of a recurring meeting, such as daily, weekly, or monthly, held at the same time

Look-ahead

The near-term window, commonly three weeks, the field builds from, with constraints named and cleared

Related tools

Calculators and readiness checks for this work

Compare your options

FAQ

People also ask

• What is the critical path?
• What is job costing?
• Why do bridge decks deteriorate faster than the rest of the bridge?
• How is a commercial concrete pool built?
• What is the difference between mortar and grout in a block wall?