OAC meetings that move the job: turn the owner-architect-contractor meeting into a decision machine

The Decide-Don't-Report method

The principle is simple: status information is distributed before the meeting, and the meeting is used for decisions, risks and coordination that need the three parties in the same room.

1. Pre-read, sent 24 to 48 hours before

• Updated look-ahead schedule and milestone status.
• RFI log with ages and items overdue.
• Submittal log with items awaiting review and their procurement impact.
• Change order and pending change log with amounts and status.
• Owner decisions required, with the date each is needed.
• Photos of progress and issues.

2. A decision-first agenda

The meeting starts with decisions needed, not with a walk through every trade. Items that do not need discussion are not discussed.

3. Every item leaves with an owner and a date

No item is closed as "will look into it." It becomes "architect to respond to RFI 047 by Thursday" or "owner to confirm finish selection by the 12th."

4. Minutes within 24 hours

Short, action-oriented minutes with a clear statement of decisions and assignments, sent the next business day with a request to report corrections within a set period.

A 60-minute agenda that works

• 5 minutes — Safety and site issues that affect all parties.
• 10 minutes — Schedule: milestone status, critical path risks and what the look-ahead needs from the owner and design team.
• 15 minutes — Decisions required: owner selections, design clarifications, scope questions, with dates needed.
• 10 minutes — RFIs and submittals that are overdue or on the critical path only.
• 10 minutes — Changes and cost: pending changes needing direction, approved change orders, budget and contingency status.
• 5 minutes — Quality, inspections and permits.
• 5 minutes — Action review: read back every assignment, owner and date.

Who should be in the room

Too many attendees slow the meeting; too few leave decisions without anyone able to make them. The core group is the owner's decision-maker or representative, the architect's project lead, the contractor's project manager and superintendent. Invite consultants, major subcontractors or the owner's facilities team only for the agenda items that need them, and let them join for that part of the meeting. If the owner's representative cannot make decisions above a certain value, identify in advance who can, and schedule a separate decision call when needed instead of carrying the item for weeks.

Framing decisions so they actually get made

Owners and architects postpone decisions when the question is vague. Present each decision in the same format:

• The question: one sentence.
• The options: two or three, with cost and schedule effect for each.
• The recommendation and the reason.
• The date the decision is needed to avoid impact, tied to the look-ahead or procurement lead time.
• The consequence of no decision by that date.

"We need the lobby tile selection by May 10 to hold the eight-week lead time and the June 30 finish date; option A is in budget, option B adds $14,000 and two weeks" gets decided. "Any update on the lobby tile?" does not.

RFIs and submittals in the OAC

Do not read the RFI log aloud. Bring only the items that are overdue, on the critical path or disputed, and for each state the date the answer is needed and the effect if it is late. Track average response times over the project and share them respectfully; they often explain schedule pressure better than any argument. See RFIs and requests for information and submittals and shop drawings.

Changes and money

The OAC is where pending changes get direction. For each pending change, report the estimated cost, schedule effect, status of pricing and what authorization is needed to proceed. Never rely on a verbal "go ahead" in the meeting without documenting it — record the direction in the minutes and follow the contract's change process to get written authorization. See change orders.

Minutes that protect the project

• Numbered items that carry forward with their original number until closed.
• Date opened and date needed for every open item.
• Responsible party by company and person.
• Decisions stated as decisions, in plain language.
• Notices recorded where the contractor identified potential delays or cost impacts, while remembering that meeting minutes may not replace formal written notices required by the contract.
• A correction window: a statement that the minutes will be considered accurate unless corrections are received within a set number of days.

See notice requirements in construction contracts.

A worked example: what a better OAC saves

An illustrative $6 million project with 12 months of duration and general conditions of about $55,000 per month:

• Before the change, the OAC ran 100 minutes weekly with 11 attendees, and the average open owner decision stayed open 3.5 weeks.
• After adopting pre-reads, a decision-first agenda and assignments with dates, the meeting runs 60 minutes and the average owner decision closes in 1.5 weeks.
• Meeting time saved: 40 minutes × 11 people × 50 meetings — over 360 person-hours in the year.
• If faster decisions avoid even three weeks of cumulative delay on the project, that protects roughly $40,000 in time-related general conditions.

The numbers are illustrative, but the pattern is consistent: late decisions are among the most expensive things in construction, and the OAC is where they are either made or deferred.

Subcontractor meetings are separate

Do not turn the OAC into a subcontractor coordination meeting. Hold a separate weekly subcontractor meeting run by the superintendent for trade coordination, look-ahead planning and site logistics, and bring to the OAC only the issues that need owner or design input. Keeping the two meetings distinct respects the owner's time and gives trades a forum where they can speak openly. See look-ahead scheduling and constraints.

