Window and Door Supplier Kickoff Meeting Agenda for Builders

A window and door supplier kickoff should confirm the awarded scope and current document baseline, identify every project contact and decision owner, review open assumptions and required submittals, define revision and communication rules, align project-specific procurement and delivery dependencies, and state the written production-release process. The meeting records decisions; it does not change the signed scope or authorize production by itself.

Hold the meeting after supplier selection but before detailed coordination accelerates. The Builder should arrive with the selected proposal, attachments, clarification record and open-item list—not an empty agenda.

Prepare the meeting baseline

Distribute the selected proposal number, revision and date; current plans, elevations and window/door schedule; accepted alternates; known exclusions and assumptions; relevant correspondence; and the proposed project milestone list. Mark superseded documents before the call.

If the supplier has not yet been qualified, complete that work first using the published controlled overseas-ordering guide where applicable. Kickoff is not a substitute for due diligence.

Confirm attendees and authority

Name the Builder's project lead, supplier coordinator, architect or design reviewer, local verification contact, receiving/site contact and any other participant required by the project's contracts. For each person, record what decisions they may make and what must be referred elsewhere.

“Design team,” “factory” and “site” are not owners. Use named contacts and an escalation route. Meruzy manages and coordinates selected manufacturing partners, so the meeting record should also distinguish Meruzy's coordination role from partner-specific manufacturing facts and local professional responsibilities.

Agenda 1: awarded scope

Confirm which systems and opening marks are included, which proposal revision governs, which alternates were accepted, and which items remain excluded or TBD. Do not negotiate silent changes during the meeting. If the discussion changes commercial scope, route it through the agreed written process.

Agenda 2: document control

Agree how plans, schedules, proposed drawings, comments and revisions will be identified and transmitted. Establish one current-document index and a method for withdrawing superseded information. Identify who consolidates project-team comments before returning them to the supplier.

The detailed shop-drawing review checklist belongs at the later review stage. Kickoff only establishes how that review will be controlled.

Agenda 3: submittals and samples

List the proposed drawings, samples and other project-specific documentation expected under the agreed scope. Name the issuing party, intended reviewer and required sequence. Receiving a document does not prove that it applies to the proposed configuration or that the project team has approved it.

Route performance, code, structural, glazing, installation and other technical questions to the qualified parties responsible for the project. The agenda should record the question and owner, not manufacture an answer.

Agenda 4: open assumptions and decisions

Bring forward the assumptions accepted with the selected proposal. For each open item, record the affected openings, required response, decision owner and project milestone. Use TBD for criteria that remain unresolved. “Discussed at kickoff” is not a resolution.

Agenda 5: production release

Define the written event that authorizes production and who can issue it under the agreed process. Separate quotation information, supplier proposals, locally verified information, reviewed drawings and production-authorized information. Identify whether unresolved items hold the entire package or only affected opening marks.

A selection notice, payment, drawing transmittal or kickoff meeting should not be assumed to authorize production unless the applicable written agreement and process expressly establish that result.

Agenda 6: procurement and delivery dependencies

Review project-specific target milestones, supplier-confirmed dates when available, destination and access information, proposed delivery basis, receiving contact and site-readiness dependencies. Do not insert a generic lead time. Actual dates depend on the selected package, approved information, written order and supplier confirmation.

Agenda 7: communication and escalation

Choose the system of record for decisions, define response routing and establish a practical meeting cadence. Fast messages can alert the team, but material scope, revision and release decisions need a traceable written record.

Copyable kickoff agenda

1. Introductions, roles and decision authority
2. Awarded scope, alternates, exclusions and assumptions
3. Current drawing, schedule and proposal baseline
4. Submittal, sample and review register
5. Open design, verification and technical questions
6. Revision-control and comment-consolidation process
7. Production-release event and holds
8. Project-specific procurement and delivery dependencies
9. Communication, escalation and meeting cadence
10. Decision, action and document-update recap

Minutes and action record

Close the meeting as a controlled record

Circulate minutes promptly according to the project's agreed practice. Ask attendees to identify factual errors, then transfer actions into the live registers. Do not let the minutes become a second uncontrolled source of product information; update the governing proposal, schedule or drawing when required.

What the Builder should leave with

A productive kickoff ends with five controlled outputs: a confirmed proposal and document baseline, a named contact and authority list, an open-item register, a submittal and decision sequence, and a written description of the production-release process. Each output should identify its owner and next update point.

If one of these outputs cannot be completed, record the missing information and who will provide it. Do not fill the gap with a generic supplier practice or an assumed project deadline.

Common kickoff failures to avoid

• Reviewing from mixed revisions: establish one current index before discussing scope.
• Assigning actions to a company instead of a person: name the responder and escalation contact.
• Treating verbal agreement as document revision: identify which controlled record must change.
• Combining all open items into one hold: identify the affected opening marks or package area.
• Assuming dates: record only project-specific dates confirmed through the applicable process.
• Calling the meeting a release: preserve the separate written authorization step.

Start coordination from the current package

Meruzy provides free project quotations and can coordinate proposed product dimensions, drawings and revisions from submitted plans, schedules, photos and preliminary dimensions. There is no minimum project amount. The local project team must verify site conditions and approve final production information.

Submit the current project package for quotation and coordination.