Free OAC (Owner-Architect-Contractor) Meeting Agenda Template

Nine-section agenda structure mid-market GCs use to run OAC meetings that end with decisions. Pre-filled, distributed 48 hours before, closes with a signed action log.

ExcelWordPDF

Fill in an OAC meeting agenda online

Free, no sign-up. What you type stays in your browser.

Example: a weekly OAC meeting with three open RFIs. Clear the example to start your own agenda.

Meeting
Send it out 48 hours before the meeting
Administrative opening and schedule review
Name, firm and role
RFIs, submittals and change orders on the agenda (fields 3, 4 and 5)
Section
No.
Subject
Responsible
Due
Status or action
Remove
Safety, decisions and action log
Incidents, inspections and open items
State the consequence of no decision
RFI responses, submittal reviews, design clarifications
One action per line: what was decided, who owns it, the due date. Every attendee initials the log before leaving.

Want the working Excel agenda or the editable Word version? Get the blank Word, Excel or PDF.

The nine-section agenda structure mid-market general contractors use to run OAC meetings that end with decisions, not follow-up meetings about the last meeting.

Why this template exists

Every construction project has OAC meetings. Most of them are a waste of an hour for everyone in the room. The owner wants schedule updates and cost certainty. The architect wants RFI responses and submittal approvals. The contractor wants change order decisions and access to information that’s holding up field work. Nobody leaves satisfied because nobody came in with a structure that forces those specific things to get resolved.

The default OAC agenda, if there is one, is a typed list of topics sent the morning of the meeting. Half the items carry over from the last meeting. The other half spawn two new items apiece. The meeting runs long, decisions are deferred, and the PM writes another email summary that nobody reads.

The Contracts Connected team built this template because good OAC meetings don’t happen by accident. They happen when the agenda is structured to force decision-making, not just status-reporting. The difference is in the architecture: items are pre-sorted into decisions needed today vs. status only, owners are pre-assigned to each item, and the meeting closes with a written action log that everyone signs before leaving. That last part is the one most PMs skip, and it’s the one that makes the next meeting shorter.

This template covers nine sections organized around the workflow of a standard OAC meeting: administrative opening, schedule review, RFI and submittal status, change order decisions, safety and quality, owner decisions required, architect decisions required, open items and lookahead, and meeting close with action log. The sections are sequenced to front-load the items most likely to cause field delays, RFIs, submittals, change orders, and owner decisions, so they get addressed before the meeting runs out of time.

The nine sections work on commercial and public projects. Federal projects with additional reporting requirements (certified payroll, safety plans, EEO compliance) can add a federal compliance standing item between sections 4 and 5 without disrupting the overall structure.

Who uses this template

  • Mid-market general contractors running weekly or biweekly OAC meetings across commercial and public projects
  • Prime contractors on federal projects who chair the OAC meeting and own the action log
  • Project managers responsible for driving decisions and documenting outcomes at OAC meetings
  • Owners’ representatives who want a consistent meeting structure across their GC roster
  • Construction executives standardizing meeting management across multiple active projects

What’s included: 9 agenda sections

The agenda template contains nine sections organized to drive decisions, not just updates:

  1. Administrative opening. Attendance, quorum, prior minutes. Captures attendees by name, firm, and role at the top of the meeting, confirms quorum (whoever needs to be in the room to make decisions is actually in the room), and formally approves or corrects the prior meeting minutes. Approving prior minutes at the start, not circulating them afterward via email, closes the loop on what was decided and agreed at the last meeting. If someone disputes a prior minute, resolve it now, not in a separate email chain.
  2. Schedule review. Current baseline, float, and critical path. A structured update on current schedule status against the baseline: whether the project is on schedule, ahead, or behind, what activities are on the critical path, and where float has been consumed. The section has a pre-formatted table for the top five schedule risks and their mitigation status. Schedule review goes second, before RFIs and change orders, because schedule impact is the context that makes everything else on the agenda urgent or manageable.
  3. RFI status. Open, pending, and overdue items. A running table of all open RFIs, organized by RFI number, subject, date submitted, responsible party for response, due date, and current status. RFIs that have passed their due date are pre-flagged in red on the Excel version. The section distinguishes between RFIs pending architect response, RFIs pending owner decision, and RFIs pending contractor clarification. Because the resolution path differs. Overdue architect RFIs that are holding up field work are escalated to the owner decisions section if not resolved by the RFI discussion.
  4. Submittal log review. Approvals needed and returned items. Parallel structure to the RFI section: a table of all submittals currently in the review cycle, organized by submittal number, spec section, contractor submission date, expected return date, and current status. Submittals returned with comments requiring resubmission are tracked here with the comment-resolution owner assigned. Submittals that have been in review longer than the contract-specified review period are flagged for escalation to the architect or owner as needed.
  5. Change order decisions. Pending PCOs and formal COs. The section where Potential Change Order items move to decisions. Each PCO or CO on the agenda is presented with a one-line description, the cost impact, the schedule impact, and a required action: Approve, Reject, or Defer with a specific decision date. Deferrals that don’t come with a specific date are not allowed: ‘we’ll discuss next meeting’ is what generates the carry-over backlog that makes OAC meetings useless. This section is where the agenda structure pays for itself in projects that have contested change orders.
  6. Safety and quality update. Incidents, inspections, and open items. A standing safety section covering: any recordable incidents or near-misses since the last OAC, current safety inspection status, any outstanding OSHA citations or corrective actions, quality deficiency notices issued or resolved, and the next planned safety inspection date. Safety goes here, in the middle of the agenda, not at the end, where it gets rushed or dropped. On federal projects, add a certified payroll compliance status line here.
  7. Owner decisions required. Items with a hard deadline today. This section is the most important one most OAC agendas omit. It pre-lists every item that requires a decision from the owner today, not this week, not next meeting, and states the consequence of non-decision for each item. ‘If the owner doesn’t approve the structural steel substitution by end of meeting, the steel order misses the lead time window and the project goes 3 weeks back on the critical path.’ That framing changes the meeting dynamic. Owners who understand the cost of non-decision make decisions faster.
  8. Architect decisions required. RFI responses, submittal reviews, design clarifications. Parallel to the owner decisions section: items requiring the architect’s decision or action today, with consequence framing. ‘This RFI has been open 14 days against a 7-day contract response window. Field work on Level 3 is paused pending the answer.’ The architect’s decision section is not a complaint log. It’s a structured forcing function. Put it on the agenda, assign an owner, state the deadline, close the loop before the meeting ends.
  9. Open items, 3-week lookahead, and action log close. The final section covers: the 3-week lookahead for upcoming submittals, RFIs, deliveries, and inspections that will need OAC attention in the next three meetings; any open items not resolved during the meeting with assigned owners and due dates; and the meeting close action log. The action log captures every decision made and every action assigned during the meeting, what was decided, who owns it, and the due date, and is circulated within 24 hours. Every attendee initials the log before leaving the meeting room. No initialing, no leaving.