Virtual and hybrid OACs

• Share the screen with the logs, not a slide deck.
• Use a site walk video or photos for field issues.
• Keep cameras on for decision items when possible.
• Record decisions in the minutes, not only in chat messages.
• Hold an in-person site OAC at key milestones: before major concealment, before finishes and before substantial completion.

When the meeting turns difficult

Tension in OAC meetings usually comes from cost overruns, delays or quality disputes. Keep the discussion on facts and options, avoid assigning blame in front of the group, and move detailed disputes to a smaller meeting with the right people. Record that the issue was raised and where it will be resolved. Contractors who stay calm and organized when things go wrong earn the owner's trust for the next project. See dealing with a difficult owner.

OACs near closeout

As the project approaches completion, shift the agenda: punch list status by area, inspections and certificate of occupancy steps, commissioning, training sessions, closeout documents, owner move-in dates and final change order reconciliation. This is when many projects lose weeks, and a focused closeout OAC keeps momentum. See punch list and closeout.

Setting the rules at the first OAC

The first meeting after notice to proceed sets habits for the whole project. Use it to agree on the ground rules, in writing:

• Meeting day, time, length and location or video link.
• Who prepares the agenda and minutes, and when each is distributed.
• Required attendees for each party and who has decision authority.
• Target response times for RFIs, submittals and owner decisions, consistent with the contract.
• How pending changes are priced, reviewed and authorized.
• How corrections to the minutes are submitted.

Agreeing on these rules early turns later reminders into references to what everyone accepted, instead of complaints. See preconstruction meeting and client onboarding.

The owner decision log

A single, simple log does more to keep projects on schedule than most scheduling software features. Columns:

• Decision number and description.
• Date raised and date needed, tied to a schedule activity or procurement lead time.
• Options with cost and schedule effect.
• Responsible decision-maker.
• Status: open, decided, overdue.
• Decision made, date and reference to the minutes or directive.

Review overdue decisions first at every OAC. When a decision is late, record the potential impact at that moment, not months later.

What owners want from the OAC

Owners and their representatives rarely want more detail; they want confidence. They want to know whether the project is on schedule and on budget, what could change that, what they need to decide and by when, and whether the contractor is in control of the site. A contractor who answers those four questions in the first ten minutes, with honest data, earns trust — and trust makes difficult conversations about changes and delays far easier when they come.

OAC mistakes

• Reading logs aloud instead of sending pre-reads.
• Open items without owners and dates.
• Vague decision requests without options, cost, schedule and deadlines.
• Minutes sent late or written by someone who was not tracking decisions.
• Relying on minutes instead of required formal notices.
• Treating verbal direction as a change order.
• Mixing trade coordination into the OAC.

Where to start

Running a better OAC does not require new software or a bigger team. It requires preparation before the meeting, discipline during it and follow-through in the day after, repeated every single week until it becomes the way the project works. At your next OAC, offer to prepare the agenda and minutes. Send a pre-read 24 hours before with the look-ahead, RFI, submittal and change logs, and a one-page list of owner decisions with needed dates. Run the decision-first agenda, close each item with an owner and date and publish minutes the next day. After a month, compare how long decisions stayed open before and after the change.

Frequently asked questions

What is an OAC meeting in construction?

An OAC meeting is a recurring meeting between the owner or owner's representative, the architect or design team and the general contractor to review project progress and make decisions. On most commercial projects it happens weekly or every two weeks. Typical topics include the schedule and critical path, owner decisions and selections, overdue or critical RFIs and submittals, pending changes and costs, quality, inspections and permits, and closeout. Depending on the contract and the project, the meeting may be chaired by the architect, the owner's representative or the contractor, and one party prepares the agenda and publishes minutes that become part of the project record.

What should be on an OAC meeting agenda?

A productive agenda starts with safety and site issues, then the schedule with milestone status and critical path risks, followed by the decisions required from the owner and design team with the dates they are needed. After that come only the RFIs and submittals that are overdue or on the critical path, pending changes that need direction along with budget and contingency status, quality, inspections and permits, and a final review of every action item with its responsible party and due date. Routine status information, such as full logs and progress photos, should be sent as a pre-read one or two days before the meeting.

Can OAC meeting minutes serve as formal notice of a delay or change?

Sometimes they help, but contractors should not rely on them alone. Minutes that record when a potential delay or cost impact was raised are valuable documentation, especially if they are distributed promptly and include a correction window. However, many construction contracts specify how formal notices of delays, claims and changes must be given, including the form, the recipient and the deadline, and minutes may not satisfy those requirements. The safer practice is to record the issue in the minutes and also send the formal written notice required by the contract, keeping both in the project file.