Project Planning

How to Create a Window and Door Finish Schedule for a Custom Quote

Learn how to document exterior and interior finish intent, color references, sheen, texture, sample status, exceptions and revisions for a clearer custom window and door quote.
By AdminMeruzyPublished August 22, 2026Updated August 22, 2026Reviewed by MERUZY Project Coordination Team
Architecture project team comparing window and door frame finish samples with a finish schedule and elevation drawings

A useful window and door finish schedule records the finish intent for each opening in a form that a supplier can quote and clarify. At minimum, identify the opening mark, surface or component, exterior and interior finish, reference system and code, sheen or texture, sample requirement, current status, source document and revision. Use project-wide defaults where possible, list exceptions by opening, and mark unknown information as TBD rather than guessing.

The schedule is a coordination record—not proof that a finish is available, suitable, matched, reviewed or approved. A rendering can communicate design intent, a supplier quote can state what was priced, and a physical sample can support later review, but those are different stages. Keep each stage visible so a preliminary color choice does not quietly become production information.

Why finish information gets lost during custom quoting

Finish decisions often live in several places at once: an elevation note, an interior material board, a rendering, a written specification, an email and a supplier color chart. Those sources may use different names. “Dark bronze,” for example, may describe a design direction rather than a unique product finish. A screen image may look precise while omitting the color system, sheen, texture, substrate or sample status needed for coordination.

Custom window and door packages add another layer because one unit can have more than one visible surface. Exterior and interior frame finishes may differ. Hardware, trims, panels, screens or other components may need separate records. Some openings may follow a project default while a feature door or interior-facing frame is an exception.

The solution is not a longer color description. It is a controlled record that distinguishes what the project team requests from what the supplier quotes and what is later reviewed.

The eight fields every finish record should include

1. Opening mark

Use the same mark that appears on the current window and door schedule, plans and elevations, such as W-101 or D-203. If several identical openings share a type, record whether the finish applies to the type or to specific marks. Stable marks make it possible to trace an exception without rewriting the whole package.

2. Surface or component

Name what the finish applies to: exterior frame, interior frame, sash or panel, trim, visible hardware, screen frame or another clearly defined component. Avoid a single “color” cell when several components could reasonably be interpreted differently.

3. Exterior and interior intent

Keep exterior and interior finishes in separate fields even when the current intent is the same. This prevents “same color” from losing its reference when one side changes. If the project has no decision yet, use TBD. Do not infer that a dual-color arrangement is available for a particular system; request confirmation from the supplier.

4. Reference system, code and name

Record a recognized color-system name and code when the project team has selected one, plus any project name used in presentations. A standardized code is more precise for communication than a descriptive name alone. RAL notes that its unique designations and codes support communication across project workflows, while its digital libraries provide an early visual impression.

A code still does not establish product availability or an exact finished appearance. Keep a separate field for the supplier-stated finish or nearest offered option.

5. Sheen and texture

Color, sheen and texture are separate attributes. Record the project intent only when it is known and supported by project documents. If the desired surface is described only as “matte,” “smooth” or “textured,” identify that wording as design intent and ask the supplier to state its proposed finish designation. Do not translate descriptive language into a technical coating specification without the responsible project team.

6. Sample requirement and sample identifier

State whether a physical sample is requested, received or reviewed. Give each sample a traceable identifier and record the supplier, date and related proposal or drawing revision. Do not use a screenshot or ordinary printout as a substitute for a controlled physical reference. The RAL FAQ explains that ordinary four-color printing cannot reproduce every shade in true color, and RAL describes physical samples as part of professional color planning.

7. Status

Use status language that describes the stage without implying more authority than exists:

Status What it means What it does not mean
Design intent A project preference or direction has been recorded. The supplier has not necessarily quoted or confirmed it.
Requested for quote The finish information was issued with the quotation package. It is not automatically included or available.
Supplier quoted The proposal states a finish basis. The project team has not necessarily reviewed a sample.
Sample requested A physical reference has been requested. No sample review has occurred.
Sample reviewed The identified sample was reviewed by the named party. It is not production authorization unless the project process says so.
Approved for production The responsible project process has explicitly approved the identified finish information. Earlier renderings, quotes or informal comments do not create this status.
Revised A later record supersedes an earlier finish entry. The reason and affected openings still need to be traceable.
TBD The information is unknown or unresolved. No assumption should be inserted.

8. Source and revision

For every entry, identify the source document, date or revision. Examples include an architectural finish schedule, interior-design material board, issued clarification, supplier proposal, sample transmittal or approved production record. A finish schedule without source control can look complete while combining decisions from different dates.

Use project-wide defaults, then list exceptions

A compact schedule usually works better than repeating the same wording for every opening. Establish project-wide defaults only when the source documents support them, then create exception rows for openings or components that differ.

For example, the project may record one exterior-frame design intent for the general window package while D-301 has a different interior-facing intent. The schedule should show the default, identify D-301 as an exception and keep the supplier's quoted response in a separate field. It should not state that the exception is available until the supplier confirms it.