How to run an OAC meeting with this agenda

Distribute the pre-filled agenda 48 hours before the meeting, not the morning of. Each section should be pre-populated by the PM with current data pulled from the project management system before distribution. Attendees review their sections in advance so they arrive with decisions ready, not questions.

Run the meeting in section order. Set a time budget per section at the start (e.g., “We have 60 minutes; schedule gets 10, RFI/submittals get 15, change orders get 15, decisions get 15, close gets 5”). When a section runs over, items carry to the end, not to the next meeting.

Close the action log before ending the meeting. Every attendee initials the log before leaving the room. Circulate the signed log within 24 hours.

Stop running meetings that generate more meetings

An OAC meeting with no action log produces a follow-up email that produces a follow-up meeting. Contracts Connected’s Approval Workflows module keeps submittals, RFIs, and change orders moving between meetings, so the items that arrive at your OAC are ready for decisions, not still waiting for someone to open a PDF and respond.

For educational purposes. These templates, checklists, and trackers are operator-built starting points designed to help you move faster on the kind of work that usually drowns construction admins in email chains. They are not legal, insurance, accounting, or tax advice. Each project, jurisdiction, and contract has its own quirks. Review the document, refine the language, and consult your attorney, broker, CPA, or compliance officer before relying on it for a live project decision.

Frequently asked questions about OAC meetings

How often should OAC meetings be held on a typical construction project?

Weekly during active construction phases, biweekly during preconstruction and closeout. Weekly cadence during construction keeps RFI and submittal cycles tight enough to prevent field delays. A biweekly OAC on a fast-track project typically means 10-day-old RFIs hitting the agenda, which is already a problem. Some large programs run two OAC tracks: a weekly operational OAC for RFIs, submittals, and field issues, and a monthly executive OAC for budget, schedule trend, and owner decisions requiring senior authority.

Who should attend an OAC meeting?

The minimum: the owner’s representative with decision authority, the architect or architect’s project manager, and the GC’s project manager. For complex decisions, add the relevant subcontractors, the structural or MEP engineers of record, and the owner’s financing or legal contacts as needed. The guiding principle: only attendees who either make decisions or have information required for decisions should be in the room. Status-only attendees get the action log, not a seat at the table.

What’s the difference between an OAC meeting and a progress meeting?

OAC meetings involve the owner, architect, and contractor and are focused on decisions. Change orders, design clarifications, owner approvals, schedule-impacting issues. Progress meetings (or subcontractor coordination meetings) typically don’t include the owner and focus on field coordination, trade sequencing, and short-interval scheduling. Both have distinct agendas and distinct outputs. Mixing them produces a meeting that’s too long, too detailed for the owner, and not detailed enough for the field.

How should change orders be presented at an OAC meeting?

Each change order or potential change order item should have a one-line description, a cost impact (with backup available), a schedule impact, and a clear action required: Approve, Reject, or Defer with a decision date. Don’t present a change order as ‘we’re still working on pricing’. That’s not an agenda item, it’s a status update. PCOs should come to the OAC when they are ready for decision, not when they are still being developed. Presenting undecided items wastes meeting time and trains the owner to expect that the GC isn’t prepared.

What goes in the action log versus the meeting minutes?

The action log captures decisions and actions: what was decided, who owns the follow-up, and the due date. The meeting minutes capture the discussion that led to the decision. The context, the options considered, the dissenting views. Both serve a purpose, but the action log is what drives work in the next 7 to 14 days. Some PMs maintain only the action log and skip formal minutes. That’s a risk on public projects where the minutes serve as an official project record. On private commercial projects, the action log alone often suffices.

Can this template be adapted for Design-Build or CM-at-Risk delivery methods?

Yes, with adjustments. In Design-Build, the architect section collapses into the contractor’s scope because the designer is on the contractor’s team. Owner decisions required becomes the primary external decision section. In CM-at-Risk, the OAC structure is similar to traditional delivery but the GC’s role in managing the architect relationship is more active during preconstruction. Add a preconstruction deliverables section during design phases. The nine-section structure adapts to both delivery methods without losing its core logic.

Where this document lives in the system
Back-Office System · Contracts Connected
Product bridge

Contracts Connected tracks every document a vendor owes you against the contract, reads what comes back, and shows who can mobilize, who is compliant on site, and who can be paid. Construction compliance.

More in Project management

All Project management templates