Window and Door Submittal Register for Custom Home Builders

Create a window and door submittal register from the current project documents and agreed supplier scope. Give every required deliverable a source reference, affected opening marks, issuing party, reviewer, project milestone, revision and status. Track receipt, review and resubmission separately. A complete register shows what is due and who acts next; it does not approve a product or authorize production.

For a custom-home builder, the immediate problem is often practical: drawings arrived, a sample is still being discussed, and a required document is buried in correspondence. A register brings those separate items into one reviewable list. Start it after award, using the decisions recorded in the supplier kickoff meeting.

Start with the current source set

List the selected proposal, attachments, plans, opening schedule and relevant project requirements by revision and date. Identify the person who can clarify an ambiguous requirement. If the supplier scope and project documents appear inconsistent, create a clarification action instead of deciding which document takes precedence yourself.

A document folder answers “What files do we have?” A submittal register answers “What deliverables are required, which have arrived, and what happens next?” Keep both. Each register row should point to the source that created the requirement and the latest submitted file.

Name a specific deliverable

Replace broad entries such as “window documents” with a clear action or deliverable. Depending on the actual project, that might be proposed drawings for an identified opening group, a finish sample with a reference number, or product information requested for a defined system. Do not turn this example list into a universal supplier obligation.

Procore’s guidance on submittal registers supports establishing the list early to help avoid overlooked submissions. The window-and-door fields below are an editorial coordination tool; the project documents determine what your register must contain.

Connect the row to opening marks

Record whether the deliverable covers one opening, a group, a system or the entire package. “All windows” is appropriate only when that scope is actually confirmed. If two systems have different reviewers or issue dates, separate their entries even when they appear in the same supplier folder.

Keep the opening reference consistent with the current schedule. When marks change, retain the old reference in the history and record the new one. Otherwise a submitted drawing can appear complete while the register is tracking an outdated group of units.

Assign the issuer, reviewer and next action

Use named contacts rather than “supplier,” “architect” or “site.” Record who issues the deliverable, who receives it for coordination, and who performs the applicable project review. These roles may be different. Assignments should follow the agreed project process and each party’s scope.

Every open row needs one immediate next action. “Follow up” is too vague. “Supplier coordinator to issue the revised drawing for W-01 through W-06” identifies the expected response. Record a project-specific target date or milestone, leaving it TBD until agreed.

Separate tracking status from review disposition

• Not requested: the requirement is identified but has not been issued to the responsible party.
• Requested: the request and receiving contact are recorded.
• Received: a file or sample has arrived; review is still pending.
• Under review: the assigned reviewer has the current submission.
• Resubmission required: a documented response calls for another issue.
• Closed: the required response and final reference are recorded under the project process.

Keep the reviewer’s actual disposition in its own field. Do not translate a formal review response into a stronger approval label. “Received” never means “approved,” and “closed” in this register does not establish production authorization.

Check completeness before routing

Before forwarding a package, confirm its identity, revision, affected marks and listed attachments. Record missing files as open actions. This administrative check does not replace technical review; it makes the submitted package identifiable and traceable for the responsible reviewer.

Use the shop-drawing review checklist for the separate drawing-review task. Keep comments consolidated through the agreed channel so a supplier does not receive several conflicting sets of instructions.

Copyable window and door submittal log

Two hypothetical register entries

These examples illustrate recordkeeping only. Opening marks and document names are fictional.

In the first example, receiving revision B does not close S-01 automatically. Record the subsequent review response. In the second, physical possession of a sample does not establish what surface, finish or opening it represents. Keep that question visible until the reference is confirmed.

Maintain one live register

At each review, filter for missing sources, unassigned actions, approaching milestones and resubmissions. Archive superseded files without removing the history. If the next action depends on another item, identify that dependency by register ID.

Connect those milestones to the window and door procurement schedule. Use project-confirmed dates rather than a generic review allowance. Distribute the updated register to the relevant contacts so the same status is visible across the team.

Bring the document list into your quote request

Meruzy manages and coordinates selected manufacturing partners for custom architectural systems. Project quotations, proposed product drawings and revisions are free. Share the current plans, window and door schedule, and required-document list so the proposed scope can be reviewed together.

The local project team verifies site conditions and approves final production information. Request a project quote with your current plans and document requirements.