Window and Door Scope Gap Log for Preconstruction

A window and door scope gap log records every package item that is missing, excluded, assumed or left without a clear owner before bids are treated as comparable. Each row should identify the affected opening or package, source document, observed gap, decision question, proposed owner, required response and status. The log surfaces coordination work; it does not interpret contracts, allocate legal liability or select technical criteria.

For a custom-home Builder, the purpose is simple: make invisible scope visible while there is still time to ask a precise question. A gap does not automatically mean that a supplier made an error. It may come from the RFQ, design documents, proposal, local-work boundary or an unresolved project decision.

Use four gap types

1. Missing: an item needed to understand the proposed package is not shown in the current source set.
2. Excluded: a bidder expressly states that an item or service is outside its proposal.
3. Assumed: pricing or scope relies on a condition that the project team has not confirmed.
4. Unassigned: the work is recognized, but no party is clearly identified to coordinate or provide it.

Keep the categories separate. “Not shown” is different from “by others,” and both are different from a supplier assumption. Accurate labels make the next action easier to assign.

Freeze the review baseline

Record the exact RFQ, plan, elevation, schedule and proposal revisions under review. A gap log built from mixed revisions creates false issues. List every source by file name, revision and date, and identify superseded material before beginning the comparison.

If the pricing package itself is not controlled, start with a quote-ready window and door schedule. When proposals have already returned, use the scope-by-scope quote comparison to normalize them.

Review the package by boundary

Move through the proposal consistently. Check which opening marks and quantities are included; which systems, accessories or finish directions are identified; which drawings and revisions are referenced; and which delivery, unloading, storage, installation, field-verification and professional-review activities are stated or excluded.

This is not permission to decide how those activities should be performed. Record only what the current documents say, what they do not say and which project party must clarify the question.

Write an observable gap

A useful observation can be reproduced by another reviewer. Write: “Proposal revision B lists opening marks W-01 through W-18; current schedule revision C includes W-19.” Avoid conclusions such as “supplier forgot W-19” until the package boundary and transmission record are checked.

Turn the observation into a decision question: “Confirm whether W-19 is included in the requested package and identify the proposal revision that will carry it.” This creates an answerable task rather than a vague warning.

Propose an owner without assigning liability

The log can propose who should answer next—Builder, architect, supplier coordinator, qualified local verifier or another named party—subject to the project's actual contracts and professional roles. “Architect to confirm design intent” is a routing instruction. It is not a declaration that the architect bears contractual liability.

Every open row also needs a required response: revised proposal, drawing clarification, schedule update, written exclusion, local verification or a visible TBD carried into pricing.

Use controlled status labels

• Open: question created but not yet assigned or answered.
• Pending response: named owner and requested evidence recorded.
• Resolved: answer documented and the controlled source updated.
• Carried as TBD: intentionally unresolved for the current quotation stage.
• Not applicable: reviewed and excluded from this package with a reason.

“Discussed” is not a closed status. A row closes only when the answer is traceable to a controlled document or written project decision.

Copyable scope gap log

Pre-bid closure check

• Every row cites the current source set.
• Every observation is separated from its conclusion.
• Every open question has a proposed owner and required response.
• Resolved items point to an updated document.
• Remaining unknowns are visible as TBD.
• No log entry is treated as production authorization.

Prioritize gaps without hiding them

Not every gap needs the same response time, but every gap should remain visible. Add a coordination priority based on its effect on the next project decision: now for an item that prevents bid comparison, before selection for an item that changes the accepted package, before drawing review for an input needed to develop proposed information, and before release for information that must be locally verified or approved before affected items can proceed.

Priority is not a risk rating and should not imply a technical judgment. If the project team cannot determine the correct milestone, record the milestone as TBD and assign the question to the responsible project lead.

Keep the log connected to change control

A resolved gap often changes another controlled record. A missing opening may lead to a revised schedule and quote. An unclear finish direction may lead to a design response and updated proposed drawings. An unloading exclusion may lead to a site logistics action. Record the resulting document and revision in the resolution field so the answer does not live only in an email thread.

When a new proposal revision arrives, do not delete the history. Mark which rows the revision addresses, confirm whether the wording actually closes the question, and carry forward everything still open. This makes it possible to explain why two proposals that appear similar are not yet comparable.

Use the log in a 20-minute review

1. Confirm the document baseline and remove superseded files.
2. Review new gaps and changed supplier language.
3. Assign each open question to a named responder.
4. Identify items that block bid comparison or package selection.
5. Record updated source documents and leave unresolved criteria as TBD.

The meeting should end with an action list, not a rewritten scope. The Builder remains responsible for coordinating the project process, while qualified local parties retain the verification and approval duties defined by the project.

Send the controlled package for quotation

Meruzy manages and coordinates selected manufacturing partners for custom architectural systems. Builders can submit current plans, schedules and scope questions for a free project quotation; proposed product drawings and revisions are also free. There is no minimum project amount. The local project team must verify site conditions and approve final production information.

Request a project quote with the current scope gap log.