A construction meeting agenda template should include a project header and attendee log, a review of open action items, safety, schedule and delay documentation, RFI and submittal logs, change orders and payment status, quality control, third-party coordination, and close-out tracking, with clear rules for how minutes are recorded and distributed. Build it once, use it every week, and the agenda becomes both a meeting tool and a permanent project record that holds up if claims surface later.
Project Header and Attendee Log
Every agenda opens with a header that ties the document to one specific project and one specific meeting. Include the full project name, site address, the contract document reference (such as AIA A101-2017 if the owner-contractor agreement is AIA-based), and the meeting number in sequence.1AIA Contract Documents. Summary A101-2017 Standard Form of Agreement Between Owner and Contractor Add the date, time, and meeting location or video-conference link.
Below the header, list every attendee with name, company, role, and contact information. Note anyone invited who did not attend, and anyone who joined partway through. When you later need to confirm who agreed to a deadline or who was absent when a design change was discussed, a clean attendee record prevents arguments.
Review of Previous Action Items
Before new business, the agenda should walk through unresolved items from the prior meeting. Each open item carries forward with the responsible party, the original due date, and current status: completed, in progress, or overdue. Items that are genuinely done get marked closed and drop off. Everything else stays until it’s finished.
Precision matters here. “Electrical subcontractor to submit revised panel schedule by March 14” is useful; “team to follow up on electrical” is not. The more specific the original entry, the harder it is to dodge later, and the easier it is to see patterns when the same name keeps appearing next to overdue items.
Safety
Safety belongs near the top of the agenda, not at the end. Federal regulations under 29 CFR 1926 require construction employers to maintain accident prevention programs that include frequent and regular inspections of job sites, materials, and equipment by competent persons.2eCFR. 29 CFR 1926.20 – General Safety and Health Provisions The template should capture whether those inspections happened during the reporting period and what they found.
A workable safety block typically covers:
- Incidents and near-misses since the last meeting, with corrective actions taken.
- Training status by crew, including fall protection, confined space, and hazardous materials. Employers must instruct each worker in recognizing and avoiding unsafe conditions specific to their work environment. Fall protection training specifically requires a written certification record with the worker’s name, training date, and trainer’s signature.3eCFR. 29 CFR 1926.21 – Safety Training and Education4Occupational Safety and Health Administration. Fall Protection in Construction
- Emergency action plan review. The plan must cover escape procedures, employee accountability after evacuation, rescue duties, and alarm systems, and the agenda should flag whether changes in site layout or work phase mean an update is due.5eCFR. 29 CFR 1926.35 – Employee Emergency Action Plans
- Upcoming hazards tied to new work activities such as steel erection or excavation, so protections are in place before the work starts.
This section does two jobs. It keeps workers safer in real time, and it builds a compliance record for insurance audits or OSHA inspections. A blank safety section week after week reads almost as badly as a reported incident, because it suggests nobody was paying attention.
Schedule, Look-Ahead, and Delays
The schedule section is the heart of most progress meetings. It breaks into three pieces: what got done, what’s coming, and what’s blocking the timeline.
Work Completed and Look-Ahead
Summarize work completed since the last meeting, organized by trade or building area. Then lay out the look-ahead: planned activities for the next two to three weeks in enough detail that subcontractors can coordinate labor and material deliveries. A standard three-week look-ahead breaks down day-by-day tasks pulled from the overall project schedule.6Naval Facilities Engineering Systems Command. 3-Week Look Ahead Schedule Problems surface here first. If framing cannot start until the foundation cure period ends and that date keeps sliding, the look-ahead makes the cascade visible before it becomes a claim.
Site Conditions and Delays
Record any conditions affecting the schedule: weather events, unforeseen subsurface conditions, access restrictions, or material delivery problems. If a contractor eventually needs a time extension, meeting minutes that document the delay in real time carry far more weight than a narrative assembled after the fact.
Delays generally fall into three categories that determine who bears the cost and time consequences. Excusable and compensable delays are caused by the owner’s actions or inactions, such as late delivery of owner-furnished equipment or design changes; the contractor is entitled to both a time extension and potential cost recovery. Excusable but not compensable delays are neither party’s fault, with severe weather and labor strikes not caused by the contractor as typical examples; the contractor gets additional time but no extra money. Non-excusable delays, including late subcontractor performance, slow mobilization, or faulty workmanship, fall on the contractor for both time and cost.
Whether a delay affects project completion depends on whether it hits the critical path. A two-week delay to interior paint does not matter if the building envelope will not be sealed for another month. Record that distinction in the minutes so the delay analysis stays clean if a formal claim is filed.
RFIs and Submittals
Requests for Information and submittals are the two document streams that stall projects when they are not tracked aggressively. The template should include a log section for each.
For RFIs, list each open item by tracking number, date issued, responsible party, and days outstanding. When an RFI sits unanswered past its contractual response window, that fact belongs in the minutes, because unanswered RFIs are among the most common foundations for delay claims.
Submittals follow a similar format. AIA Document G712 provides a standardized form for tracking each submittal’s receipt, consultant referral, action taken, and return date.7AIA Contract Documents. G712 – Shop Drawing and Sample Record Whether you use that form or your own log, the agenda should show the status of every active submittal: pending review, approved, approved as noted, or rejected and resubmit. Late submittals delay material procurement, and that delay ripples into the schedule faster than most teams expect.
Financial Tracking
Money produces more disputes than any other construction topic, which is why the agenda needs a financial section that leaves nothing to memory.
Change Orders
Track every proposed change by number, description, estimated cost impact, and approval status. AIA Document G701 is the standard change order form; it requires signatures from the owner, architect, and contractor and covers changes to both the contract sum and the contract time.8AIA Contract Documents. AIA Document G701-2017 Change Order A proposed change stays on the agenda as “pending” until all three parties sign. Letting unsigned changes accumulate without weekly visibility is how budgets quietly blow up.
Payment Applications and Retainage
The agenda should track the status of the most recent payment application, including whether the architect has certified the amount due. AIA Document G702 provides the standard format and requires the contractor to show total work completed and stored to date, retainage withheld, previous payments received, a summary of approved change orders, and the current amount requested.9AIA Contract Documents. G702 – Application and Certificate for Payment
Retainage, the percentage the owner withholds from each progress payment as security, deserves its own line. On federal contracts, retainage cannot exceed 10 percent of the approved amount.10Acquisition.gov. FAR 32.103 – Progress Payments Under Construction Contracts Private contracts typically fall in the 5 to 10 percent range, though limits vary by jurisdiction. As the project approaches completion, the agenda should flag whether retainage reduction has been discussed.
Lien Waivers
Each payment cycle should include a record of whether required lien waivers have been exchanged. The four standard types are conditional and unconditional waivers for progress payments, and conditional and unconditional waivers for final payment. Conditional waivers only take effect once the claimant actually receives payment; unconditional waivers are effective immediately upon signing. Tracking outstanding and executed waivers prevents the surprise of a mechanics lien filed months after a check was supposedly cut.
Quality Control and Inspections
Quality issues caught late cost exponentially more to fix, so the agenda should track QC and inspection activity as its own section rather than burying it inside the schedule update.
Include the status of any material testing, such as concrete cylinder breaks, soil compaction tests, and steel weld inspections, along with whether results met specification. If a test fails, record the non-conformance and the corrective action plan. Building permit inspections belong here as well: which have been called for, which passed, which failed and need reinspection, and which are coming up in the look-ahead window. A failed rough electrical inspection that nobody discusses for two weeks can quietly put the drywall schedule at risk.
For projects with formal QC programs, the agenda can also capture whether preparatory meetings were held before new phases of work began. Walking through specifications and inspection criteria with a subcontractor before they start is far cheaper than writing non-conformance reports after the work is in place.
Third-Party Coordination
Construction rarely happens in isolation. Utility companies, municipal agencies, and neighboring property owners all introduce dependencies that belong on the agenda.
For utility work, track the status of relocations, new service connections, and conflicts between underground utilities and planned excavation. Capture the utility company’s mobilization date, duration of their work, and any predecessor activities that must be completed before they can start. Escalation triggers deserve a standing place on the template: when a utility company falls significantly behind, the record should show the gap and the steps taken to resolve it.
Municipal inspector visits, fire marshal reviews, and environmental agency checkpoints (stormwater permit compliance, for example) follow a similar tracking format: date requested, date scheduled, outcome, and any follow-up required. Public right-of-way work adds coordination with traffic management and local permitting offices.
Close-Out and Punch List
As the project approaches completion, the template shifts gears. Substantial completion covers ground that routine progress meetings never touch, and most teams wait too long to start discussing it.
The close-out section should track the running punch list of incomplete or deficient items, with responsible parties and target completion dates; the punch list’s total value directly affects retainage calculations and final payment. It should also track operation and maintenance documentation, including equipment manuals, warranty certificates, as-built drawings, and training schedules for building systems. On most contracts these are a prerequisite to substantial completion, not an afterthought to deliver weeks later.
Confirm warranty start dates and whether any exceptions apply to specific systems. Warranty commencement is often tied to the substantial completion date, so getting that date right matters. Document the transfer of responsibilities for security, insurance, and utilities when the owner takes possession, because a vague handoff creates liability exposure for both sides. And schedule and track the final inspection, certificate of occupancy, and any remaining regulatory sign-offs.
Introducing close-out topics a few months before expected completion is far better than scrambling to assemble documentation after the last subcontractor leaves. Projects where close-out drags on for months almost always share the same root cause: nobody put these items on the agenda until it was too late.
Additions for Federally Funded Projects
Projects receiving federal funding carry compliance requirements that private work does not, so the template needs an extra section when they apply.
Under the Davis-Bacon Act, contractors on covered projects must pay prevailing wages for all hours worked on-site and submit weekly certified payroll records to the contracting agency.11U.S. Department of Labor. Fact Sheet 66 – The Davis-Bacon and Related Acts Each submission must include a signed Statement of Compliance confirming wages meet the applicable determination.12U.S. Department of Labor. Instructions for Completing Davis-Bacon Payrolls Form WH-347 The agenda should track whether certified payrolls are being submitted on time, whether the wage determination and required poster are posted on-site, and whether any apprentices working at reduced rates have proper registration documentation on file. Worker misclassification and missing payrolls are the most common failures, and they are much easier to fix when flagged in a weekly meeting than when discovered during an audit.
Federal highway and infrastructure projects must also comply with domestic sourcing requirements for steel, iron, and construction materials under the Build America, Buy America Act.13Federal Highway Administration. Build America, Buy America Act Q and As The agenda should track material certifications showing domestic origin and flag any items where a waiver may be needed. Catching a non-compliant material order before it ships is a scheduling inconvenience. Catching it after installation is a project-stopping problem.
Minutes, Distribution, and Record-Keeping
The template only works if someone turns the discussion into a usable record. Assign one person as the dedicated minute-taker before the meeting starts, and make sure that person understands the project well enough to capture technical decisions accurately. Minutes should record decisions made, action items assigned with responsible parties and deadlines, and any dissenting positions. Keep the language factual and specific. “Owner directed contractor to proceed with alternate ceiling grid” is a useful record. “The team discussed ceiling options” is not.
Distribute finalized minutes within a few days of the meeting while the content is still fresh. Many project teams include a clause stating that minutes are considered accurate and approved unless corrections are requested within a set window, often two to five business days. That default acceptance mechanism prevents parties from claiming months later that the minutes do not reflect what happened.
Store completed agendas and minutes in a digital management system that timestamps each document and prevents retroactive edits. Organized by meeting number and date, these records become searchable project histories. If a dispute reaches formal claim proceedings, a clean sequential set of meeting minutes with consistent formatting carries significant evidentiary weight. A box of loose notes does not.