If your opening marks, quantities and preliminary dimensions are not yet organized, first use How to Prepare a Window and Door Schedule for a Custom Quote. Add the finish fields to that controlled opening list rather than maintaining an unrelated color spreadsheet.

A fictional finish-schedule example

Consider a fictional package with a general window type W-A and one feature opening D-301:

  • W-A exterior frame: design intent recorded with a color-system reference; requested for quote; physical sample TBD.
  • W-A interior frame: project finish intent not yet selected; status TBD.
  • D-301 exterior frame: same design-intent reference as W-A, but supplier response not yet received.
  • D-301 interior panel: separate material-board reference; treated as an opening-specific exception; sample requested.

This record makes the unresolved items visible without inventing availability. It also prevents the feature opening's interior requirement from being applied accidentally to every window. No real code, manufacturer option or approval is shown because those facts must come from the actual project and supplier documents.

Coordinate finishes through five distinct stages

  1. Design intent: the project team records the desired visual direction and known references.
  2. Quote request: the current finish schedule is issued with a controlled drawing and opening schedule set.
  3. Supplier response: the proposal states the finish basis, alternates, assumptions and exclusions.
  4. Sample and drawing review: identified samples and proposed product information are reviewed under the project's responsibility matrix.
  5. Production information: the responsible project team approves the final identified information through the required process.

Do not collapse these stages into one “approved color” column. When proposals return, use How to Compare Custom Window and Door Quotes to keep supplier-stated finish scope, alternates and TBD items visible. During later coordination, the window and door shop-drawing review checklist helps separate quoted information from reviewed production documents.

Common finish-schedule mistakes

  • Using only a color name: descriptive names can be ambiguous without a system, code or controlled supplier designation.
  • Using a rendering as the finish authority: renderings communicate appearance but may not identify the actual reference, surface or status.
  • Combining exterior and interior: one color field hides which side or component the note controls.
  • Leaving exceptions in email: opening-specific changes should return to the controlled schedule.
  • Overwriting the requested finish: preserve both project intent and supplier-quoted information so substitutions or alternates remain visible.
  • Calling a sample “approved” without authority: record who reviewed it, when, and what project process gives that review its status.
  • Forgetting revision history: a new sample or proposal should not erase the previous basis without a trace.

Finish schedule checklist before requesting a quote

  • Opening marks match the current plans, elevations and window/door schedule.
  • Exterior and interior surfaces are recorded separately.
  • Components that need separate finishes are named.
  • Known references include the system, code and project description.
  • Sheen and texture are recorded only when supported by project information.
  • Project defaults and opening-specific exceptions are distinguishable.
  • Unknown information is marked TBD.
  • Sample requirements and identifiers have their own fields.
  • Status does not imply quotation, review or production approval prematurely.
  • Every entry has a source and revision.

Frequently asked questions

Can I use an online color image as the final reference?

Use digital color information for early coordination only unless the project's documented process says otherwise. Screens, files, lighting and reproduction methods can change appearance. Record the actual reference system and use controlled supplier information and physical samples where the responsible project team requires them.

Should hardware use the same finish record as the frame?

Not automatically. Record hardware or other visible components separately when their finish matters. Ask the supplier to state the offered designation and relationship to the frame finish.

What if the supplier does not offer the requested reference?

Keep the requested intent unchanged, record the supplier's proposed option as a separate response, and request a sample or clarification. Do not silently replace the project reference in the schedule.

Does “sample reviewed” mean approved for production?

Not necessarily. The schedule should reflect the project's actual authority and approval process. Keep “sample reviewed” and “approved for production” as separate statuses unless the responsible project team explicitly defines them as the same action.

Prepare your finish information for a Meruzy quote

Meruzy offers free project design and quotation for custom architectural systems. Submit your current plans, window and door schedule, preliminary dimensions, reference images and clearly labeled finish intent through the project quote form. Meruzy can coordinate a proposed solution from the submitted information; the local project team must verify site conditions and approve final production information.

Project note: This guide organizes finish information for quotation and coordination. It does not confirm product availability, coating performance, color tolerance, sample acceptance, contractual responsibility or production approval.

Editorial review

Prepared for project education and reviewed for consistency with MERUZY’s current supply-only design, quotation and delivery process. Project-specific requirements are governed by approved documents and the formal order.

Reviewed by: MERUZY Project Coordination Team

Sources and further reading

QUESTIONS & DISCUSSION

Ask a question or add to the discussion

Have a question about this guide? Ask it here. The MERUZY team and other project professionals may respond.

Do not include private project information, addresses, drawings, pricing, order details, phone numbers or email addresses in your public comment.

Your email is used for moderation and is not displayed publicly.

Submissions are reviewed before publication. Please allow time for moderation.

Have a project to review?

Share your plans, rough dimensions, or schedules for a comprehensive DDP estimate and technical review.

Request a Project Quote