On this page
- Step 1: Set the ground rules at the start of the job
- Step 2: Send the agenda and the logs ahead
- Step 3: Use the same agenda every week
- Step 4: Start with what was left open
- Step 5: Write decisions, not conversation
- Step 6: Give every open item one owner and a date
- Step 7: Distribute within a day and carry items forward
- Worked example: three items from meeting 14
- Common mistakes
- How os.construction handles it
- FAQ
To run an OAC meeting, hold it at the same time every week, send an agenda with the open-items list and current logs a day ahead, work through the same sections in the same order, record each topic as a numbered decision with one owner and a due date, send the minutes within a day, and carry every open item to the top of the next agenda. Most of the value comes from the follow-up after the meeting.
An OAC (owner-architect-contractor) meeting is where most project decisions either get made or get deferred another week. A loose one turns into a status recital. A tight one moves RFIs, submittals and changes, and leaves a written record of who agreed to what and when. The free meeting minutes template follows the same structure as this post.
Step 1: Set the ground rules at the start of the job
At the preconstruction meeting, agree:
- Cadence and slot. Weekly is common during active construction; every two weeks can work on slower phases. Pick a day and time and keep it.
- Who attends. The owner’s representative, the architect (and consultants when their items are up), and the GC’s project manager and superintendent. Invite subs by topic.
- Who chairs and who writes the minutes. Usually the GC’s PM chairs and a project engineer takes the minutes. Check whether the contract or owner procedures assign this.
- How corrections work. Minutes stand as written unless corrections arrive by a stated date.
Step 2: Send the agenda and the logs ahead
Send the agenda a day before, with the documents it refers to: the open-items list from the last minutes, the RFI log, the submittal register, the change log and the current three-week look-ahead. People who have read the logs come ready to decide instead of hearing the status for the first time.
Step 3: Use the same agenda every week
A fixed order means people know when their item comes up and nothing gets skipped. A sample agenda for a one-hour meeting:
| # | Section | Time | What happens |
|---|---|---|---|
| 1 | Safety | 5 min | Incidents, near misses, upcoming high-risk work |
| 2 | Last minutes | 5 min | Corrections, then accept |
| 3 | Open items carried forward | 10 min | Each one: done, new date, or escalate |
| 4 | Schedule and look-ahead | 10 min | Progress, slips, next three weeks, critical items |
| 5 | RFIs | 8 min | Overdue first, by ball in court |
| 6 | Submittals | 7 min | Late to submit, overdue in review, long-lead items |
| 7 | Changes | 8 min | Pending change events and change orders awaiting decision |
| 8 | Quality, inspections, punch | 4 min | Failed inspections, upcoming inspections |
| 9 | Owner items and decisions | 3 min | Selections, approvals, access, permits |
| 10 | Next meeting | — | Date, time, anything to prepare |
The times are a starting point. If one section keeps overrunning, that topic probably needs its own working session.
Step 4: Start with what was left open
Before any new business, go through last week’s open items. Each one gets one of three outcomes: closed, a new date with a reason, or escalated. This is the part of the meeting that keeps commitments honest. An item that has slipped three weeks running is a decision nobody wants to make, and the minutes should say so plainly.
Step 5: Write decisions, not conversation
Minutes are not a transcript. For each topic, write one or two lines: what was decided, who does what, by when. Number each topic by meeting and item (14.3 is meeting 14, topic 3) and keep that number when the item carries forward, so its history is easy to follow. Reference the record the topic is about, such as RFI-212 or the submittal number, instead of retelling it.
Be careful with disputed points. If the owner and contractor disagree about whether something is a change, record that each party stated its position, not that anything was agreed. Minutes are often the first place people look later to see what was said, so they should be accurate and neutral.
Step 6: Give every open item one owner and a date
“Team” and “TBD” are not owners. If two people each have a part, split it into two items. A date without an owner doesn’t happen, and an owner without a date gets done eventually, which on a construction schedule usually means late. Actions that aren’t RFIs, submittals or changes can go on an action item tracker so they don’t live only in the minutes.
Step 7: Distribute within a day and carry items forward
Send the minutes the same day or the next, to attendees and the distribution list, with the date for corrections. Then copy every open item to the top of next week’s agenda, with its original number. Then do it again next week.
Worked example: three items from meeting 14
Here is part of the minutes from meeting 14, as they’d be written:
| Item | Topic | Decision / discussion | Owner | Due | Record | Status |
|---|---|---|---|---|---|---|
| 12.2 | Door hardware resubmittal | Resubmitted 3 days ago; architect reviewing. Hardware supplier needs approval within 2 weeks to hold the delivery date. | Architect | Next meeting | Submittal 08 71 00-2 | Open |
| 13.4 | Corridor 3B duct clearance | Engineer accepted Option A (34×10 duct). GC to price the duct change and submit. | GC PM | 1 week | RFI-147 | Open |
| 14.1 | Lobby tile selection | Owner to select from the two samples on site. Tile is needed on site in 7 weeks with a 4-week lead time. | Owner’s rep | 1 week | Submittal 09 30 13-1 | Open |
Three things to notice. Item 12.2 kept its number from meeting 12, so anyone can trace it. Item 13.4 closed the RFI question but opened a pricing action, which now has its own owner. Item 14.1 says why the date matters: with a 4-week lead time and a need date 7 weeks out, the order has to go in within three weeks, and a selection within one week leaves two weeks for the submittal to be prepared and approved. Writing the reason into the minutes makes the deadline harder to ignore.
Common mistakes
- No agenda, or a different one every week. Items get skipped and nobody prepares.
- Minutes that read like a transcript. Nobody can find the decision.
- Items with no owner or no date. They don’t move.
- Renumbering carried items. Their history disappears.
- Minutes sent a week later. By then memories differ and corrections pile up.
- Recording a disputed position as agreed. That causes problems later; record what each party said.
- Letting the meeting replace the logs. The meeting reviews the RFI, submittal and change logs; it doesn’t replace keeping them current.
How os.construction handles it
The Meetings tool holds each meeting from agenda to minutes: recurring weekly, biweekly or monthly series, attendance marked Present, Absent, Conference or For Distribution Only, numbered topics with an assignee and due date, and links to the RFI, submittal, punch item or observation a topic is about. Create Follow-up Meeting carries open topics into the next meeting, and Create task turns a topic into a tracked task. The app doesn’t email minutes; Record Distribution keeps a record of who received them. The weekly OAC meeting walkthrough shows it step by step, and construction meeting minutes software covers what to look for in any meeting minutes tool.
FAQ
What does OAC stand for in construction?
Owner, architect, contractor. The OAC meeting is the regular meeting, usually weekly or every two weeks during construction, where those three parties review progress, the schedule, open RFIs and submittals, changes and decisions the owner needs to make.
Who runs the OAC meeting?
Usually the general contractor's project manager chairs it and publishes the minutes, but some owners or architects run it themselves, and some contracts say who is responsible. Agree it at the preconstruction meeting and write it into the project procedures.
What should be on an OAC meeting agenda?
The same order every week: safety, corrections to the last minutes, open items carried forward, schedule and look-ahead, RFIs, submittals, changes, quality and inspections, owner items and decisions, and the next meeting date. Send the logs that back each section with the agenda.
How soon should OAC meeting minutes go out?
As soon as practical, ideally within a day, while people still remember the discussion. State a date by which corrections must be received, and record any corrections at the start of the next meeting.
Are subcontractors invited to the OAC meeting?
Sometimes, for specific topics. Most teams keep the OAC meeting to the owner, design team and GC, and hold a separate subcontractor coordination meeting. Invite a sub's PM when an item on the agenda needs them.
Share this article