Architecture & Design · Fundamentals
Produce OAC meeting minutes with an open-items log
Every other Tuesday, the owner, the architect and the contractor sit around a site trailer table for an hour. Twenty items get discussed. Three of them change something. One of them sounds like an approval but isn't. The minutes become part of the project record, and on a project that goes wrong, they're among the first documents anyone reads. This guide drafts them quickly and keeps the open-items log honest, while the words that carry contractual weight stay with you.
What AI is for here, and what it isn't
OAC (owner–architect–contractor) meeting minutes do two jobs. They tell everyone what happened, and they keep a running list of open items, each with a responsible party and a date. On most projects the second job is the important one. Items that fall off the log come back months later as delays, claims and disputes.
AI is good at the mechanical parts: turning rough notes into your office format, matching today's discussion to the open items carried from last time, and noticing new items that nobody took responsibility for. It does this consistently across a long project, and it doesn't get tired at item 47.
It doesn't know what carries contractual weight, and on a construction project almost everything can. Minutes that say the owner "approved" a substitution, or that the architect "directed" a change, can be read later as exactly that. The contract defines how changes happen. Under the AIA's general conditions, for example, that's through change orders, construction change directives and architect's supplemental instructions, each with its own form and signatures, not through meeting minutes. So the AI drafts, and you choose every word about approvals, changes, cost and time, and decide who receives the minutes.
Collect the inputs
You need four things:
- Today's notes or transcript, as they are.
- The previous minutes and the open-items log, so items carry forward with their numbers intact.
- Your office minutes format: headings, numbering convention (many firms number items by meeting and sequence, like 7.03), and the standard disclaimer paragraph your firm uses, typically asking attendees to report corrections within a set number of days.
- The attendee list, with company and role.
Draft the minutes and update the log
Draft OAC meeting minutes in the format below, from today's notes, and
update the open-items log.
FORMAT: [paste your office template, including numbering convention]
PREVIOUS OPEN ITEMS: [paste log: number, item, responsible party, due]
ATTENDEES: [name, company, role]
TODAY'S NOTES: [paste]
FOR EACH PREVIOUS OPEN ITEM: was it discussed? New status (open,
closed, superseded), what was said, and any new due date. Keep its
number. If it wasn't discussed, carry it forward unchanged and mark
NOT DISCUSSED.
FOR NEW ITEMS: a new number, a factual description, the responsible
party, and the due date if one was stated.
FLAG SEPARATELY:
- NO OWNER: items with no responsible party named.
- CONTRACTUAL LANGUAGE: any place where the notes suggest an approval,
acceptance, direction, change, cost or time impact. Quote the notes.
Do not write these as decisions; describe what was said and by whom.
RULES: Use "discussed", "reported", "stated", "requested". Never write
"approved", "accepted", "directed" or "agreed" yourself.
The verbs rule is the important one. "The contractor requested approval of an alternate storefront system" is a record. "The owner approved the alternate storefront" may be read as an approval.
Resolve the flags
Go through the two flag lists yourself.
No owner: every item needs a responsible party. Assign it yourself if your role allows, or list it as "responsible party to be confirmed" and raise it at the start of the next meeting. An item without a name doesn't get done.
Contractual language: for each one, decide how the minutes should describe it, and whether something else needs to happen outside the minutes: a proposal request, an architect's supplemental instruction, a change order or construction change directive, a formal response to a submittal or substitution request. The minutes can note that the process was started ("Architect to issue proposal request"). They shouldn't be the process.
Check and distribute
Compare the open-items log against the previous one. Every item should be either still there or marked closed, with a reason. Items don't just disappear. Check names, dates, item numbers and spec section references.
Then decide distribution: who receives the minutes, and in what order. Distribute within the time your contract or office standard requires, with the usual note inviting corrections by a set date.
Worked example: meeting 7
Fictional example. At OAC meeting 7 for a small office fit-out, the architect's project manager has 40 lines of rough notes and an open-items log of 18 items from meeting 6.
The draft comes back in the firm's format. All 18 previous items are accounted for: 5 closed, 11 updated, 2 marked NOT DISCUSSED and carried forward. Six new items are added. The flags:
- NO OWNER (2 items): "Confirm whether the existing ceiling grid can be reused" and "Coordinate after-hours elevator access for deliveries". Nobody took them in the meeting. The project manager assigns the first to the contractor (it's means and methods) and lists the second for the owner's facilities contact to confirm, with a note to raise it first next time.
- CONTRACTUAL LANGUAGE (1 item): the notes say "Owner OK with alt storefront if no cost." The draft records it as: "Contractor requested consideration of an alternate storefront system. Owner stated it would consider the alternate if there is no cost impact." The project manager checks the specification: substitutions follow the procedure in Section 01 25 00, Substitution Procedures. The minutes add: "Contractor to submit a substitution request per Section 01 25 00. Architect to review."
That last line is worth more than the rest of the minutes combined. Three months later, the contractor installs the alternate before it's reviewed. The minutes show that no approval was given, and that the agreed path was a formal substitution request.
The minutes and log format
[Project] — OAC Meeting [n], [date], [location]
Prepared by: [name, firm] Next meeting: [date]
Attendees: [name, company, role]
Distribution: [list]
These minutes record the discussion. Report corrections to [name] by
[date]; otherwise they will be taken as accurate. Changes to the
contract are made only through the procedures in the contract
documents.
OLD BUSINESS
[n.nn] [item] — Responsible: [ ] — Status: open/closed — [what was said]
NEW BUSINESS
[n.nn] [item] — Responsible: [ ] — Due: [ ]
ITEMS STARTED THROUGH CONTRACT PROCEDURES
[e.g., Substitution request per Section 01 25 00 — contractor to submit]
AI assistance: draft prepared with [tool]; contractual wording and
distribution by [name]
What stays with you: the wording on anything contractual, and distribution.