Window Project Meeting Minutes That Become Controlled Decisions

1. Commission the meeting with purpose, records and authority visible

Issue agenda, purpose, meeting ID, date/time/time zone, location/platform, required roles, pre-reads and decision requests. Link current drawing/register revisions rather than attaching unnamed screenshots. State whether the meeting coordinates, recommends, reviews or is expected to make defined decisions under delegated authority.

At opening, record participant name, organisation, role, attendance interval and claimed/delegated authority scope. Distinguish chair, minute taker, technical advisers, decision authorities, observers and substitutes. Attendance or silence does not confer approval power; verify delegation against the authority matrix.

Review prior actions and open RFIs/changes using stable IDs. Freeze the baseline used in discussion. If an essential decision-maker or document is missing, record that the item can be discussed but not disposed, and maintain the applicable hold.

2. Separate facts, discussion, decision, action and reservation at capture

Record facts as source-linked statements or observations: document says, survey records, shipment arrived, test reported. Label unverified statements and assumptions. Discussion summarises material options and evidence without turning the loudest opinion into agreement.

A decision entry states the exact authorised disposition, affected opening marks/configurations, effective conditions, authority and source. An action names a deliverable, owner and due date; an action to investigate is not the underlying technical decision. A reservation records objection, dissent, qualification or unresolved condition and who raised it.

Use unique item IDs and status codes with definitions. Avoid ‘noted’, ‘agreed’, ‘team to coordinate’ and ‘supplier to proceed’ without object, scope and authority. Record no-decision explicitly. Neutral wording should preserve disagreement instead of smoothing it away.

3. Write each decision so it can be incorporated without oral memory

Repeat the issue ID and baseline, state what changed or was confirmed, affected marks/locations, excluded scope, conditions, effective date and named authority. Cite sketch, sample, calculation or source by controlled identity. If the authorised outcome is only a recommendation or preferred option, say so.

Run an impact scan across design/shop drawings, schedules, BIM, BOM, glass/hardware/finish, compliance/certification, purchase/material, production, inspection/test, packing, installation, cost and programme. Name which records must update and which separate process—RFI, submittal, change, instruction, notice or NCR—will carry the consequence.

Meeting minutes themselves should not overwrite contract or released technical documents unless the governing protocol expressly assigns that role. Until incorporation and issue, maintain the old authorised baseline and visible holds. Emergency actions still require the project's authorised safety and follow-up route.

4. Control deadlines, distribution, correction and confirmation without inventing deemed approval

Every action has one accountable owner, deliverable, input dependency, due date/time zone, reviewer/acceptance authority, status and evidence link. Contributors can be listed, but ‘all’ is not an owner. Derive deadlines from programme need and approved protocol; this article sets none.

Issue draft minutes promptly through the controlled channel with meeting ID/version, distribution and a confirmation/correction window only if the project procedure defines one. Ask recipients to identify factual corrections, authority disputes and missing reservations with evidence. Preserve draft/final history and who approved the final record.

No comment should not be represented as contractual agreement or technical approval unless the executed contract expressly establishes that result and authorised legal/project governance confirms it. Late corrections require controlled amendment, not silent editing. If parties disagree, publish the disputed record and route resolution.

5. Link decisions to RFIs, changes and drawings, then close by evidence

Create an incorporation row for each decision/action: target controlled record, owner, target revision/status, due date and verifier. Link minutes to the TQ/RFI response, change order, instruction, submittal, drawing, schedule, work instruction or NCR rather than copying text inconsistently into each.

Withdraw/supersede old workface copies when revised sources issue. Verify procurement, factory, QA and site received the same baseline. Audit both directions: minutes decision to incorporated documents; changed document back to authority and meeting/RFI/change. A decision that cannot be found outside minutes remains operationally fragile.

Close a decision only after authority, separate consequences, incorporated documents, notifications, supersession and remaining holds are verified. Close an action only after its deliverable is accepted by the named reviewer—not when someone reports completion. Archive agenda, attendance, evidence, drafts/final minutes, reservations and relationship records.

FAQ

Continue the project review

Connect this guide with the proposed window and door systems, then review how Cavorlen approaches manufacturing and quality control. When your schedule is ready, send it through the project review form.

Related buyer guides

• A Window Factory Quality-Control Checklist Buyers Can Actually Use
• An Aluminum Window Specification Checklist for International Projects
• How to Evaluate an Aluminum Window Manufacturer in China