Construction site meeting minutes are worth exactly what their action list produces. Everything else in them is context: who said what, the back-and-forth about the window delivery, the superintendent's view of the drywall crew. The part that moves a job is a short list. Every item on it has one owner, one date and a status, and that list is the first thing reviewed at the next meeting. Minutes that record discussion without owners are the reason the same issue comes up three weeks running.
Why the same issue comes back every week
Most site meeting notes read like a summary of a conversation. 'Discussed fire caulking at penetrations. Electrical to look into it. GC to follow up with inspector.' Everyone in the room agrees it was covered, and nobody leaves with a task. The following Tuesday someone asks about fire caulking. Last week's notes say it was discussed, which is true and useless.
That entry fails in three ways. 'Electrical' is a company, not a person. 'Look into it' has no finish line. There is no date, so there is nothing to be late against. When nothing can be late, nothing is. The item survives because the minutes gave it no way to close.
Better note-taking will not fix this. The meeting needs a different document. The meeting produces actions, and the minutes are the record of those actions and of the decisions that created them.
One owner, one date, one finish line
Every action item needs the same fields. Keep them as columns, not prose, so the list can be sorted and carried forward from week to week without retyping.
- Item number — sequential for the life of the job and never reused. Item 47 is still item 47 in week 3 and in week 9.
- Action — a verb and a finished state. 'Submit revised door hardware schedule to architect,' not 'door hardware.'
- Owner — one named person. If two companies are involved, one person owns the item and the other is noted as support.
- Due date — a calendar date. Not 'ASAP,' 'next week' or 'before drywall.' If the item ties to a schedule activity, write the date that activity needs it by.
- Status — open, closed or slipped, with a count of how many times the date has moved.
- Opened — the date of the meeting where the item first appeared.
People resist the owner rule most. A sub's foreman will say 'we'll handle it' on behalf of the company. Write down the foreman's name. If the person in the room can't commit their office to a date, they still own an action: get a date from the office by Thursday. That is a real action with a real owner.
The date rule comes second. 'ASAP' is a mood, not a date. An item without a date can never be overdue, so it can never be escalated. The person running the meeting should not move on from an item until it has a date. The date can be a guess that gets moved next week. A moved date tells you something and a missing date tells you nothing.
Take the line 'Owner agreed to upgrade to the 24x48 tile.' It records a change in scope with no price, no signature and no schedule effect. Months later that line may be the only evidence, and it does not say who pays. Any decision that moves cost or time gets one action item, such as 'Issue change order for tile upgrade, priced and signed.' The person who writes change orders owns it, and it is due before the work starts. The minutes point to the change order and never stand in for it.
Review the open list before anything else
Agenda order decides whether the list gets used. Open items reviewed at the end get reviewed while people are standing up to leave, and they get skipped. Put them first.
- Open items from the last meeting, in number order. Each one is closed, re-dated or escalated. Discuss it only if it is blocking other work.
- Safety and site conditions.
- The two- or three-week lookahead against the schedule: what starts and what is at risk.
- New issues. Each one ends with an owner and a date before the next one is raised.
- A read-back of every new action item, with its owner and date, out loud before people leave.
The read-back takes a few minutes. It catches disagreements that would otherwise surface by email two days later. Say the plumber hears 'Item 52, plumber, rough-in at unit 4 complete by the 14th' and says nothing. That is now an agreed date, made in front of witnesses.
Track how often each date moves. An item that slips once is normal. An item that slips twice is no longer a scheduling problem. It is an ownership problem: the wrong person owns it, or the owner is blocked by something nobody wrote down. The third time it comes up, reassign it or escalate it to whoever can remove the block. That escalation is an action item too, with its own owner and date.
What the minutes should not try to be
Minutes that try to hold everything end up holding nothing well. The meeting surfaces issues. Once an issue is named, it usually belongs in another record, and good construction site meeting minutes point to those records instead of replacing them.
- Questions for the design team — the RFI log. The minutes item is 'Issue RFI on beam pocket detail,' with an owner and a date. The answer lives in the RFI.
- Scope or price changes — a change order, as described above.
- Delays and site conditions — the daily log, written the day it happens. 'Rain last week slowed framing' in Tuesday's minutes is not the record you need. The daily record of weather and its effect on the work is.
- Revised drawings and submittals — the document set, at the current revision. The minutes should note which revision was discussed and leave the register to the document set.
- Punch and quality issues — the punch list, with photos.
Routing issues this way keeps the minutes short. One page of action items and a few decisions is a document people read. Four pages of narrative is a document people file. If drawings and submittals keep drifting out of date, that is a document control problem, and meeting notes will not fix it.
Keep one kind of narrative: a single dated line for each decision that says who made it. 'Architect confirmed Option B for stair rail, 3/11.' That line settles more arguments than a transcript does.
Get the list to its owners the same day
Minutes sent five days later are already history. Send the action list the same day or the next morning to everyone with an open item, not just the people who attended. A sub who missed the meeting still owns item 61.
Sort the list by owner before you send it, so each person can find their own items without reading anyone else's. For subs, the action list belongs to the same discipline as scopes, insurance and schedules. The day-to-day work of managing subcontractors depends on clear written requests with dates on them.
Ask owners to reply if a date is wrong. Silence after 24 hours counts as acceptance. That is a working rule, not a legal standard, and putting it in the email header makes it stick.
Chase items before the meeting, not at it. A short message two days ahead, such as 'Item 47 due Friday, still on?', means the open-item review confirms what you already know. Without it, the review is where you find out.
Where BuilderSolve fits, and where it doesn't
In the software, meetings and calls sit on the job alongside the schedule, daily logs and change orders. An action item that turns into a change order or a schedule shift is a step away, not a separate file. The AI assistant drafts change orders, daily logs, schedule shifts and time entries for a person to approve or reject. It does not decide who owns an action and it does not agree a date on anyone's behalf.
On the services side, the operations and admin team already handles contracts, RFIs and lookaheads. Keeping the action list, sending it out sorted by owner and chasing items before the next meeting is the same kind of work. Neither the software nor the team runs your meeting or makes a sub show up. The person chairing the meeting still has to refuse 'ASAP' and insist on a name.
Start with the next meeting
- Before the meeting, pull every open item from the last three sets of minutes into one numbered list. Assign an owner at the top of the meeting to anything that doesn't have one.
- Change the agenda so the open list comes first.
- Add the six columns. Don't move on from any new item until it has a person and a calendar date.
- Read the new items back before people leave.
- Send the list, sorted by owner, the same day.
- At the following meeting, count how many items closed. That number tells you whether the meeting is working.
Common questions
what should construction meeting minutes include
Construction meeting minutes should include a numbered action list and a short decisions log. Each action needs a verb and a finished state, one named owner, a calendar due date, a status and the date it was opened. Each decision gets one dated line saying who made it. Keep any discussion summary brief. Anything needing a longer record belongs in an RFI, change order, daily log or the document set.
who should take minutes at a construction site meeting
The person who will chase the action items should take or own the minutes. That is usually the project manager or a project coordinator. The superintendent chairing the meeting should not also be writing, because running the agenda and refusing vague owners is a full job. Whoever writes the minutes sends the list the same day, sorted by owner, and follows up before the next meeting.
how long should weekly construction meeting minutes be
One to two pages is enough for a weekly site meeting on most jobs. Most of that should be the open action list and new items in table form, plus a few dated decision lines. If minutes run to four pages of narrative, the extra content usually belongs in the RFI log, change orders or daily logs, where it can be found and acted on later.
are meeting minutes binding for changes on a construction job
Meeting minutes are generally evidence of what was discussed, and they should not be relied on in place of a contract change. If a decision changes scope, price or time, issue a signed change order. Minutes that are sent out promptly and not disputed can support your account of events. The contract still governs how changes and notices must be made, so check its terms.
same item keeps coming up in site meetings what to do
Reassign it or escalate it. An item that slips once is normal. One that slips twice usually has the wrong owner or a blocker nobody has written down. On its third appearance, ask what is blocking it, give it to whoever can remove that block and set a new date. Record the escalation as its own action item with one owner and one date.