The OAC meeting: who attends, what to cover, and a minutes template you can copy

By Adam Chandler, founder of Pangea · August 13, 2026

An OAC meeting is a recurring construction project meeting between the owner, architect, and contractor — the three parties who together control a project's budget, design, and schedule. Typically held weekly or biweekly during construction, it's where the team reviews progress, clears RFIs and submittals, decides on changes, and records those decisions in minutes that become part of the project record. OAC stands for owner-architect-contractor; the same meeting goes by "owner's meeting," "progress meeting," or "the OAC call" depending on the firm.

This guide covers who should be in the room, how often to meet, what belongs on the agenda, and a complete owner-architect-contractor meeting minutes template you can copy — no download form, it's all below.

Who attends an OAC meeting?

The core attendees are decision-makers from the three named parties: the owner (or owner's representative), the architect or lead design consultant, and the general contractor's project manager — plus whoever is needed for that week's agenda items. In practice the room usually looks like this:

• Owner or owner's representative — the person with authority to approve changes, spend contingency, and make design decisions. Without decision authority in the room, the meeting produces questions instead of answers.
• Architect / design team — the architect of record, joined by consultants (structural, MEP, civil) when their scope is on the agenda. They answer design questions, report on submittal reviews, and carry RFI responses.
• General contractor — typically the project manager and superintendent, often with a project engineer supporting the log updates.
• As needed — a construction manager or owner's rep firm, major subcontractors for their scope, a commissioning agent near closeout, or a lender's representative on financed work.

Keep the standing group small: the people who can make decisions, plus specialists for their item only — everyone else reads the minutes.

How often should OAC meetings be held?

Weekly or biweekly during active construction is the norm; monthly is common during early design and closeout. The cadence follows how fast decisions are needed: during foundation and structure, a two-week-old answer can idle a crew, so most teams meet weekly. During design development, biweekly usually keeps pace. What matters more than the exact interval is consistency — a standing 30 to 60 minute slot each week beats long ad-hoc meetings scheduled whenever things feel urgent, because the standing meeting catches problems while they're small.

What's on a typical OAC meeting agenda?

A standing OAC agenda walks the same logs in the same order every meeting, so nothing depends on someone remembering to bring an item up. A typical sequence:

1. Review of previous minutes — corrections, then acceptance.
2. Safety and site update — brief report from the contractor.
3. Schedule — progress against critical path milestones and the two- or three-week look-ahead.
4. Budget and change orders — contingency status, pending change requests, approved changes.
5. RFIs — open items, overdue responses, anything blocking work.
6. Submittals and procurement — items in review, overdue reviews, long-lead materials that need ordering in the next 60–90 days.
7. Design items and owner decisions needed — each with a needed-by date.
8. Old business — the open-item log, walked line by line.
9. New business, then next meeting — date, time, and items parked for it.

For a real-world example, the University of Utah's facilities group publishes its OAC meeting agenda template with a constraint log built in.

How is an OAC meeting different from other construction meetings?

The OAC is the decision meeting — it's where the three contract parties resolve anything that touches budget, design, or schedule. Other recurring meetings coordinate execution:

What should owner-architect-contractor meeting minutes include?

OAC minutes are a record of commitments, not a transcript: who was there, what was decided, who owes what by when, and which items remain open. All three contract parties rely on them, and they're the document people reach for when memories differ months later. We covered how minutes fail at AEC firms, and how to pick tooling for them, in our guide to construction meeting minutes software.

OAC meeting minutes template (copy and adapt)

Here is the full structure. Copy it into your firm's document template and keep the section order identical from meeting to meeting:

1. Header. Project name and number, meeting number, date, time, location or call link, minutes prepared by, and the distribution list.
2. Attendance. Present — name, firm, role. Note absences and anyone attending for a single item.
3. Review of previous minutes. Corrections requested, or a note that the prior minutes stand as issued.
4. Open items carried forward. Item number, description, owner, due date, current status. Nothing leaves this list until the room agrees it's closed.
5. Schedule. Progress against critical path milestones, the look-ahead, and any date that moved — with the downstream impact acknowledged in the meeting.
6. Budget and changes. Contingency status, pending change requests and potential change orders, and changes approved since last meeting, each with cost and schedule impact.
7. RFIs. Open count, overdue responses, and the specific RFIs blocking work — with who owes the answer and by when.
8. Submittals and procurement. Submittals in review, anything overdue, and long-lead items with order-by dates.
9. Decisions made this meeting. What was decided, who decided it, and any conditions attached. Write these as full sentences — "Owner approved Alternate 2 (metal panel) contingent on confirming lead time under 10 weeks" survives a year better than "panel approved."
10. Owner decisions needed. Each pending decision, the date it's needed by, and what slips if that date is missed.
11. New action items. Number, action, one named owner, due date.
12. Next meeting. Date, time, location, and items already parked for its agenda.

Two conventions make this template much more useful. First, number items continuously across the project — item 12.03 is the third item raised in meeting 12 — so an item keeps its identity as it rolls forward week after week. Second, end every issue of the minutes with a correction window: a line stating that the minutes will stand as the record unless written corrections are received within a set number of days. It turns silence into acceptance, which is exactly what you want from a document three parties depend on.

What are the best practices for running an OAC meeting?

Teams whose OAC meetings actually move the project do the same few things:

• Send the agenda a day or two ahead, with updated logs attached, so people arrive with answers instead of promises to check.
• Keep the structure identical every week. The agenda is a checklist; the value is that nothing depends on memory.
• Give every action item one owner and one date. "Design team to review" is how items die. "Maria to return the storefront submittal by Friday the 21st" is how they close.
• Timebox, and take deep-dives offline. When a design question needs 45 minutes, schedule a working session with the right three people rather than holding twelve people hostage.
• Issue minutes within 48 hours. Details go soft fast, and a correction window only works if people can still remember the meeting.
• Record the meeting — and announce it. A recording means the minutes get written from what was said, not from what a notetaker caught while also running the meeting.
• File minutes by project, not by date. The FMI and PlanGrid Construction Disconnected study found construction professionals spend about 5.5 hours a week just looking for project data. A folder of files named "Minutes 3-14" is how that happens; a project record you can search is how it stops.

Where Pangea fits

OAC meetings are the exact meeting type Pangea was built around. It's an AI notetaker and project coordinator for architecture, engineering, and land-development firms: it records the meeting with no bot joining the call — which matters when the owner is on the line — and covers in-person meetings like site walks and conference-room sessions, not just video calls. (Prefer a visible guest? You can send a bot to Zoom, Meet, or Teams instead.) It writes minutes in your firm's own format, files them — along with every decision and action item — to the correct project automatically, and shares them as view-only links, so the owner sees a clean record rather than an editable draft. With your approval it pushes tasks and schedule updates into the PM software your firm already runs, and months later you can ask the project what was decided about the storefront alternate and get the answer with its source cited. There's a 14-day free trial, no credit card required.

Frequently asked questions